Finance | Project Operations, Human Resources, ...

Copying recurring integrations batch jobs

(4) Share

Report

Posted on by CU22120935-0

150

Hi,

I created a recurring job out of an export data project in Company A, and when i click on "manage recurring data jobs" i see this recurring job and all processed records.

Now if i go to the batch job form and copy this recurring batch job and it's monitoring batch job (but specify another legal entity when copying, Company B), then i don't see this new recurring job inside "manage recurring data jobs". Why?

But if i go to the export data project and switch to another legal entity (Company C), then create another recurring job from it, then if i go to "manage recurring data jobs" i will see two jobs one for Company A and one for Company C, but why i can't see there the one for Company B?? How to make it appear?

see here we have 6 batch jobs for recurring job (3 for processing and 3for monitoring) -- they yellow ones are the copied ones

but in manage recurring data jobs, i only see the two i created manually in Company A and Company C and not the one i copied from the batch job form for Company B, why?

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

André Arnaud de Cal... 303,105 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi,

For this scenario, you should not copy the batch job. There is more details initialized when starting recurring batch jobs. Copying the batch job is useful in case of e.g. changing owner of the job.

Was this reply helpful? Yes No
CU22120935-0 150 on at

Like (0)

Report
Copy link

Link copied!

Hi Andre, @André Arnaud de Calavon

And in case of changing the owner of the job, i should delete the old one?

but when copying the batch job, we also have the option to create it in another legal entity.. so in which cases (business scenario) i would copy the batch job in another legal entity if it's not in the case of recurring jobs?

Was this reply helpful? Yes No
André Arnaud de Cal... 303,105 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi,

Yes, when you copy a job to change the owner, you can delete or disable the batch job by changing the status to withhold.

In this case for the recurring data jobs it is not sufficient to only copy the batch job. So, the recommendation is to create a new recurrence job.

Was this reply helpful? Yes No
Suggested answer

Navneeth Nagrajan 2,495 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @CU22120935-0,

As Andre rightly mentioned, you shouldn't copy recurring integration batch jobs. The reason is the settings from the source batch job are copied into the new batch jobs and this causes an issue when you run the new batch job.

No need to delete the old batch job. Create a new batch job with the application id and the authorization policy. Run it manually once and see if the job is queueing the oubound jobs with the expected requests. Secondly, in the screen clip below that you share you need to first uncheck the second Customer Group Managed scheduled data jobs and keep the first option active. If you are using Logic Apps for integration then would recommend setting up a schedule in Logic Apps instead of D365 FO. Its easier to manage the recurring schedules in Logic Apps than in D365 FO.

This issue also occurs when you do a platform upgrade from the existing version to a newer version so would recommend following the steps mentioned above. The batch jobs tend to cache and create multiple monitoring recurrence.

Hope this helps. Happy to answer questions, if any.

Was this reply helpful? Yes No