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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics 365 | Integration, Dataverse... / A duplicate column hea...
Microsoft Dynamics 365 | Integration, Dataverse...
Answered

A duplicate column heading exists while downloading Template for data export

(1) ShareShare
ReportReport
Posted on by BF-19051058-0 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?
 
 
A duplicate column heading exists.png
Categories:
Dynamics 365 general
I have the same question (0)
  • Suggested answer
    Tom_Gioielli Profile Picture
    Tom_Gioielli 3,086 Super User 2026 Season 1 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
    BF-19051058-0 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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

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

#1
11manish Profile Picture

11manish 85

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 76 Super User 2026 Season 1

#3
Subra Profile Picture

Subra 61

Last 30 days Overall leaderboard

Featured topics

Welcome to the Microsoft Dynamics 365 forum!
Identifying an Org as CDS or Dynamics
Get batch job history log from D365 FO to Power Automate
Gross and Net Weight of Shipments feeding back into Sales Order (from External Source)

Product updates

Dynamics 365 release plans