Record producer created on a wrong scope

[1_DipikaD]

Hi All,

I have created a record producer in global scope but it should be created on a different scope . So now what should I do  ? Should I create a new update set changing the scope and restart the catalog from beginning or is it possible to change the scope from global to custom without harming my development  ? Also I want to know if I can change the application scope from custom to global as well ? 

Please suggest.

Thank you. 

[Dr Atul G- LNG]

Create it fresh that will be more better.

[Ankur Bawiskar]

@1_DipikaD 

then better to create fresh components in correct update set.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Sandeep Rajput]

@1_DipikaD Creating the RP and variables from scratch is the easiest solution. However, if you want to do it in other way then export the XML of your update set, try and replace the attributes representing the Global scope with the Custom Scope and re-import the same XML on your instance. 

[RohanGladman]

In your developer instance, open the record producer i.e. "Finance Query" - created in Global scope.
Switch to the scope you should be in - Finance.

Top right on the record producer form, there should be a UI Action: "Copy"
This will take a carbon copy of all your config, and save it in the correct scope as "Copy of Finance Query".

Back in Global scope, the original record producer should then be renamed i.e. "Finance Query Legacy", and inactivated.

Now in Finance scope, update the name, short description and producer template to your preferred name.