Dependent & Required Fields

I don't know of an easy way to do that in Studio.

Off the top of my head, if I needed to do that I would look in the cache folder at that module's vardefs (for example

cache/modules/Leads/Leadvardefs.php ) and search for

'required' => true

Not the most efficient way, but it's one way....


You can get the same information via API using the metadata, for example:

rest/v11/metadata?type_filter=modules&module_filter=Leads

But both those require searching and digging for the required true.

Finally, the option I would probably choose if I had that many fields to check would be to write a quick script:

get the bean in question and output the required fields to the log:

$GLOBALS['log']->fatal($bean->required_fields);

None of these are "easy" solutions, maybe someone else will have better ideas...

FrancescaS

HI Annie Kielian,

I agree with Francesca that there is no easy way to get a comprehensive list of all required fields. If the majority of the fields you have are custom fields created  via Studio, then our Upsert Lens plug-in provides you the quickest way to see which custom fields are required. One of the lenses provided in the plug-in is the Fields Metadata Lens which provides you a backend view of all fields created via Studio. You can filter the lens by module and whether the field is required to get to the information you are seeking:

You would still need to manually inspect all of the module's original base fields to get a comprehensive list of all required fields, but Upsert Lens would likely cut the time down on this exercise significantly. 

Chris

Hi Annie, I don't have an answer for you, but wanted to share my experience with required fields on dropdown-conditional layouts. In my testing, if the required field is not on the current layout, it does not prevent saving the record. It only prevents saving if it is on the layout that is currently applied. If you see something different, there may be something weird going on, or maybe there is a different reason that the required fields are being validated.

Hopefully you can find a solution that works for you though!

-Brenda

Chris Raffle purchased! please get me package asap! :)

Hi Annie,

Yes Brenda is right, it would be most probably some readonly/calculated field that is empty and also required.

And since you can't edit it, it is preventing you from saving the record.

--Shameen Arshad

Hi Annie,

If the required fields are custom fields (added after the first creation of the module) then you can do a custom query in the Advanced Reports

Here is an example of the SQL you could run, just change the module name below.
select * from fields_meta_data where custom_module = 'Accounts' and Required = 1

Having said that, in my experience, if a field is not displayed in a layout, it should not block you from saving even if it has been checked required in Studio.

Muriel

I am happy to share that our version 3.0 release of Upsert Lens includes a new 'Vardef Lens' so you can filter and view through the field vardefs of any module in the UI:

This new lens provides the ultimate source of truth as it provides a compiled insight of Studio configurations and code-level customizations. Now you can quickly identify which fields are required, calculated, read-only, and more!

Chris