Form Layout not moving when publishing scoped app to the Application Repository

danpatino
Tera Expert

My client is having an issue promoting a scoped application I created for them.   When they install or update the application (using the 'Make App available on other instances' link), the form layout on the custom tables is completely off.   It's as if the Form Section (sys_ui_section) record didn't move over but there were no prompts for issues or conflicts.   We found a workaround by adding the sys_ui_section record to an update set manually and applying the update set.   However, it would be much more convenient if all updates moved through the application repository.

Has anyone experienced the same issue and/or were you able to find the cause?   Thanks in advance for any input!

1 ACCEPTED SOLUTION

Thijs Daemen
Mega Guru

Hi Dan,



This sounds a lot like PRB639462 which we had some serious issues with for one of our scoped apps.



https://hi.service-now.com/nav_to.do?uri=problem.do?sys_id=f2a03f750fe10ec01c7e938172050e19%26syspar...



We were told it should be fixed in patch 8 of the Fuji release.



We experienced this on new installations and reinstalls of the scoped application. Some form layout / sections weren't being copied at all.


View solution in original post

9 REPLIES 9

Thijs Daemen
Mega Guru

Hi Dan,



This sounds a lot like PRB639462 which we had some serious issues with for one of our scoped apps.



https://hi.service-now.com/nav_to.do?uri=problem.do?sys_id=f2a03f750fe10ec01c7e938172050e19%26syspar...



We were told it should be fixed in patch 8 of the Fuji release.



We experienced this on new installations and reinstalls of the scoped application. Some form layout / sections weren't being copied at all.


I can't see this record.


Is there a workaround?



ServiceNow Nerd
ServiceNow Developer MVP 2020-2022
ServiceNow Community MVP 2019-2022

Hi Paul,



No, unfortunately ServiceNow did not have a (automated) workaround for the deployment of the application. The only thing that would work is what Dan Patino mentioned in his post


We found a workaround by adding the sys_ui_section record to an update set manually and applying the update set.

Ok, that is what I have been doing too.



ServiceNow Nerd
ServiceNow Developer MVP 2020-2022
ServiceNow Community MVP 2019-2022

The SN Nerd
Giga Sage
Giga Sage

I have had this exact same issue. I even posted about it last week but no-one replied



The Default view is in global, not in that application scope.


You can only have one default view, so this can't be fixed (until a patch).


It is good to see a fix is on the horizon, as this is frustrating.



ServiceNow Nerd
ServiceNow Developer MVP 2020-2022
ServiceNow Community MVP 2019-2022