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

whitewalker · ‎10-11-2017

Chuck Tomasi wrote:

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

No, thanks.

Chuck Tomasi · ‎10-11-2017

If I have answered your question, please mark my response as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.

If you are viewing this from the community inbox you will not see the correct answer button. If so, please review How to Mark Answers Correct From Inbox View.

Thank you

Peter Oneppo · ‎06-23-2020

Chuck,

"There may be a property to disable this" - From what I can tell, there isn't. Did I miss it? If not, do you know how we can get one added?

"doing so would be a real pain to developers in the future because every field would need to be manually added." - In our experience as an ISV, the opposite it true: it's a pain to remove the fields that get added especially if you don't know its happened. You should be consciously arranging your forms anyway, so you should have to explicitly add fields. This "feature" can cause a lot of trouble. For example, we have a base class that extends Task. We extend that for our application tasks so that we can have one place to put common business logic. When we were building domain support, we added "sys_domain" to the base table. It added "Domain" - a field you generally don't want on the form - to all of the forms for the tables we extended from that base class. We didn't see it until after we submitted for certification and had to resubmit.

Thanks,

-pbo

Peter Oneppo · ‎06-23-2020

Chuck,

"There may be a property to disable this" - From what I can tell, there isn't. Did I miss it? If not, do you know how we can get one added?

"doing so would be a real pain to developers in the future because every field would need to be manually added." - In our experience as an ISV, the opposite it true: it's a pain to remove the fields that get added especially if you don't know its happened. You should be consciously arranging your forms anyway, so you should have to explicitly add fields. This "feature" can cause a lot of trouble. For example, we have a base class that extends Task. We extend that for our application tasks so that we can have one place to put common business logic. When we were building domain support, we added "sys_domain" to the base table. It added "Domain" - a field you generally don't want on the form - to all of the forms for the tables we extended from that base class. We didn't see it until after we submitted for certification and had to resubmit.

Thanks,

-pbo

Nicholas Sjelin · ‎12-13-2023

Necropost, but I found how to disable this feature.

Find the Business Rule "Add New Column To Form Section", which runs on the sys_dictionary table, and disable it.
This effectively prevents all new sys_dictionary records (adding Columns to Tables) from automatically adding the new column to its respective table's default form layout.

I find it less of a pain to manually add fields where I want them in forms, as opposed to the platform just dropping it in the default view's default section. Many times, we add columns specifically to enable reporting, or want them to be in particular sections rather than in the default layout, or even to a specific custom view... the benefits of disabling this rule, for us, far outweigh the cons.

Your mileage may vary, but if you really want to disable this, you can.