Skip to Content

Rename SI_ID after Promotion

Dec 28, 2017 at 11:48 AM


avatar image

Hi Experts,

I have a report on DEV envt with report ID 13795 and now i have moved this report to UAT envt and now the CUID for both reports are same but Report id get changed.

But for me it is mandatory to have same report ID on both the environments.

So is it possible to have same Report ID or rename or Update UAT report ID with DEV report ID ?

Please advise

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Best Answer
Denis Konovalov
Dec 28, 2017 at 12:34 PM

SI_ID change during promotion is normal, this is how ID's work.
SI_ID is unique in the cluster, but changes when object is moved to another environment/cluster.
CUID is unique during objects live time, so it stays the same no matter where the object is.

Using SDK, you might be able to change SI_ID of the object, but it is a dangerous road, as you need to ensure no other objects with your desired SI_ID already exist.
Instead you should not rely on SI_ID's in any of your workflows/designs and use CUID instead or object name.

10 |10000 characters needed characters left characters exceeded
Jawahar Konduru Dec 28, 2017 at 06:28 PM

why do you want keep the same SI_ID across all the environments? What is the use case for you? As explained above by Mani and Dennis, IDs will change.

10 |10000 characters needed characters left characters exceeded
Manikandan Elumalai Dec 28, 2017 at 04:33 PM

Just to add with Denis.

You cannot maintain same SI_ID across all the environments for an object as it is a sequence number generated for CMS_IDNUMBERSx table which is getting incremented not only an object is created in repository by user but also objects created by the system. So when you promote objects across environments you will not get the same SI_ID all the time.

The only way to maintain SI_ID unique across environments is to restore the CMS tables and FRS, which should be done only during your environment recovery scenarios. You don't need to maintain SI_ID across environments.



10 |10000 characters needed characters left characters exceeded