Finance | Project Operations, Human Resources, ...

Package is not available for execution while export customer master through custom entity

(2) Share

Report

Posted on by @rp@n

Hi Team,

When I export the Customer master data through custom entity. - It is not creating the data package and got the below error: in log file it is showing "Record already exists in stagging table".

View execution log

I have checked in Stagging table, there is already Primary index on this.

Properties :

Allow duplicate is set to NO, then why it is showing on log "Record already exists in stagging table".

How will i resolve this issue.

thanks!

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

André Arnaud de Cal... 304,729 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @rp@n,

When looking at your screenshots, it is related to a customization. What is the source table and what records are to be exported? In case the source will give for some records more than one record with the same Client1 value, it is not unique anymore. So, it is probably not your staging table, but the source records which might have a duplicate value for your export job.

Was this reply helpful? Yes No
@rp@n 56 on at

Like (0)

Report
Copy link

Link copied!

"Thanks Andre, for the response.

As you said "In case the source will give for some records more than one record with the same Client1 value,

You mean to say source = Cust table?

Pls let me know which class and method will be the best option to debug this issue.

thanks!

Was this reply helpful? Yes No
Martin Dráb 239,451 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Moved from Integration, Dataverse, and general topics forum.

We can't tell you what data source your entity uses. That something you should tell us, not the other way around.

If you've added a custom field to CustTable and you're trying to use as an entity key, you'll have to make sure that all CustTable records have a value in the field and that all values are different.

Was this reply helpful? Yes No
Suggested answer

Alireza Eshaghzadeh 14,853 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi,
I completely agree with André and Martin—it appears the issue is due to duplicate records related to Client1, which does not allow duplicates. If the values in this field need to be unique, please verify for any duplicate entries and resolve them accordingly.

Was this reply helpful? Yes No