Skip to main content

Notifications

Announcements

No record found.

Finance | Project Operations, Human Resources, ...
Answered

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

(1) ShareShare
ReportReport
Posted on by 145
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
 
  • Verified answer
    André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 291,861 Super User 2024 Season 2 on at
    What causes a "is already in use." message upon Import?
    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.
  • rgouette Profile Picture
    rgouette 145 on at
    What causes a "is already in use." message upon Import?
    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
     
  • Verified answer
    André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 291,861 Super User 2024 Season 2 on at
    What causes a "is already in use." message upon Import?
    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.
     
     
    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. 
     
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Congratulations 2024 Spotlight Honorees

Kudos to all of our 2024 community stars! 🎉

Meet the Top 10 leaders for December

Congratulations to our December super stars! 🥳

Start Your Super User Journey Pt 2

Join the ranks of our community heros! 🦹

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,861 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,540 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans