Topic: Custom Fields (Required)

Why is it that when you create a required custom field it cannot be left blank? By requiring "default text" in the custom field you are defeating the purpose of it being "required".

For example: I've created a custom serial number field. I want every asset entered to have it's corresponding serial number added as well. However, since a "default text" is already present the user creating the asset is not "required" nor prompted to update the field.

Am I misunderstanding the intended purpose of a required custom field or is this something that can easily be changed?

Last edited by jared (2010-12-16 18:57:08)

Re: Custom Fields (Required)

You are correct that the current implementation of required custom fields is not ideal. We have had a few other requests to change this, and we are planning to make the change in the next few months.

Justin Sinclair

Got Inventory? Get Tracmor.

Re: Custom Fields (Required)

A workaround that I've found for the time being is to do the following:

  1. Create your custom field from the Admin panel without setting the "Required" check-box.

  2. Next, go to your Tracmor databse and edit the custom_field table.

  3. Locate your created custom field, and change the required_flag field from 0 to 1.

Alternatively, you could run a SQL query, similar to the one below, where the custom_field_id correlates to the field you wish to modify.

UPDATE `tracmor`.`custom_field` SET `required_flag`=1 WHERE `custom_field_id`='1';

Re: Custom Fields (Required)

Just wanted to give an update on this request. Requirements have been published here and this change will be part of our next release.

Justin Sinclair

Got Inventory? Get Tracmor.