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 :
Supply chain | Supply Chain Management, Commerce
Answered

Data Management - Import Scenario - Log Analysis

(0) ShareShare
ReportReport
Posted on by 2,188

Good afternoon dear experts

the scenario is that I am importing 282 records using Data Management and using a standard data entity.

The import is successful and according to the import, D365 states that 78 records have been created and the rest updated.

pastedimage1673632249178v1.png

If I look at the staging table, it tells me that all 282 records have been imported without error as the status is "Completed" however there is no indication on the staging table of which records have been created and which ones have been updated directly from this job without workarounds such as database log or exporting the same data entity before and after the upload?

Now, how would I identify the 78 records created?

pastedimage1673632289292v2.png

I have the same question (0)
  • André Arnaud de Calavon Profile Picture
    300,731 Super User 2025 Season 2 on at

    Hi Alessandro,

    If the table has the property createddatetime enabled, you can recognize the created records by this field. Data Management Framework itself does not maintain this information.

    What is the (business) reason that you want to know the records which got created?

  • Suggested answer
    SouravDam Profile Picture
    11,730 on at

    Hi Alessandro Parisi,

    In addition to what André mentioned, you will know and can compare what are the new records that is imported is by taking a copy of entire existing records from the form before you do the import. This is from functional side 

    Regards,
    Sourav

  • Aparisi82 Profile Picture
    2,188 on at

    Control on importing the file and understanding what is created and what is updated.

  • Aparisi82 Profile Picture
    2,188 on at

    As mentioned in my post this is not what I would like to do. The same table could be updated by other users in the meantime I run the import and the count therefore compromised.

    I find the data management import really a "primitive" tool for running updated en-masse in the system.

    Anyway thanks for the replies.

  • Verified answer
    nunomaia Profile Picture
    25 Moderator on at

    Data management for some scenarios works quite well, in another ares, yes, it misses very basic features.

    Unfortunately, it don't tracks in staging records that were updated and records that were inserted.

    Sometimes it required me to go destination tables and filter records by update date / time  

  • Aparisi82 Profile Picture
    2,188 on at

    Thank you, to add on this , even the updated information on the staging table is misleading as actually in my scenario the majority of records being imported are not updated.

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 > Supply chain | Supply Chain Management, Commerce

#1
Siv Sagar Profile Picture

Siv Sagar 303 Super User 2025 Season 2

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 173 Super User 2025 Season 2

#3
Laurens vd Tang Profile Picture

Laurens vd Tang 93 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans