In a custom flow to sync sales orders from Warroad to Touchstone, we need to writeback to the sales orders synced from the Warroad account mentioning that the syncing was completed successfully. For this, we need to include an extra Import as the last part of the flow Before we include the writeback the flow… Continue reading Writeback to the Source
Category: Celigo
Netsuite Salesforce integration using Celigo :Pre-Built Flows (Premium Edition):
Sync Accounts from Salesforce to NetSuite Sync Customers from NetSuite to Salesforce Sync Contacts from Salesforce to NetSuite Sync Contacts from NetSuite to Salesforce Sync Items from NetSuite to Salesforce (excludes Item Groups) Sync Opportunities from Salesforce as Sales Orders to NetSuite Sync Sales Orders from NetSuite to Salesforce Sync Sales Order Status from NetSuite… Continue reading Netsuite Salesforce integration using Celigo :Pre-Built Flows (Premium Edition):
Handlebars to check a checkbox in the destination record, for a specific customer
Here we need to check a checkbox named Wholesale Order in the destination record if the customer in the sales order record is with the ID 255507. So in the Import mapping select the Destination as Wholesale Order and click on the settings option near to that. Select the Field mapping type as Multi-Field Expression… Continue reading Handlebars to check a checkbox in the destination record, for a specific customer
Celigo’s ‘One to Many’ Configuration
One of the most common issues this configuration solves is the case when input data has child records that should each be considered as a parent record. If the records being processed are JSON objects, the ‘Path to many’ field can be used to enter the JSON path to child records. This field need not be set… Continue reading Celigo’s ‘One to Many’ Configuration
Find existing sublist line in Mapping
To find existing sublist line in mapping, the Use as a key field to find existing lines setting can be used. The Use as a key field to find existing lines setting is not a mapping field, but it’s available in the sublist mapping settings. If set, the setting finds the existing sublist line with “<DestinationRecordField (NetSuite)>” as… Continue reading Find existing sublist line in Mapping
Lookup to fetch package-related details from the IF record
Create a search to fetch the details of the package weight and the tracking number. Criteria Type: IF Mainline: True Result tab include Then create the Lookup in the flow By clicking that + we are able to provide lookup Also provide Additional Search Criteria inside this lookup Thus we get the details from that… Continue reading Lookup to fetch package-related details from the IF record
Export Type: Once
If you want to export a record only once give this option. Also, we need to provide a Boolean field to mark records as exported Boolean field to mark records as exported : Please select a boolean field (i.e. a checkbox field) from the export application that integrator.io can use to keep track of records that… Continue reading Export Type: Once
Solve the error [ { “code”: “invalid_search”, “message”: “Failed to load search with SearchId: 19935. because That search or mass update does not exist.”, “occurredAt”: 1689321146120, “resolved”: false, “source”: “application”, “classification”: “value” } ]
In Export, we fetched the saved search data from the NetSuite side. Sometimes we get this error while taking the preview of Export. We can solve this by making the saved search in the NetSuite as PUBLIC
Configure error notification emails for other users
If you have Manage access to an integration, you can set up notifications for other users. To set up subscriptions for a user: Navigate to the integration that contains the connections or flows for which you want to configure email notification. On the Users tab, examine the list of users and the icons that appear in the Notifications column. Click… Continue reading Configure error notification emails for other users
Solve the error: Failed to save record because You must enter at least one line item for this transaction
While we are using suiteAPP 2.0, it will throw an error when all the sublist(eg: items) values are hardcoded. we need to map either one of the sublist values from exports(Standard type) or you can use the dynamic lookup to solve the above error