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 :
Finance | Project Operations, Human Resources, ...
Suggested Answer

D365+logic apps: use recurring integrations and check status of import project

(0) ShareShare
ReportReport
Posted on by 15

Hi all.

We need to process xml files which we receive from externally in Dynamics 365 F&O and apply a transformation before importing. We succeeded in doing this by creating a logic app which polls an FTP location and uses the enqueue service to place the xml file on the DMF queue (https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/recurring-integrations).

So far, so good. But what would be the approach in case processing the file fails? We can see the status in the scheduled data jobs page and in the DMF execution details. But we can't resume processing or retrieve the xml from Dynamics, correct? Would that mean that we have to poll in the logic app to check the execution status hand handle the file accordingly? And if so, how would we retrieve the executionId as we only get the message id returned from the enqueue request?

Or any other suggestions?

 

Thanks for your feedback!

Kenn

I have the same question (0)
  • Suggested answer
    Ludwig Reinhard Profile Picture
    Microsoft Employee on at

    Hello Kenn,

    The DMF import is done by running a batch job, right?

    If this batch job fails you can send an email to a specific account that can trigger a notification flow to inform users that something was going wrong.

    Wouldn't that be a solution to follow up errors with the import?

    Best regards,

    Ludwig

  • KennV Profile Picture
    15 on at

    Hi Ludwig

    Thanks for your quick answer!

    The scheduled data job is indeed a batch job which can check if there are new messages to process with a certain recurrence.

    However, when an import fails, the status of the recurring job will be "Processed with error" but the batch task will have status ended and I don't think I can resume the batch task from there.

    Maybe I can setup up an alert based on the recurring job status in Dynamics, but I don't know how we will be able to retrigger then?

    That's the reason I was lookin into handling it in the "calling" logic app. Just like when you would use the data management rest API, where we get the execution id back from ImportFromPackage and can use it again in GetExecutionSummaryStatus.

    Best regards

    Kenn

  • KennV Profile Picture
    15 on at

    Looked a but further.

    Don't know how I missed it earlier, but the solution is probably just on the same page.

    docs.microsoft.com/.../recurring-integrations

    --> API for getting message status

    POST /data/DataManagementDefinitionGroups/Microsoft.Dynamics.DataEntities.GetMessageStatus

    BODY

    {

       "messageId":"<string>"

    }

    will return the execution status.

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 > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 565 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

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

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 250 User Group Leader

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans