Customization DS1045
Auto-set PO Buyer ID
Problem Definition
Acme needs to make the Buyer ID required on PO Entry. This requirement has been met by modifying the PO Entry window. However, that modification only applies when POs are created in the PO Entry window. Acme uses Dynamics GP Field Service.
Acme also needs the Buyer ID to be populated for PO’s coming from the Service Call Parts and Additional Charges windows.
Design Features
Acme’s Buyer IDs are always the same as the GP User ID.
When a PO is created from Field Service, the enhancement will:
- Check that the GP User ID, in upper-case, exists as a Buyer ID in GP. If not, it will create a Buyer ID based on the User ID and User Name.
- Update the Buyer ID on the PO Header created by Field Service
Assumptions/Requirements
The functionality described in this document is intended for the Dynamics GP desktop client. Unless specified otherwise, all testing will occur in the desktop client only. Projects created in Dexterity should have a very high level of compatibility with the Web Client, but cannot be guaranteed without explicitly including additional time in the estimate for testing in the Web Client.
If you are interested in this customization, or any other design spec or product, please contact us at:
Customization DS1045
Auto-set PO Buyer ID
Problem Definition
Acme needs to make the Buyer ID required on PO Entry. This requirement has been met by modifying the PO Entry window. However, that modification only applies when POs are created in the PO Entry window. Acme uses Dynamics GP Field Service.
Acme also needs the Buyer ID to be populated for PO’s coming from the Service Call Parts and Additional Charges windows.
Design Features
Acme’s Buyer IDs are always the same as the GP User ID.
When a PO is created from Field Service, the enhancement will:
- Check that the GP User ID, in upper-case, exists as a Buyer ID in GP. If not, it will create a Buyer ID based on the User ID and User Name.
- Update the Buyer ID on the PO Header created by Field Service
Assumptions/Requirements
The functionality described in this document is intended for the Dynamics GP desktop client. Unless specified otherwise, all testing will occur in the desktop client only. Projects created in Dexterity should have a very high level of compatibility with the Web Client, but cannot be guaranteed without explicitly including additional time in the estimate for testing in the Web Client.
If you are interested in this customization, or any other design spec or product, please contact us at: