Product: Dynamics 365 Business Central
Article Link: https://help.truecommerce.com/en/articles/16148097-dynamics-365-business-central-filtering-imports-by-user-defined-fields
You can configure your Transaction Manager Import search criteria to only import documents from Dynamics 365 Business Central based upon a User-Defined Field string. Allowing you to dynamically filter based on the value within that User-Defined Field.
This will work across any Import Document such as your Invoice, Shipment, or a Sales Order when generating EDI Documents to be sent to your Trading Partner. Often used to help filter between EDI Created Documents and Non-EDI Created Documents when generating fulfillments from methods outside of the TrueCommerce Transaction Manager platform.
Configuring a User-Defined Field
Transaction Manager will search against the Header level User-Defined Fields located under the TrueCommerce Tab that get bundled with the TrueCommerce Extension. These fields are automatically transferred over into the Invoice or Shipment when being posted from a Sales Order with that existing User-Defined Field Filled out.
The TrueCommerce Extension by default adds 10 User Defined Fields that can be utilized by your company to pass data that does not have a pre-defined field, insert information through custom-scripts, or be used for filtering when importing documents into Transaction Manager.
User-Defined Fields can be given custom labels within Business Central. As your team assigns out various User-Defined Fields it is recommended that you provide labels for them.
Manually Entering a User-Defined Field
You can manually modify a Sales Order's User-Defined Field by locating the Sales Order and navigating to the TrueCommerce group for that order and entering in a value for that field manually.
Locate: The Desired User-Defined Field
Enter: Value manually
Entering UDF Value on Sales Order
Token Mapping
If you have access to the Mapping Manager add-on to Foundry - you can utilize the Token Mapping screen to either hard-code a value or map a token from the inbound Purchase Order (850) to any of the UDF fields to have it automatically map upon creation of the Sales Order when exporting out of Transaction Manager for a specific Trading Partner.
If you do not have access to Mapping Manager or wish to have the UDF mapped for ll Trading Partners - you can submit a Support Ticket to have our team add the logic on your behalf
Navigate: Mapping Manager → (Project) → Edit
Select: Purchase Order (for corresponding Trading Partner)
Select: Edit
Row/Column Selection: Select SalesOrder from the Dropdown
Search Elements: Enter UDF
Select: Desired UDF
Enter: Value
Save
Deploy
Mapping Manager - Hard-Coding UDF
When attempting to create a system to filter between EDI and non-EDI Orders. TrueCommerce Recommends utilizing mapping the keyword 'EDI' into the desired User-Defined Field to help identify all documents created via the Transaction Manager EDI System
Filtering Imports by User Defined Fields
Once the User-Defined Field (UDF) is populating with the desired keyword inside your Sales Orders, Invoices, or Shipments you can then apply the filter within the Transaction Manager search criteria window - and even save the search for future use with Scheduler or repeated manual searches.
If you do not apply a UDF filter, the search will return all documents of the selected type — including non-EDI invoices.
It is strongly recommended to configure and use a UDF filter if your Business Central environment contains both EDI and non-EDI records.
Navigate: Transactions → Outbox → Import
Locate: UDF Name Search Filter
Enter: UDF# (The # corresponds to the UDF you chose)
Locate: UDF Value
Enter: Desired keyword to filter by (multiple values accepted separated by a semicolon)
UDF Search Criteria
Note: The Search does not utilize your custom label when searching. You will need to enter the UDF# as it's shown inside the UDF Caption Setup screen or Mapping Manager
Search Results - Filtered by UDF4
UDF Value (semicolon delimited)
You can provide multiple values to search against separate them by a semi-colon within the UDF Value input box.
Example: EDI — returns only records where UDF1 equals "EDI"
Example: EDI;NEDI — returns records where UDF1 matches either value
Additional Resources
rev 08/20/2026