Schedule Ferli updates
An administrator can use the job queue to retrieve an update file and update customers and vendors without manual import. Use this after a manual file retrieval succeeds and you have verified its effects on cards.
Purpose
A recurring run retrieves the Ferli update file and applies its information to matching cards. It does not wait for a user's approval.
Prerequisites
File-based integration must be fully configured and Data source set to File. Choose a frequency that matches when Ferli update files are available.
Permissions needed
The user running the process needs permissions for the job queue, the connection and the customer and vendor cards being updated.
Steps
- Open job queue entries in Business Central and create a new entry.
- Select the object to run according to the table.
- Configure recurrence, days, starting time and the interval between runs. The schedule must suit Ferli's file delivery.
- Set the entry ready to run and monitor its first execution.
| Job queue | Value |
|---|---|
| Object Type to Run | Codeunit |
| Object ID to Run | 10042266 |
| Object name | RdN NR Azure Function |
Verify it works
Check the job queue entry's run history and open Update Logs from National Register Setup. This shows the numbers of updated customers and vendors. Also verify the result on one card.
With Do not store any data, cards can be updated even though no new rows are retained in the register list. Save Fetched Files independently controls whether a copy of the file is retained.