Skip to main content

Using the Grist Integration

Brewery steps to export Grist events and import them into Encompass Production Orders via the Grist Analytics PdO Import dashboard, plus recipe and Table Translations setup. Requires v25.11+.

B
Written by Bailey Naas-Thornton

Minimum Version Required: 25.11

Pre-Conditions

System Setting: Ensure System Setting 3353 is updated with the correct EDBL Source ID (recommended label: "Grist").

Recipe Configuration:

  • Naming: Recipe Version names must contain the keywords “Brewhouse” or “Cellar” to facilitate matching.

  • Structure: Each Recipe Version must contain only a single Recipe Stage.

  • Method: Set Turn Config Method to Recipe for brewing stages to support multi-turn data.

  • Table Translations: Ensure 1:1 mappings are established for Locations, Equipment, Products (Ingredients and Output), and Brands.

Steps

How to Export & Import Grist Events:

1. Export Data from Grist

  1. Navigate to Export Data in the Grist left-hand menu.
    ​
    ​

  2. Select the Encompass Export tab.
    ​
    ​

  3. Select the desired date range (e.g., "Today") and click Export Data.
    ​
    ​

  4. Grist will generate a ZIP file (compressed) containing 2 JSON files (Grist_Data_Export.zip) to your local computer.

2. Prepare the Files

  1. Click on the download ZIP file. This will create a folder with the same name as the ZIP file containing the 2 JSON files (Grist_Cellar_Export.json and Grist_SubBatchTransferToCellar_Export.json)
    ​
    ​

  2. Identify the specific file containing the SubBatchTransferToCellar event for Brewhouse activities.
    ​
    ​

  3. Rename the files using the download date and a counter (e.g., Grist_SubBatchTransferToCellar_20250623_1.json) to easily identify it during the upload.

3. Import into Encompass

  1. Navigate to the Grist Analytics PdO Import dashboard using Universal Search.
    ​
    ​

  2. Select the Brewhouse tab.
    ​
    ​

  3. Click Upload Files and select the renamed JSON file from your computer.
    ​
    ​

  4. Click Process to begin the import.
    ​
    ​

  5. Result: Encompass will match the data to an existing Production Order or create a new one, populating quantities and marking the Production Order as Completed.

4. Repeat steps for the Cellar export (note: in beta testing)

Encompass will update existing, unverified Production Orders based on the below matching criteria, otherwise new Production Orders will be created if a suitable Recipe Version is found.

  • ProductionOrder.Batch = Grist Event.BrewhouseBatch or Event.CellarBatch, AND

  • ProductionOrder.RecipeVersion.Brand = Grist Event.Recipe/Plan, AND

  • ProductionOrder.Location = Grist Event.Location, AND

  • ProductionOrder.RecipeVersion.RecipeVersion (name) contains: “Brewhouse” if the Event is a Brewhouse event, or “Cellar” if the Event is a Cellar event

Fields And Definitions

  • EDBL Source ID: A unique identifier used to map Grist data into the Production Cloud.

  • Table Translations: A tool that pairs local Encompass IDs with Grist names, allowing the two systems to communicate even if naming conventions differ.

  • Batch Number: The primary key used to match Grist events to Encompass Production Orders. These must match textually exactly.

  • SubBatchTransferToCellar: The specific Grist event type that triggers the Brewhouse data import.

  • Lot # / Batch Code: Values passed from Grist to select the specific inventory layer in Encompass. If a match is found, that layer is depleted; if not, the system defaults to FIFO.

Best Practices

  • 1:1 Mapping: Ensure every ingredient in Grist maps to exactly one product in Encompass. Avoid "many-to-one" or "one-to-many" mappings as the import cannot resolve them.

  • Explicit Mapping: Map all shared data items even if names are identical. This prevents the integration from breaking if an Encompass record is renamed later.

  • Import Frequency: Export and import data no more than once per day to prevent redundant processing of events.

  • Naming Uniqueness: Ensure equipment names (like "FV01") are unique across all locations in Grist to prevent resolution errors in Encompass.

Did this answer your question?