sys_ui_view on different domains

[Salvador Alcant]

After upgrading to Utah the UI views we created under global domain scope, doesnt load when changing into other Domain scope.

I have access to global Domain scope, so when I created the UI views for the table, its under global Domain scope.  other users done have access to global, so they are automatically scoped to domain : internal_e.g, when this happens, the UI view loads the default not using the view we created.

AS admin,I can replicate the issue by switching the domain scope from global to internal_e.g.

the view of table changes, the correct layout which follows our UI view is from the Internal.

 

 

How can I make the UI views work regardless of domains?  Thank you.

[Community Alums]

Hi @Salvador Alcant ,

The 'sys_ui_view' table is not domain separated. So unfortunately you cannot make the UI views work regardless of domains.

[Tony Chatfield1 · Accepted solution]

Hi, list views are stored in sys_ui_list table and they are domain separated.
This means that if someone in domain X changes their list view a record will be created in that domain for that user, if an admin user updates a view while in domain X, then a new view will be created in X with user field empty (IE for all users). Similarly if someone adds\removes fields for a report, then these changes will also show as a record in domain X.

If you have views created in specific domains but want users to have the global view, then you can simply delete the relevant domain specific sys_ui_list record(s)  and this should also delete the dependent sys_ui_list_element records;

But as with everything in life, test and validate in sub-production before updating prod.

[Salvador Alcant]

Thanks all for the response. I'll try that work around.