Ahmed Kamel Support Engineer

In Automatic release of sales orders, it is not possible to exclude partially released sales orders. There is a parameter to not include the sales orders that are partially released, but the query does not exclude the orders. The problem is that the batchjob tries to release the sales orders, but it can’t, and the error log contains all the errors.

In telemetry all these are recorded as errors and there is no possibility to exclude these in the query.

that The Allow release of partially released orders parameter determines whether orders in the batch should be accepted or rejected if they were partially released earlier, so it’s a normal behavior of the system to throw the warning message telling you that this order hasn’t been released to warehouse as it’s partially released earlier

The behaviour of the batch job is indeed correct, but the error message in a batchjob is not a good design.

Batch jobs in D365 does not like errors and they do not perform the same when they report errors.

Telemetry data does not like error message and error messages as this one should be avoided to not create bias data.

Expected behavior

The batch job should have skipped orders that are partially released (as it does) and not create a error message in the batch job 

There’s an issue with the configurator where the OK button becomes grayed out after a few minutes of inactivity. This is particularly frustrating, especially during complex configurations when we need to keep the configurator open while gathering information from other systems.

To improve usability, we request that the configurator’s idle timeout be extended to accommodate longer periods of inactivity.