Making an existing custom field mandatory as a required field

[crmtamer]

I was asked to make an existing custom dropdown field mandatory (required). Checking the Required checkbox in studio had no effect on the field, because, I assume, it had already been created. (Running Repair Custom fields after checking the box had no effect.)

I made the following changes and it appear to be working:

In EditView.html I added the following: <span class="required">{APP.LBL_REQUIRED_SYMBOL}</span> , which now causes the required field red asterisk to appear in the edit screen.

In /opt/sugarcrm/cache/dynamic_fields/Opportunities/fields.php I changed: 'required_option' => 'required', (changed from 'optional' to 'required')


Is there anywhere else I should make a change to code? And is there any future impact that I should be aware of?

[mapm]

Did you try the repair custom fields in studio?

[lvangool]

Why oh why are you editing in /cache? The name 'cache' suggests something temporary...it won't last!

you should take a look at vardefs and field_arrays

[crmtamer]

This custom field is not found in either vardefs or field_arrays. Where else are custom field definitions stored?

[gunni]

Of which field exactly are you talking?

[crmtamer]

It is a custom dropdown field in the Opportunities module (created in Studio).

[mjp9119]

This custom field is not found in either vardefs or field_arrays. Where else are custom field definitions stored?

Hi, I´m no sugar wizzard but I've asked that question to myself a few weeks ago and the answer
my friend is.....FIELDS_META_DATA !!!
( it´s just a table )
I´ve notted that there´s a table with that name in the sugar_database.
better take a look in there..you'll be glad you did.
Good luck.

[crmtamer]

Thank you! That's exactly what I was looking for -- I found the field in fields_meta_data and changed it from optional to required, so hopefully that will ensure it will stay that way in the future.