Form field not visible in a domain separated environment.

[Ashwini3]

Hi,

I have minimal knowledge on Domain separation.

My instance is domain separated, and a field on the incident form is not visible. It should be visible on incident form only in particular domain.

The field is visible on our Dev instance but missing on Test and Prod instance. I am not sure where to check for this domain based configuration changes. The field exists at the backend in the instance and field value is also been captured but just the field is not present on the incident form.

I could find a domain specific record under System UI --> Forms (i.e. sys_ui_form) in my Dev instance and it is missing on my Test instance. I am not sure if that the affecting the field visiblity.

Kindly suggest, where should I check to find the related configuration.

[scott barnard1]

Hi

If there is a form missing and it contains the form section that you want to see then that is your problem.

In the domain separated environment go to Views

Pick up the default view on the table in question

You should see at least 2 entries in the forms section. 1 will be the global one that all see and the other should be your special domain one.

Note your domain one will need all the other entries as well as the extra field.

If the domain one is missing from test then you didn't force it to update set when created. They don't go by default.

Easy way is to just pop up 2 screens and recreate the form, in the correct domain on your TEST instance. 

Don't try and xml it, it's easier just to recreate.

Hope that makes sense 🙂

[dj7887]

Hi Ashiwini,

1) check on your Dev instance in which perticular domain field is visible.

2) In that domain check form layout and UI policies and client scripts for that field.

After that on Test instance.

1) Go to respective table and check whether field exist or not.

2) If field exist on test then go to respective Domain from Domain picker and then add field to form.

3) Or ele you can also move xml's from Dev instance.

Please mark helpful or correct if this helps to resolve your issue.

Thanks,

DJ.