Please answer my query

[Deepa12]

Hi,

i want to understand that Dev and production environment local update sys id should be same.

I migrated the local update set xml file from dev to prod. both having same retrieved sys id but update set sys id is differ.

pls advise me.

Update set	update set name
DEV local update set sys id	xxxxxxxxxxxxxx
PROD retrieved update set remote sys id	yyyyyyyyyyyyyyyyyyyyyyyyyyyy
XML file sys id	ssssssssssss(Same sys id in dev and prod)
PROD retrieved update set sys id	ssssssssssss(same sysid in dev and prod)

[Community Alums]

Hi @Deepa12 ,

Always move customization through Update Set to maintain the same SYS_ID.

When you manually create a record in two instance, it takes a sys_id randomly.

[Deepa12]

Hi Sandeep, thanks for reply.

I have worked enhancement and created update set also(xml file store) in dev, that time dev clone has done. so again i migrated that xml file to dev env. after that i migrated this file to production.

Now issue is dev and prod retrieve update set remote sys id is varying. kindly assist me what is the issue

DEV local update set sys id	PROD retrieved update set remote sys id	XML file sys id	PROD retrieved update set sys id
e496733c47ad511081a70834846d433a	9f774c721b181510aef9c802604bcb95	f708180c471d919081a70834846d43a0	f708180c471d919081a70834846d43a0

[Kurian Thomas P]

ok got it,

so you uploaded an old xml after clone to both dev and prod and did not use team dashboard module or re-export the xml from dev.

if you want consistency
i would suggest you back out the updateset from prod.
export the xml from dev again then redeploy
but only if any issues occurs.

if all your files are properly in prod it should not cause any issue

[Pinky Awal]

I believe I am not the right person for the above query.