-
Reintroduce date handling in report filtering known from previous versions
In previous AX versions we could type in ranges like D-1 for yesterday in reports to get yesterday. Very handy in e.g. batch execution of jobs. This seams to be disabled in Dyn365.
-
Ability to disable "Device token lifetime" feature or measure by activity
Not everybody is interested in automatic disabling of the POS's. It would be a more relevant to measure when to disable based on inactive time. E.g. if a POS hasn't been active for 180 days disable it instead of having us reactivate in a given frequency.
-
Copy register settings shouldn't overwrite offline database name
When creating a new register you can use the copy all function to add settings from another register. It also overwrites the offline database which can add some inconsistency. -
Copy batch job function should respect selected company in the tasks
Batch jobs can be copied from the enhanced batch form. However if a batch job consists of multiple tasks and these tasks has different companies specified they are all overwritten when copying. The expected behaviour would be to either 1. warn about this and allow the user to abort 2. respect the selection and keep the selected companies. -
Increase length of Data area id
Increase dataareaid from 4 to e.g. 6 or even 10 char. We're frequently running into situations where it's hard to create logic and readable 4 character abbreviations. -
Allow "Synchronize orders" and "Validate store transactions" to run across legal entities.
Both "Synchronize orders" and "Validate store transactions" jobs allow selection of channels using the hierarchy but can only run for channels in the current legal entity.
This means that you need to create the jobs in the batch queue per legal entity instead of grouping them into e.g. regions or one job for all legal entities.
You’re offline. This is a read only version of the page.
