13
In process industries and especially in pharmaceuticals, it is MANDATORY that any change in batches is logged correctly.
However, when using a mobile device to change a disposition code, D365 replaces the user name by an "Admin" user. The Android WHS App connects to D365FO using OAuth 2.0 with an azure application id, mapped as a single D365FO user. This means that all activities performed by the external system are recorded in the system as the mapped user. This behavior is currently the same for ALL integrations that use this pattern.
All modifications performed from the D365 GUI are correctly reported, while when using a mobile device it is not.
D365 offers 2 separate log tables related to this topic :
A first which captures all actions performed with a mobile device, the Mobile Device Activity Log (Warehouse Management > Inquiries and reports). It indicates for each entry the work processing mode and details of the action performed item number, license plate, etc.)
A second log displaying the history of disposition coders on a batch, the Batch Disposition History (Inventory Management > Inquiries and reports > Batches). It reflects the complete history of changes of disposition code on a batch.
The idea would be to combine both log files and reflect a change in disposition code executed by a mobile device user into the batch disposition history with the associated D365 user ID.
However, when using a mobile device to change a disposition code, D365 replaces the user name by an "Admin" user. The Android WHS App connects to D365FO using OAuth 2.0 with an azure application id, mapped as a single D365FO user. This means that all activities performed by the external system are recorded in the system as the mapped user. This behavior is currently the same for ALL integrations that use this pattern.
All modifications performed from the D365 GUI are correctly reported, while when using a mobile device it is not.
D365 offers 2 separate log tables related to this topic :
A first which captures all actions performed with a mobile device, the Mobile Device Activity Log (Warehouse Management > Inquiries and reports). It indicates for each entry the work processing mode and details of the action performed item number, license plate, etc.)
A second log displaying the history of disposition coders on a batch, the Batch Disposition History (Inventory Management > Inquiries and reports > Batches). It reflects the complete history of changes of disposition code on a batch.
The idea would be to combine both log files and reflect a change in disposition code executed by a mobile device user into the batch disposition history with the associated D365 user ID.
STATUS DETAILS
Needs Votes