Minimum Version Required: 25.11
Steps
Grist Integration Troubleshooting
The success of the Grist integration relies on precise data mapping and exact matching between Grist events and Encompass records. If the import encounters unmapped or missing data, it may result in a partial import or fail entirely.
Location and Recipe Errors
Error Message:
Cannot find Location: xxxxxxx; Cannot find Recipe: xxxxxxx.
Cause: A Location or Recipe/Plan value in the Grist file does not have a corresponding mapping in Encompass.
Resolution: Use Table Translations to map the Grist Location or Recipe to the correct Encompass Location or Recipe Version. Once mapped, re-import the file.
Product Mapping Errors
Error Message:
Cannot find Product: xxxxxxx.
Cause: An ingredient name in the Grist event cannot be resolved to a Product ID in Encompass.
Resolution: Map the Grist Ingredient name to the appropriate Encompass Product via Table Translations and re-import.
Note: Ensure a 1:1 mapping; the system cannot resolve two Grist ingredients to one Encompass product.
Batch and Lot Number Issues
Batch Matching: The system uses Batch Number and Lot Number as primary keys. These must match textually exactly.
Missing Batch Match: If a Batch Number cannot be matched, Encompass will create a new Production Order rather than updating an existing one. No specific error message is provided for this condition.
Lot/Batch Code Error:
Product XXXXX with Batch Code CCCCC not found.
Cause: The system cannot find an inventory layer (Purchase Transaction) matching the Lot # provided by Grist.
Logic: If the specific Lot # isn't found, the system defaults to the oldest inventory layer (FIFO).
Failure: If no inventory layer exists at all (zero inventory), the component will not be imported.
Resolution: Re-open the PdO and manually enter the ingredient amount and batch.