Record Producer Best Practice for Scoped Applications

[Kev9]

Hi,

We've created a custom application with it's own scope that has record producers that reside within a Catalog within the app.

We find however that if we want to make minor changes to one of the record producers in the app it seems excessive to have to republish the entire app. It also causes issues if more major changes are being developed in the app that we can't make the minor changes to the record producer if done in parallel with the RP update as it will pull through whatever dev work has been completed on the major change.

How have others dealt with this? Is it better to create the RP's for the app in Global scope and add them to the custom app Catalog? Is there an issue i  doing this?

Thanks

[Community Alums]

Hi @Kev9 ,

First you will need to create the update set with the scope

Select the scope from the banner and create local update set in that scope

Create the Record producer that will be captured in the update set after that make the update set complete and export to xml

To move the update set to other instance open the retrieved update set upload downloaded update set xml file and preview and the commit the update set

The record producer can be created by selecting the table which will be available there, if unable to see the scoped table then there is some condition on that field written which must be restricting the scoped application table to display there