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

Data Management as Integration - Auto-Generation logic and data structure.

(0) ShareShare
ReportReport
Posted on by 2,190

Dear experts

Data Management in D365 can be used as integration tool  between D365 and third party software , my undertanding is.

A simple integration in my case is an import of csv files which will generate batch orders in status created.

The data entity to be used is Batch orders and I can achieve this easily by setting up a project and mapping the fields .

Where I get stuck is around fields that are mandatory for D365 and they are meaningless for the third party integration.

For example , the column BatchOrdernumber seems to be mandatory in the file for the import.

You can set the column to be auto-generated but , the column needs to be specified in the file with blank values .

This is where I get confused. Why do we need to specify these fields in the file if we set the rules in D365 ?

In theory , the file structure should contain only the information provided by the third party software and D365 should manage the additional fields thanks to the rules applied such as auto-generation or auto-default.

Why do we need to specify the column in the file ? 

Or am I setting up the project wrongly?

I have the same question (0)
  • Suggested answer
    Sergei Minozhenko Profile Picture
    23,095 on at

    Hi Alessandro,

    First of all, you need to check Map source to staging in the data project. If BatchOrderNumber is mapped between source and staging, you need to have this column in the inbound file to pass file structure validation. I'm not sure how mapping looks in your case, but usually you use one file as an example to create the entity with mapping, and then in mapping details, you can add a new line manually and select auto-generated field and auto-default fields. The field, in this case, will not have a mapping between source and staging, but the value will be taken from a number sequence if it's supported.

  • Aparisi82 Profile Picture
    2,190 on at

    This is what I did to generate the mapping and setting the batch order number field to be auto-generated but then I would like the import file to not contain that field for future imports.

    But D365 would not let me and import will fail.

    I created this post where I explain the issue in detail

    https://community.dynamics.com/365/supply-chain-management/f/dynamics-365-supply-chain-management-forum/415409/dm-import---auto-generate-logic-and-file-structure 

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 March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Supply chain | Supply Chain Management, Commerce

#1
Mallesh Deshapaga Profile Picture

Mallesh Deshapaga 306

#2
Laurens vd Tang Profile Picture

Laurens vd Tang 191 Super User 2026 Season 1

#3
André Arnaud de Calavon Profile Picture

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

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans