Finance | Project Operations, Human Resources, ...

DMF API package import "None of the columns used for mapping matches with columns in uploaded file"

(3) Share

Report

Posted on by Rich

385

Has anyone else encountered this "None of the columns used for mapping matches with columns in uploaded file" error when using the DMF REST API? Any suggestions why it happens please?

We're seeing this on 20-40% of executions when running in reasonably quick succession (6-10 executions per minute) in a Tier 4 environment, with no clear pattern of the first or the last executions in a given period being the ones to fail (i.e. failures are mixed in with successes), and if we import the failing packages through the UI, the error doesn't occur, so I'm pretty confident there's nothing directly wrong with the input data files or the metadata XML files that accompany them in the zip. With little expectation, we added a brief delay between the blob upload API call and the import from package API call in case the upload was somehow incomplete, but that didn't seem to help (and hasn't been necessary before in my experience of using the REST API). Any thoughts welcome

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (10)

Answers (0)

Sort by

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

Like (0)

Report
Copy link

Link copied!

HI Rich,

Can you tell what technology your are using to call the data management API? Are you using Logic Apps, Postman, or something else? Please describe the process how you build the package zip file and how you send it to the API.

Was this reply helpful? Yes No
Rich 385 on at

Like (2)

Report
Copy link

Link copied!
André,

Thanks for attention. Yes, we're using Logic Apps to create the zip, then make what I'd consider the 'normal' three calls to

get write URL (receiving 200 response & a URL)

upload blob via HTTP put to that URL (receiving 201 response)

import from package (receiving 200 response)

Was this reply helpful? Yes No
Rich 385 on at

Like (2)

Report
Copy link

Link copied!

Microsoft have confirmed that this can happen when multiple DMF API requests are sent in quick succession for the same DefinitionGroupID: there's a conflict in the mapping process that means multiple executions attempt to use the same table at the same time. Rather than deadlock, you get this error. They haven't advised whether we can ask the API whether it's busy with an existing mapping, so we may have to introduce a random wait in hope of avoiding the conflict

Was this reply helpful? Yes No
PaulNoakes 48 on at

Like (0)

Report
Copy link

Link copied!

We have recently started experiencing the exact same issue - did you find a solution?

Do you know if MS are working on a fix?

Was this reply helpful? Yes No
Suggested answer

Giorgio Bonacorsi 2,364 on at

Like (1)

Report
Copy link

Link copied!

Hello,

As far I know, when you use the DMF API, the columns mapped into the Import project should be the same of the files present into the package.

If there is a different, you risk to have an error.

Thank you,

Giorgio

Was this reply helpful? Yes No
Rich 385 on at

Like (0)

Report
Copy link

Link copied!

@Paul - No updates from MS yet, no: Support are in that unenviable position of just passing messages between us as a Partner and their Product Group. If you log a support request with MS, feel free to mention our request ID 2602120050003228 if you think it'll make the point that multiple people are encountering this behaviour.

@Giorgio - the columns/fields mentioned in the import package manifest XML are those present in the data files, hence the packages importing without issue when loaded through the UI, and MS confirming it's a conflict in the mapping process between instances of the execution, rather than being an intrinsic problem with the packages

Was this reply helpful? Yes No
Suggested answer

Anthony Blake 3,142 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi @Rich

You can poll the API for the result, the endpoint is data/DataManagementDefinitionGroups/Microsoft.Dynamics.DataEntities.GetExecutionSummaryStatus

See working example here:

https://www.postman.com/anthonyblakedev/workspace/dynamics-365-finance-apis/request/22139284-2bbe6beb-3647-4a96-b6bb-7af0c3de8eb9?action=share&creator=22139284

You should be able to use this in your orchestration rather than have to use a random delay.

Anthony

Was this reply helpful? Yes No
Rich 385 on at

Like (1)

Report
Copy link

Link copied!

Thanks Anthony. We don't need to wait for the previous job to finish loading before we start the next, but I take your point, getting confirmation that the previous job has started successfully should act as confirmation that there will be no mapping conflict. Feels like an idea with legs. Appreciated

Was this reply helpful? Yes No
Anthony Blake 3,142 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

No problem @Rich, I'm just wondering if you can use the status to implement queuing while you wait for MS. Exactly like you say, if its in progress, if may be an indicator that the mapping step is done. Are you running via a logic app? Does it allow these requests to run asynchronously, i.e. more than one instance of the logic app running at a time? Just thinking, it could be another reason the clash can happen if 2 kick off asynchronously in very quick succession.

Was this reply helpful? Yes No
Diego Mancassola 787 on at

Like (0)

Report
Copy link

Link copied!

Hi, read the discussion from the first day.

The mapping project is always the same or every time you create a new import project for every import?

Was this reply helpful? Yes No