web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance forum / DMF-recurring import job
Finance forum

DMF-recurring import job

(0) ShareShare
ReportReport
Posted on by AskForum 15

Hi,

I am new to D365FO. I want to create Import project to import Customer entity data from datapackage. When I click on Create Recurring data job, after entering Name, description and batch group. Click Save it gives error message:

At least one client id must be enabled for the recurring data job before it can be activated.

Intention is run import job, on a recurring schedule to import from specified local folder. 

Still we need to specify "Application ID" in "Setup authorisation policy"?

Looking for your guidance.

Thanks.

Categories:
Data Integration
I have the same question (0)
  • MATTGUO Profile Picture
    MATTGUO 22,349 Moderator on at

    Hi AskForum,

    Refer to links:

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

    www.loganconsulting.com/.../

  • AskForum Profile Picture
    AskForum 15 on at

    Thanks Mattguo.

    Some following question to confirm my understanding.

    1. If we create Data import project and want it as Recurring then there are only two options 1. Data Management Package API and 2. Recurring integration scheduler. Can we not just use recurring within D365FO to import on a schedule from local folder?

  • MATTGUO Profile Picture
    MATTGUO 22,349 Moderator on at

    Hi,

    I cannot find current version support it.

  • AskForum Profile Picture
    AskForum 15 on at

    Just to confirm , what I understand : Using recurring within D365FO to import on a schedule from local folder is not supported in this version?

    we can only use DMF- Import project to manually import. If we want this to run in background using "Create Recurring data job" option then it should be linked to an Application ID. Only external applications can call these recurring data job?

    Please seniors confirm this.

  • Frank Bruemmer Profile Picture
    Frank Bruemmer 354 on at

    Hello,

    the problem is that while your ad hoc import uploads a file from your local machine, the recurring integration does not have access to your local machine. And you don't have access to the file system of the AOS which executes the import/export job. You also don't necessarily know which AOS - there is likely more than one - will pick up the job. You can no longer have a client session running on an aos executing batch jobs as you used to in previous releases.

    The only solution that I'm aware of is to use the recurring integration scheduler which runs stand-alone on an external environment where you have accessible folders for dropping and retrieving files. It connects to the DMF jobs via web service and submits the files it picks up. You can import single files or packages including a manifest (required for dependencies).

  • AskForum Profile Picture
    AskForum 15 on at

    Great explanation. Thanks for your help - Frank Bruemmr 

    [quote user="Frank Bruemmer"]

    Hello,

    the problem is that while your ad hoc import uploads a file from your local machine, the recurring integration does not have access to your local machine. And you don't have access to the file system of the AOS which executes the import/export job. You also don't necessarily know which AOS - there is likely more than one - will pick up the job. You can no longer have a client session running on an aos executing batch jobs as you used to in previous releases.

    The only solution that I'm aware of is to use the recurring integration scheduler which runs stand-alone on an external environment where you have accessible folders for dropping and retrieving files. It connects to the DMF jobs via web service and submits the files it picks up. You can import single files or packages including a manifest (required for dependencies).

    [/quote]

    Now, I get it, why "recurring integration scheduler" is an option to run recurring DMF- Import projects.

    Please clear this doubt as well - On the DMF - Import Job, Import Options , there are three options,

    1. Import now

    2. Import in batch

    3. Re-import.

    Would like to know 2. Import in batch. how this is different to recurrance created by using "Create recurring data job" please?

  • Verified answer
    Frank Bruemmer Profile Picture
    Frank Bruemmer 354 on at

    Not really sure what your are referring to. It's been since January since I used this but this is running at the client since. The general idea is that the batch processing is moved outside of D365. In D365 you just need to have the jobs present. The scheduling / execution is completely done outside D365 in RIS. You will need to have the import job name match exactly. Keep in mind that you will need one job per company account / legal entity. All you really have to do is to create the (import) job in D365, write down the name and have the file picked up and sent over to D365. Ideally, if you use a package, the manifest takes care of exact file names and mappings - settings in the job will be overriden. You can create these templates easily when setting up the job.

  • Verified answer
    Martin Dráb Profile Picture
    Martin Dráb 237,884 Most Valuable Professional on at

    There are two APIs for file imports. One, the older, merely uploads the file and waits for a job in AX to pick it up and do the import. If you use this older API, you must set up the batch in AX, otherwise nothing would be imported.

    The newer API assumes that scheduling is done outside the ERP system. When you import a file, it's imported straight away. It means that you don't need any batch in AX, but you must do some kind of scheduling for calling the API.

    The Recurring Integrations Scheduler application supports both APIs, therefore you can decide which one you want to use. Depending on your choice, you need or don't need to set up the batch in AX.

  • AskForum Profile Picture
    AskForum 15 on at

    Thanks - Frank Bruemmer - for explanation and your patience.

    I get it now, for recurring DMF - Data Import projects, Recurring Integration Scheduler(RIS) is the way to go. As I understand, this will move files from on-premise to D365FO directly.

    If the situation is such that application that is creating source files, is writing to a folder/location that is in Azure Data Factory/Azure Storage, then we should still use RIS? please suggest.

  • Martin Dráb Profile Picture
    Martin Dráb 237,884 Most Valuable Professional on at

    There is nothing in F&O itself for reading from generic folders - that's what RIS is for.

    F&O exposes APIs, but you need something calling these APIs and Microsoft provided RIS as an example how you can implement an application reading files and calling these APIs. As mentioned, there are two APIs for this purpose, both supported by RIS. By the way, RIS has a wiki which may answer some of your questions.

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

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Coming on 11/8!

In our never-ending quest to help the Dynamics 365 Community members get answers faster …

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard > Finance

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans