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

danpatino · ‎09-01-2015

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!

Thijs Daemen · ‎09-01-2015

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

Pradeep Sharma · ‎09-01-2015

Hi Dan,

Can you go to the sys_metadata.list table from the navigation filter and then group by your application name.

Make sure that the files are captured there related to form sections. If not try to capture this on your scope and then push the changes.

I hope this helps

danpatino · ‎09-01-2015

Thanks for the quick response Pradeep.

The sys_ui_section record is not in the application files list. However, when I navigate to the sys_ui_section record, it does have my scoped app in the Application field. Also, the system doesn't allow me to change the form layout without being in the proper scope.

This further explains the problem but I'm still not sure what to do to fix it.

Pradeep Sharma · ‎09-01-2015

Hi Dan,

That is the expected behavior. The form layout will not be specific to the record and it will be global. That is where system gives you the warning. However Just try to make changes to the field slightly and then re do the changes so that atleast this will be captured.

I hope this info helps

danpatino · ‎09-01-2015

Pradeep,

Here are the steps I performed just now:

Created a new update set within the application scope.
Made arbitrary changes to forms in two tables
Added a comment to a business rule
Confirmed the three Customer Update records were in the update set.
Completed the update set.
Incremented the version and published the app to the repository.
Updated the application in the target instance.

Result: The comment was in the business rule but the forms' layouts did not update.