Jobs
Last updated
Last updated
Jobs are specific tasks which are executed on a time schedule. There are many types of jobs, and a single tenant could have many jobs configured. Not all types of jobs are configurable yet; and the configuration of jobs does still require some good knowledge of the system.
Warning
The job configuration is not fool proof.
Do not create or modify jobs without being trained properly first.
You find the job configuration section in the “Jobs” tab.
There is a list of all the configured jobs, including the job type, the schedule, status, etcetera.
When selecting a job, the details wil become visible on the right side.
Below image gives a general idea
In the example a job of type “D365FO Taxonomy” is selected.
In the list itself we see that the status is Failed (because of the red circle next to the job), and we see it last executed on 08-02-2022 around 13:44. We can also see that is should be executed once every 24 hours (because of the cron schedule).
On the website crontab it is possible to replace the job schedule values. It is also possible to see the interpretation.
In the details section on the right, we can see that from top to bottom:
That the job is of type “Taxonomy Sync” for a “D365FO” source.
That the job is enabled. (see checkbox next to “Deactivate” at the top.)
That we cannot manually trigger this type of job. (the “Trigger” button next to the “Enabled” checkbox is greyed out.)
That the job (should it be active) will run using the “D365FO-DEV admin” user.
That the job uses a packager with id 38ec….
The job’s execution history. In this case: the job executed at least twice, and that it failed both times. (You see max 10 history records, and successful jobs are removed after some time)
Most jobs have more configuration options, but this particular job type is not yet supported by the web UI.
Normally each job should have at least following information in the detail section:
Type of job, Enabled / Disabled & Manual trigger, run-as user, history.
Everything else is optional and depends on the type of the job.
Used to create tags based on data from an external system.
Requires information about the source, and information on how the map the result to tags.
At the moment there are jobs available for “D365-FO”, “D365-BC”, and “D365-CE”.
User sync:
This job is used to create new users based on a set of users already available in another external system. For the moment there is only a user sync available for D365-FO. This job requires information to connect with the FO environment, and the name of an Export Package in FO that contains the users. This job also requires some mapping information to define which part of the data maps to the user id, the email of the user etcetera.
This job allows to export data from an external system, and make it available in an SQL database.
It requires information about the source. (how to log in, where is the web service, …) and information on how to create a primary key for each record in the extracted dataset.
It is possible to delete the “old” data before syncing, or to do an “add or update” sync.
It also adds a few extra columns like a timestamp, the primary key etcetera.
It automatically creates new columns if the package contains more data.
All data is stored in Nullable NVARCHAR(max) columns.
