The differences between the development environment and the test environment

[島崎拓磨]

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!

[Nikhil Bajaj9]

Hi @島崎拓磨 ,

Since it is not there is DEV so my POV - no other choice to delete it from Test ENV. But you should check why it is duplicate and are version same or code was moved twice with 2 different versions? If code was moved twice see roll back option. Also what warning it is displaying as you said that there is warning icon as well?

If my answer helped you, please mark it solution accepted.

Regards,

Nikhil Bajaj

[Ct111]

check the sysid of both the record producers that you see in test.

If one of them matches with dev , then make the other inactive (so that it is not in use).

Now the one which is present in both dev and test, recapture the record producer in dev if some changes has been made, via "Add to Update Set"  link , if your organization uses, otherwise do it via  conventional way 

And then move this changes to the test environment via update set,  in this way it would be bit clean solution.

[OlaN]

Hi,

Does both the records exist in the PROD instance ?
If so, then maybe the record should not be deleted in TEST, it should be copied to DEV.

[Shashank_Jain · Accepted solution]

@島崎拓磨,

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:

1. Manual Creation in Test:
   Someone may have created the duplicate directly in the Test environment by mistake.

2. 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!