Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Importing project xpo ...
Microsoft Dynamics AX (Archived)

Importing project xpo in different environment

(0) ShareShare
ReportReport
Posted on by MYGz 1,858

Hi,

I imported project xpo containing classes,tables,jobs,etc. in a different AX environment.

I'm getting index already used SQL Server error. for eg. the index 'I_106RecID' in table 'Table1' is already used before in 'Table2'

Is the metadata also copied in the process of export import AOT objects? 

Doesn't the new AX environment assigns fresh numbers from number sequences to the newly imported objects? If not, then how to export import AOT objects without worrying about metadata.

Thanks.

*This post is locked for comments

  • MYGz Profile Picture
    MYGz 1,858 on at
    RE: Importing project xpo in different environment

    I resolved all the compilation errors to which I was importing the XPO. But I was still getting some errors as some objects were to be overwritten. Then I deleted all the common objects, reimported the xpo, then I was able to successfully import.

    Import overwrite errors are common?

  • MYGz Profile Picture
    MYGz 1,858 on at
    RE: Importing project xpo in different environment

    Thanks Nikolaos,

    After checking the AOT that I was importing the project into, it is giving the same error. Some other dev might have made changes because last time I checked it was compiling ok.

    I was getting error for the same 2 original objects and 4 tables out of 8 newly imported tables. Yes the error was only on synchronization.

    I'm now resolving the original compilation error and then will try to reimport the project.

  • Verified answer
    nmaenpaa Profile Picture
    nmaenpaa 101,156 on at
    RE: Importing project xpo in different environment

    That sounds like a strange error, I haven't seen it before. And it should not matter if two indexes in different tables have the same name.  So you get this error when synchronizing the database? Do you get many such errors? Are you sure the source and target environments were healthy before you started with the import?

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

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

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans