Answered

Data import creates duplicate rows

(0) Share

Report

Posted on by Dereva

Hello,

I have created a custom table using a data import from an excel with the primary key: Work_Order_#. When I check the table, the initial 1812 rows has ballooned to over 4000 with duplicate rows using the same primary key (i.e. 3 rows for WO1817, 2 rows for WO1819). I thought you couldn't have multiple primary key entries? On top of that, I see that it imported ~80 blank rows.

Any help would be appreciated, thanks.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

AhmedSalih

6,680 Moderator on at

Like (1)

Report

Copy link

Link copied!

Hello, @Dereva, your custom table must have an Alternate Key assigned to your Primary Key Column before you run the DataFlow.

If my reply helped you, please give a 👍 , & if it solved your issue, please 👍 & Accept it as the Solution to help other community members find it more.

I am primarily available on weekdays from 6-10 PM CT and 5-10 PM CT on weekends.

Visit my Blog: www.powerplatformplace.com

Was this reply helpful? Yes No

Fubar 8,487 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Primary Name field is not a primary key (Primary Name is what gets displayed in Lookup fields and at the top of the a Model Driven App form when you view/edit a record).
The true primary key is a generally a system generated GUID (but can be forced to be another unique GUID useing code or when data importing) that is held in a field with the same schema name as your Table with a suffix of "id" e.g. new_mytableid for a Table with a schema name of new_mytable. You can create your own Alternate Key to enforce uniqueness on other Column(s). If integrating etc with other systems you would need to either use the actual Primary Key field or an Alternate Key.

Was this reply helpful? Yes No