Product: Dynamics 365 For Finance and Operations
When a Purchase Order (850) is received in Transaction Manager, not every EDI Segment within that transaction is automatically included in the XML file consumed by Dynamics 365 For Finance and Operations. The Transaction Manager Defaults allow you to define which EDI Segments are pushed from the received Purchase Order (850) into that XML — giving you direct control over what data lands in Finance and Operations upon export.
Each Default Lookup value corresponds to a conditional check built into the Export Definition within Mapping Manager. These conditions evaluate the qualifier value entered in the Default, and when a match is found on the incoming EDI Segment, that segment is included in the exported XML.
Any modifications to the conditions themselves require TrueCommerce Support.
Configuring Which EDI Segments to Export
You will need to configure the EDI Segments for each Trading Partner separately within Transaction Manager so that it knows which data to map onto the XML file that is sent to Dynamics 365 for Finance and Operations. You can make these configurations within the Defaults screen of your Trading Partner settings.
Navigate: Trading Partners → (Trading Partner) → Translations → Defaults
Find: Desired Export Option
Enter: Qualifier or YES for desired Option
Save
Tip: You can view the Raw EDI of a received transaction by navigating to the Inbox or Received folder in Transaction Manager to identify which qualifier values your Trading Partner is transmitting.
Export Options
The following Default Lookups are driven by qualifier values. When the qualifier on an incoming EDI Segment matches the value entered in the corresponding Default, that segment is exported into the XML.
To enter a value, type the qualifier code directly into the Default Lookup field. To include multiple qualifiers, separate each with a comma (e.g., ST, BT).
Default Lookup | Qualifier Field Evaluated | Notes |
Export DTM | DTM01 | For the Grocery Products Purchase Order (875), use qualifier G6201 |
Export N1 | N101 | Example: Enter ST, BT, or ST, BT to export one or multiple N1 Segment types |
Export N9 | N901 | Enter the qualifier found in the N9 Segment transmitted by your Trading Partner |
Export PER | PER01 | Enter the qualifier found in the PER Segment transmitted by your Trading Partner |
Export REF | REF01 | Enter the qualifier found in the REF Segment transmitted by your Trading Partner |
SDQ-Based Default Lookups
The following Default Lookups control the export of SDQ Segment loops. Unlike qualifier-based defaults, these are activated by entering a value of YES — enabling the corresponding SDQ loop to be included in the exported XML.
Default Lookup | Value to Enable |
Export SDQ Item Loop | YES |
Export SDQ Kit Loop | YES |
Export SDQ Pack Loop | YES |
Export SDQ Reference Loop | YES |
Export SDQ References Loop | YES |
Export SDQ SDQ Loop | YES |
Each Trading Partner Map is unique in its definitions. You may need to have our Support Team adjust the integration's backend configuration to properly align with your Trading Partner Map's definitions. Please open a support case for any required changes to the Export Definition conditions.
rev 07/30/26