What causes a "is already in use." message upon Import?

(1) Share

Report

Posted on by rgouette

151

I've got an issue when using Data Management & Entities to migrate User Security Config.
The migration completes, and is mostly ok, except for the following, which is happening

If I look at Staging Data, and filter for ERRORS, I can see one or more of this:

/Results. The name [DUTY NAME] is already in use./
Where, [DUTY NAME] is a custom Duty, or Priv, or Role.

And along with this is, we're also seeing some Duties become UN-associated with roles, after the migration.

Are these two related?

Kind thanks,

Rich

I have the same question (0)

All responses (3)

Answers (2)

Verified answer

André Arnaud de Cal... 301,704 Super User 2025 Season 2 on at

Like (1)

Report
Copy link

Link copied!

Hi Rich,

This can happen in case configurations were done in two different environments. When creating an object via the security configuration form, these objects will get a GUID ID as an identifier. If you create a Duty "Duty name" in one environment and also "Duty name" in another environment, they will get different GUID IDs. If you then want to move the configuration from one environment to another, there is a check on both the GUID ID and the security object name. Then based on the GUID IDs, they are different, but there is a duplicate detected based on the name. The object will be then indeed removed from the role as the reference is maintained on the GUID ID.

You can find some more information on my blog: How to: Move security configurations across Dynamics 365 environments (dynamicspedia.com)

To solve your issue, you can use the option Remove customizations available on the Security configuration form. This will delete all configurations. Thereafter, you can import the security configuration. You can also remove the objects identified as duplicate only. In case you deleted configured security roles, you would need to reassign the roles to the users.

Was this reply helpful? Yes No
rgouette 151 on at

Like (0)

Report
Copy link

Link copied!

Thanks so much Andre.

So, to be clear: if we needed to re-create a Duty or Privilege, and then migrate to PROD environment, we would have to manually DELETE that object from PROD first?

Regards,

Rich

Was this reply helpful? Yes No
Verified answer

André Arnaud de Cal... 301,704 Super User 2025 Season 2 on at

Like (1)

Report
Copy link

Link copied!

Hi Rich,

Depending on the scenario, it is also possible to delete the configurations in a UAT/Dev environment where you maintain the security, Then import all configurations from the PROD instance and apply the new required changes. That will prevent you from making risky changes in the production environment.

In future, ensure you will use only one non-production environment for security configuration. Then move from this environment to UAT for testing and after that, you can move it to production. Treat it similar to a development process.

Was this reply helpful? Yes No

Join the conversation

Community site session details

What causes a "is already in use." message upon Import?

Helpful resources

News and Announcements

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the December Top 10 Community Leaders!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates

Community site session details

What causes a "is already in use." message upon Import?

Helpful resources

News and Announcements

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the December Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates