Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Customer Service forum

Import failed: Column names in each table must be unique. Column name 'Column A' in table 'Table A' is specified more than once

(0) ShareShare
ReportReport
Posted on by 200

Below error while trying to import a solution into UAT.

Import failed: Column names in each table must be unique. Column name 'Column A' in table 'Table A'  is specified more than once. Any solutions please?

Thanks in advance.

Categories:
  • Suggested answer
    Nishant Rana Profile Picture
    Nishant Rana 11,320 Microsoft Employee on at
    RE: Import failed: Column names in each table must be unique. Column name 'Column A' in table 'Table A' is specified more than once

    This is what worked for us

    nishantrana.me/.../

  • Lynda Joyner Profile Picture
    Lynda Joyner 30 on at
    RE: Import failed: Column names in each table must be unique. Column name 'Column A' in table 'Table A' is specified more than once

    Thank you for your response Swathi, this did indeed resolve my error.

  • Verified answer
    SwathiD Profile Picture
    SwathiD 200 on at
    RE: Import failed: Column names in each table must be unique. Column name 'Column A' in table 'Table A' is specified more than once

    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

  • Lynda Joyner Profile Picture
    Lynda Joyner 30 on at
    RE: Import failed: Column names in each table must be unique. Column name 'Column A' in table 'Table A' is specified more than once

    Hi

    Did you get a resolution to this error as I have also encountered this error today and struggling to resolve. Many thanks

  • Suggested answer
    SwathiD Profile Picture
    SwathiD 200 on at
    RE: Import failed: Column names in each table must be unique. Column name 'Column A' in table 'Table A' is specified more than once

    This is a Microsoft issue. 

  • Dynamics365 Rocker Profile Picture
    Dynamics365 Rocker 7,755 on at
    RE: Import failed: Column names in each table must be unique. Column name 'Column A' in table 'Table A' is specified more than once

    An entity in CRM will be table in SQL.

  • SwathiD Profile Picture
    SwathiD 200 on at
    RE: Import failed: Column names in each table must be unique. Column name 'Column A' in table 'Table A' is specified more than once

    Sorry but this is not custom entity. This is a MS SQL table.

  • Dynamics365 Rocker Profile Picture
    Dynamics365 Rocker 7,755 on at
    RE: Import failed: Column names in each table must be unique. Column name 'Column A' in table 'Table A' is specified more than once

    in Dynamics 365, GoTo-->Settings-->Solutions-->Open your solution -->Open entity A and check if there is field with duplicate display name.

    If you find duplicate field then change display name of field.

  • SwathiD Profile Picture
    SwathiD 200 on at
    RE: Import failed: Column names in each table must be unique. Column name 'Column A' in table 'Table A' is specified more than once

    Thank you for the replies. Our organisation uses online Dynamics 365. And this is an underlying Microsoft SQL table (so we cannot check the field type or edit the table)

  • Suggested answer
    Darshik Profile Picture
    Darshik 295 on at
    RE: Import failed: Column names in each table must be unique. Column name 'Column A' in table 'Table A' is specified more than once

    Hi SwathiD,

    Please check whether the field name is same and data type is different for the field then delete the filed and migrate the field with the solution .

    you can export the target table schema and matched with the source schema.

    also check whether the field name is the case sensitive.

    Regards,

    Darshik

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... 292,516 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,401 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans