Hi, Readers.
Today I would like to talk about an interesting topic, when adding a Boolean field on the list page, why sometimes a checkbox is displayed and sometimes a Yes/No text?
PS: Boolean Data Type: Indicates true or false.
Let’s look at an example first, Item List (31, List):
Assembly BOM (6, Boolean): A Yes/No text
Cost is Adjusted (29, Boolean): A checkbox
Why? This is actually a UI behavior that has been preserved since NAV.
NAV 2018:
Next, take a look at the source code.
Assembly BOM (6, Boolean): A Flowfield
Cost is Adjusted (29, Boolean): Normal field
Well, in fact, the most important point is not Flowfield, but whether we can click through on it (Lookup/Drilldown) and whether it is editable.
Let me use one of the behavior point of list pages to do a simple test.
PS: List pages that are accessed from the Role Center page open embedded within the Role Center framework. The pages are always opened in the read-only mode, regardless of the Editable property. More details: Behavior points of List Pages
Add two new Boolean fields to Payment Terms page. Add a simple OnDrillDwon Trigger for the second one.
Access from the Role Center page, the page is opened in the read-only mode.
TestBoolean01: A checkbox
TestBoolean02: A Yes/No text
Access from Search (Tell Me).
TestBoolean01: A checkbox
TestBoolean02: A checkbox
Test Video:
Let’s look at another example, setting the Editable property of the second field to false.
Access from the Role Center page, the page is opened in the read-only mode.
TestBoolean01: A checkbox
TestBoolean02: A Yes/No text
Access from Search (Tell Me).
TestBoolean01: A checkbox
TestBoolean02: A Yes/No text
Easier to understand, isn’t it? Give it a try!!!😁
END
Hope this will help.
Thanks for reading.
ZHU
コメント