Finance | Project Operations, Human Resources, ...

Package fails to import through recurring Integrations API

(0) Share

Report

Posted on by Community member

Hi,

Is recurring integrations capable of taking a zipped /Data Package/ such as the following?

I know that the Zip itself works fine, because I can import it through the UI manually without error. However the API is not quite working.

I am sending the above as a Zip to the endpoint /api/connector/enqueue//, and the requests are landing in D365.

Here is the Recurring seup. It recognises the fact that the file will contain the 4 entities, and shows that I have sent in 6 messages.

As can be seen here, all of the messages have failed. Annoying there are NO error essages in the Batch Job processor. And there isn't any information here either.

How do I go about diagnosing this?

Thanks

Luke

I have the same question (0)

All responses (4)

Answers (0)

Martin Dráb 237,878 Most Valuable Professional on at

Like (0)

Report

Moved from D365 general forum to D365 Finance forum, because it seems to be about F&O and not about D365 in general. Please let me know if you disagree.

I also changed the title from Recurring Integrations to make it more specific.

Was this reply helpful? Yes No
Suggested answer

Anthony Blake 2,963 Super User 2025 Season 2 on at

Like (0)

Report

Recurring integrations is definitely capable of importing a Data Package

In the Data management workspace, take a look at Job History, select one of your runs and click Execution details. Hopefully there will be more details on the errors in there.

Was this reply helpful? Yes No
Community member 2 on at

Like (0)

Report

Hi Anthony,

Are you saying that the "Inbound messages" (as per last screenshot in my first message) should make their way to the Data Management History view? The 6 inbound messages above have not landed in the Data Management history view at all. Having said that, the Inbound mesages view also sports an Execution Details button... but it is greyed out. I assume that means there isn't any detail.

Was this reply helpful? Yes No
Suggested answer

Anthony Blake 2,963 Super User 2025 Season 2 on at

Like (0)

Report

Good question I don't have an example of a package execution to check myself, it could be either a limitation of running packages through recurring integration or because it failed before the step.

Do you have the facility to try the package through the REST data package API? https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/data-management-api

The other approach I would consider is reducing the contents of the package, e.g. try only Sales Order Headers V2, then add line V2, etc.

Was this reply helpful? Yes No

Join the conversation

Community site session details

Package fails to import through recurring Integrations API

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates

Community site session details

Package fails to import through recurring Integrations API

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates