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 :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Recurring integration ...
Microsoft Dynamics AX (Archived)

Recurring integration scheduler doesn't work for import. Any solution?

(0) ShareShare
ReportReport
Posted on by Community Member

Hi all,

I have tried to import a CSV file using Recurring integration scheduler, following the steps mention on GitHub (https://github.com/Microsoft/Recurring-Integrations-Scheduler/wiki).

Unfortunately, the CSV file moves to UploadErrors folder with another status file.

When I have checked the event viewer, I found the following message:

RecurringIntegrationsScheduler.Job.Import - Job: Import jobs.Customer group import. Upload failed for file: C:\Integration\Input\CustGroup01.csv. Failure response: Status: BadRequest, Reason: Bad Request

What could be the solution or workaround for it?

Thanks in advance!

*This post is locked for comments

I have the same question (0)
  • Martin Dráb Profile Picture
    Martin Dráb 239,147 Most Valuable Professional on at

    I assume you're looking to event logs for RIS. Try Applications and Services Logs > Microsoft > Dynamics > AX-OData Service as well.

  • Community Member Profile Picture
    Community Member on at

    Thanks Martin for your suggestion. I have checked the error message at the path you have suggested. I can see the below error message:

    ComponentName ODataService

     exceptionMessage System.InvalidOperationException: Exception occurred while executing action ImportFromPackage on Entity DataManagementDefinitionGroup: The file 'C:\windows\TEMP\D5309805-1C3E-4955-BD29-59B8FCD156C0_8FB2B40A-15B2-4A35-AD4F-759C96EB81FA\Customer groups.csv' already exists. at Microsoft.Dynamics.Platform.Integration.Services.OData.Action.ActionInvokable.Invoke() at Microsoft.Dynamics.Platform.Integration.Services.OData.Update.UpdateProcessor.ActionInvocation(ChangeOperationContext context, ActionInvokable action) at Microsoft.Dynamics.Platform.Integration.Services.OData.Update.UpdateManager.<>c__DisplayClass13_0.<ScheduleInvokable>b__0(ChangeOperationContext context) at Microsoft.Dynamics.Platform.Integration.Services.OData.Update.ChangeInfo.ExecuteActionsInCompanyContext(IEnumerable`1 actionList, ChangeOperationContext operationContext) at Microsoft.Dynamics.Platform.Integration.Services.OData.Update.ChangeInfo.ExecuteActions(ChangeOperationContext context) at Microsoft.Dynamics.Platform.Integration.Services.OData.Update.UpdateManager.SaveChanges() at Microsoft.Dynamics.Platform.Integration.Services.OData.AxODataDelegatingHandler.<SaveChangesAsync>d__2.MoveNext()

     infoMessage An exception occured while calling SaveChanges on the UpdateManager.

  • Verified answer
    Martin Dráb Profile Picture
    Martin Dráb 239,147 Most Valuable Professional on at

    Great, you see that event logs do contain the actual error message after all.

    It may be the same problem that I documented in Recurring Integrations Scheduler: File already exists.

  • Community Member Profile Picture
    Community Member on at

    Thanks again Martin. It has worked after following your instruction mentioned on your blog. The .csv file is being processed and also imported into D365FO. But I am not sure why there is no inbound message showing up in scheduled data job which I had created in D365 for Customer group import. Isn't it abnormal?

    Though, I can see the import information in job history.

  • Verified answer
    Martin Dráb Profile Picture
    Martin Dráb 239,147 Most Valuable Professional on at

    The package API doesn't use any batch in AX. I think you're referring to the old API, which used to use batch jobs in AX, but that's not what you're utilizing right now. The Recurrence Integration Scheduler supports both; notice that it distinguishes "import jobs" (using the new API) and "upload jobs" (using the old one).

    Please don't forget to mark the verified answer.

  • Community Member Profile Picture
    Community Member on at

    Thanks a lot!!! :)

  • Community Member Profile Picture
    Community Member on at

    Hi Martin,

    We are facing similar issue, the file is moved from input folder to upload success folder. But the batch job is still in waiting state, its not executing.

    What might be the issue?

    Regards,

    Manivannan M

  • Martin Dráb Profile Picture
    Martin Dráb 239,147 Most Valuable Professional on at

    Aren't you using the new API which doesn't use any batch job at all (as discussed above)?

  • Community Member Profile Picture
    Community Member on at

    We have created a recurring batch job in AX. But it is not executing.

  • Martin Dráb Profile Picture
    Martin Dráb 239,147 Most Valuable Professional on at

    You didn't answer my question.

    I'm saying that if you use the API that doesn't use any batch, you shouldn't have created one because it's not used at all.

    Please realize that we can't help you if you don't tell us what you're doing. Start with explaining which API you're using.

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 > 🔒一 Microsoft Dynamics AX (Archived)

#1
CP04-islander Profile Picture

CP04-islander 16

#2
GiacomoRovai Profile Picture

GiacomoRovai 4

#3
Douglas Noel Profile Picture

Douglas Noel 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans