The differences between the development environment and the test environment

島崎拓磨 · ‎08-13-2025

Hello everyone,

In my current project, we are using update sets to migrate from the development environment to the test environment.
A moment ago, I noticed that in the test environment, there are two record producers with the same name. (One of them is inactive and shows a warning icon.)
In the development environment, there was only one record producer.
In this case, is the only option to delete it directly in the test environment?
Our client has requested that we avoid making direct deletions in the test environment as much as possible, so I’m struggling with how to proceed.
I look forward to hearing your professional advice!

Shashank_Jain · ‎08-13-2025

@島崎拓磨,

Find the Root Cause (Why it happened)

As you found two record producers with the same name in the Test environment. This could have happened for one of two reasons:

Manual Creation in Test:
Someone may have created the duplicate directly in the Test environment by mistake.
Accidental Migration from Dev:
The duplicate may have been included by mistake in an update set from the Development environment.

To fix it -

If the duplicate came from an update set:
Check the update set and roll back the change.
If it was created manually in Test:
Since it wasn’t part of any update set, delete it directly from Test.

As I understand it, two record producers were originally created in the Development environment. After development was completed, one of them was deleted in Dev. However, the update set may not have been cleaned up properly before being moved to the Test environment — which is likely why both record producers are now appearing in Test.

Hope it helps!

If the solution was helpful, mark it as correct and close the thread.

Thank you!

If this works, please mark it as helpful/accepted — it keeps me motivated and helps others find solutions.
Shashank Jain

View solution in original post

Ankur Bawiskar · ‎08-13-2025

@島崎拓磨

Did you debug and analyze the other record producer was migrated as part of some other update set?

Did you check if someone created that record producer directly in TEST instance?

if that record producer is not captured in any update set in TEST then you are good as it won't migrate to PROD anyhow.

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

Regards,
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader

Ankur Bawiskar · ‎08-13-2025

@島崎拓磨

Hope you are doing good.

Did my reply answer your question?

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

Regards,
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader