How to add new field to table but not to default form view

whitewalker · ‎10-11-2017

I have created a UI Page that add fields to specific table, but I don't want to add this fields to table default view.

Found this in wiki: "When you create a field from the system dictionary, it is automatically added at the end of the first section of the default form view."

Also i don't want to set specific form view for those table.

Any ideas ?

Chuck Tomasi · ‎10-11-2017

Hi Nick,

You would have to remove it from the form after it has been created. There may be a property to disable this, but doing so would be a real pain to developers in the future because every field would need to be manually added.

The forms are constructed from the following tables, sys_ui_element, sys_ui_section, sys_ui_form, and sys_ui_view. You can kind of see how the pieces fit together (parent/child relationships) based on the names.

Can I ask what the use case is for adding a field via a UI page? Seems like a tough way to do something that's already built in to the system in several other places.

View solution in original post

Chuck Tomasi · ‎10-11-2017

I'm not sure how a UI page that creates fields, but doesn't show them solves this.

Depending on what value is selected in Choice field, form should display a set of additional fields.

If you create a field on the dictionary, but don't place it on the form, you cannot display it dynamically. This sounds like you need the fields on the form, but not displayed by default, and then show some combination of those fields based on the choice in the choice list. To me this sounds like a client script or UI policy (i would go for the latter as a starting point.) If it's a wide variety of combinations, attack it programatically with data lookups. E.g. if option A, then show fields 1, 4, 6, 7.

Not: Anything done on the client side (UI policy or client script) must be on the form with the form layout or form designer to be displayed/hidden.

Let me know if I missed something somewhere.

whitewalker · ‎10-11-2017

Chuck Tomasi wrote:

Not: Anything done on the client side (UI policy or client script) must be on the form with the form layout or form designer to be displayed/hidden.

Yep, just tested and found out this.

So my question is not valid anymore.

I was going to use UI policy and Client Script to show/hide required fields, but wanted as default to hide them all when the form is loading. Just gonna use other approach.

Thanks to all for your replies.

Chuck Tomasi · ‎10-11-2017

You can hide them with an onLoad client script. I've seen that done before.

whitewalker · ‎10-11-2017

Yes, but when the form is loaded, there is a little delay (0.5 sec) before script hides fields.

Chuck Tomasi · ‎10-11-2017

That's true. The fields need to be loaded, then UI policies and client scripts come in to play. That's just how the platform works.

Is there anything else I can help you with in this discussion thread?