How to change the order of mandatory fields that pop up on list view?

BeccaGib · ‎01-05-2018

We have a UI Policy set up so that when a "Salary" amount is entered in a field, two other fields become mandatory. When a Salary amount is entered in the list view (by double-clicking and saving on the cell), it pops up the two new mandatory fields. Is there any way to change the order that these two new fields display in the popup?

Andras Kisgyorg · ‎01-09-2018

HI Beccad,

That;s right, it's not only driven by dependencies, UI policies are also considered in this list-edit popup.

After digging into this and some testing, to me it seems that there are multiple factors at play which determine the ultimate order of field display,

however my guts feeling is that the default display order comes from the UI policy actions in their sys_id order against the given fields of the table.

But again, this may be overriden by field dependencies or multiple UI Policies controlling the same field, etc.

Below example is the incident table list edit:

and the UI policy actions (ORDERBYsys_id) at play on incident table:

In conclusion, I would suggest that if the order of the fields really matters, restrict the list-edit action and get the users to open the record and populate the form directly.

Please let me know if this helped,

Cheers,

Andras

View solution in original post

BeccaGib · ‎01-05-2018

What I have tried so far:
Changing the names of the fields to see if they display in alphabetical order

Creating one separate UI Policy per field and then changing the order of the UI Policies

Changed the order the fields display on the form layout to see if it reflects in list view

Andras Kisgyorg · ‎01-08-2018

hello Beccad,

Aren't those fields set as Dependent on each other in their Dictionary?

As I believe this popup gets displayed rather because of field dependencies, and the order of the fields in the popup should be the dependency order.

For example field B is dependent on field A, when you list-edit either of them, a popup should come up displaying field A and field B in this order under each other.

Please let me know if this helps.

Cheers,

Andras

Uncle Rob · ‎01-08-2018

Ooo good call!

BeccaGib · ‎01-08-2018

I tried turning off the UI Policy and instead made one of the fields dependent on the first field. It does not have the desired effect of making the user input a mandatory second value if they enter a first value.

Maybe I am missing something?

I have seen the behavior you are talking about with dependent Choice fields, but we are not using Choice fields here.