Skip to main content

Notifications

Announcements

No record found.

Dynamics 365 general forum

SQL Error Column names in each table must be unique.

(0) ShareShare
ReportReport
Posted on by 30

Hi 

I am encountering this problem in two different scenarios which I suspect may be linked. 

1.) I have attempted to export a solution (managed) from Sandbox Environment to Production today which includes a custom entity, the import into Production fails due to the import being to large, however when open the log it gives the reason states Column names in each table must be unique. Column name 'stageid' in table 'A'. As part of this solution I have enabled Business Process Flows to allow creation of Mobile Task Flows, I believe that stageid was created as part of this, but only exists once within Sandbox. 

2.) Having looked at the same custom entity within the Production environment, stageid does not exist and the Business Process Flow is not enabled yet. However if I attempt to enable Business Process Flow I get the same error. 

I have checked all fields within the entity for any duplication. 

Is anyone able to shed any light on this or provide any guidance as to how this could be resolved?

Many thanks

  • Lynda Joyner Profile Picture
    Lynda Joyner 30 on at
    RE: SQL Error Column names in each table must be unique.

    Thank you Swathi

    This has worked and the error seems to be resolved. 

  • Verified answer
    SwathiD Profile Picture
    SwathiD 200 on at
    RE: SQL Error Column names in each table must be unique.

    Hello Lynda,

    This is a Microsoft issue and below is the resolution they provided.

    1. Open the solution and click on the entity with the issue (Ex: Contact) .

    2. Uncheck the “Offline capability for Dynamics 365 for Outlook” (you should be able to see this field when you click on the entity )

    3. Check “Business Process Flows” field as well.

    4. Then export and import the solution into the target.

    3. Once the import is successful, again check the “Offline capability for Dynamics 365 for Outlook” field and again export and import the solution.

    Thanks,

    Swathi

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

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Coming on 11/8!

In our never-ending quest to help the Dynamics 365 Community members get answers faster …

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard

#1
André Arnaud de Calavon Profile Picture

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

#2
Martin Dráb Profile Picture

Martin Dráb 230,466 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans