web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Answered

A duplicate column heading exists while downloading Template for data export

(1) ShareShare
ReportReport
Posted on by 9
When attempting to export from an Advanced Find View, I get the below error message.
 
A duplicate column heading exists
A duplicate column heading exists. If you contact support, please provide the technical details.
 
 
A duplicate column heading exists. If you contact support, please provide the technical details.
Error Code: 0x80040338
 
I have seen a few solutions for when importing but not exporting.
 
Any suggestions?
 
 
Categories:
I have the same question (0)
  • Suggested answer
    Tom_Gioielli Profile Picture
    2,762 Super User 2025 Season 2 on at
    CRM really doesn't like having more than one column with the same name in an export.
     
    1. Go to https://make.powerapps.com and open your tables list
    2. Find the table you were exporting from, and go to the 'columns' area to see all of the defined fields
    3. Sort the list of fields by name, and look for two of them that have the same Label Name
    4. Update the label of one of them so it is unique
    5. Save and publish your changes
     
    This has been a limitation for years now, but I think of it as a good thing as you should always try to avoid having duplicate columns names from the perspective of data quality, user perspective, and general system administration.
     
    Good luck and hope this helps!
  • Verified answer
    BF-19051058-0 Profile Picture
    9 on at
    The issue wasn't to do with naming of any of the fields in a table.
    There were many fields/columns I was selecting when creating the view and as there were fields that had similar (although not the same) column names, I had selected some fields/columns more than once (not helped by the window being small to see the full name of the field). Which cased this error.
    I found a workaround - Downloading XML of the view (Download Fetch XML), then pasting it to Excel and then creating a pivot table to identify fields that more than one row/count

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
Siv Sagar Profile Picture

Siv Sagar 93 Super User 2025 Season 2

#2
#ManoVerse Profile Picture

#ManoVerse 76

#3
Martin Dráb Profile Picture

Martin Dráb 64 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans