Payment Entity
Below you can find information about the changes to the field mapping used for the Payment entity in MYOB Acumatica. These changes were introduced as part of MYOB Acumatica's alignment with Shopify's migration from the REST API to GraphQL.
In the Fields Unavailable in GraphQL section, you'll find a list of all the fields used for entity mapping that are not supported in GraphQL but were available in the REST API.
Payment Mapping
In the Shopify_GraphQL_Payment.xlsx file, you can find the mapping of MYOB Acumatica fields on the Payments and Applications (AR302000) form to Shopify default and custom fields. The system uses this mapping during the export, import, and bidirectional sync of the payment data to Shopify.
Particularly, you can see how each MYOB Acumatica field was previously mapped to Shopify fields through the REST API, and how it's now mapped using GraphQL.
Fields Unavailable in GraphQL
The following table lists the fields that were:
- Used for the import mapping and filtering of the Payment entity on the Entities (BC202000) form
- Supported by the Shopify connector with the REST API, but not with GraphQL
| Tab on the Entities Form | External Object | External Field | REST API Object | REST API Field |
|---|---|---|---|---|
| Import Mapping, Import Filtering | Order Transaction | Device ID | transaction |
DeviceId |
| Import Mapping | Order Transaction | Message | transaction |
Message |
| Import Mapping | Order Transaction | Receipt | transaction |
Receipt |