The error “{{# each data}} not found in the template.” is encountered when creating file for FTP transfer. Solution: It’s the validation to have an each loop specifically for the batch_of_records. To solve the issue, Update the handlebar as below. Also set page size to 1 in Export step and skip aggregation set to true… Continue reading Fix the error {{# each data}} not found in the template.
Category: Celigo
EDI x12 Format
The EDI X12 format is a standardized format used for electronic data interchange (EDI) to automate and streamline B2B communication. Celigo’s integrator.io platform supports the EDI X12 file type format and provides various tools and features to facilitate the exchange of business documents with trading partners. Key Features and Processes of EDI X12 in Celigo… Continue reading EDI x12 Format
EDI 997 Functional Acknowledgement flow – Celigo
The 997 functional acknowledgment (FA) flow in Celigo’s integrator.io is a process that confirms the receipt and integrity of EDI transactions between trading partners. Here’s a detailed explanation of the flow: Purpose of Functional Acknowledgment (997) A functional acknowledgment is a receipt issued by the receiver in response to a transaction sent by a trading… Continue reading EDI 997 Functional Acknowledgement flow – Celigo
Exclude the JSON row structure from files
When creating the JSON files the JSON data is enclosed in square brackets. The opening and closing square brackets are the defining characteristics of a JSON row structure. When we group the export data, the data passes through the rest of the flow in row structure. These square brackets can be removed by using the below… Continue reading Exclude the JSON row structure from files
Handlebar syntax for curly braces
{{ }} – Handlebars double-braces will URL encode characters that are able to be URL encoded. The double-braces themselves do not display in output (escaped). For example, you could use double-braces for an HTTP URI. This would automatically perform the URL encoding for any escaped characters (such as <, > , or space). In the… Continue reading Handlebar syntax for curly braces
Lookup Caches in Celigo
The new lookup caches functionality enables builders to create in-memory lookups that can be easily repurposed throughout their flows. With lookup caches, you can: Create in-memory lookups that can be reused across multiple flows. Load and maintain reference data manually or within flows through a new integrator.io API Store and retrieve data using a key-value pattern. Set… Continue reading Lookup Caches in Celigo
Diff checker for Celigo AI responses
Diff Checker in Celigo’s AI Prompt Window, enables users to review changes quickly and efficiently. This feature highlights removed lines in red and added lines in green, similar to GitHub’s diff checker. Diff Checker is accessible within both the Flow-Builder and Playground views. The following editors are supported in both the Flow-Builder and Playground views: Handlebars… Continue reading Diff checker for Celigo AI responses
EDI 850 (Purchase Order) document in X12 format
SA Segment (Interchange Control Header) The ISA segment is the envelope for the EDI document, defining communication details between the sender and receiver. ISA01 (Authorization Information Qualifier): 00 – No authorization information present. ISA02 (Authorization Information): Blank – Not used in this document. ISA03 (Security Information Qualifier): 00 – No security information present. ISA04 (Security… Continue reading EDI 850 (Purchase Order) document in X12 format
Celigo platform 2025.1.1 release notes
The January 2025.1.1 Release introduces significant advancements across the Celigo platform, reflecting our commitment to equip builders with innovative tools to create powerful workflows and integrations. With a focus on AI enhancements, connectivity improvements, platform upgrades, and marketplace advancements, this release scales automations and accelerates business efficiencies for builders. AI code assistant for GraphQL Ready to accelerate your use of GraphQL?… Continue reading Celigo platform 2025.1.1 release notes
Errors while converting special characters from JSON to EDI
Q: While performing a JSON to EDI conversion, I am unable to convert special characters and a “<” symbol appears as “<”. What is the workaround? A: You are requested to use {{{[ ]}}} in the Definition File while converting the JSON element to EDI. The following code snippet illustrates how to use {{{ }}} when… Continue reading Errors while converting special characters from JSON to EDI