In the Create Connection panel provide the below details to setup a connection. Name your connection – Enter a clear and distinguishable name. API type – Choose your Shopify account API type: HTTP: Use traditional HTTP methods (GET, POST, PUT, DELETE) for straightforward interactions with individual resources. GraphQL: Use GraphQL for flexible, efficient queries and… Continue reading Set up a token connection to Shopify
Author: Aishwarya M J
Difference Between Location Field and Adjustment Location Field on the Main Line of Inventory Adjustment Record
Location field (Field Id: Location) is for accounts not using Multi-Location feature while Adjustment Location (Field Id: adjlocation) is for accounts using the Multi-Location feature. Navigate to Customization > Forms > Transaction Forms Click Customize on Standard Inventory Adjustment Click Screen Fields Main: Location and Adjustment Location are available, and both can be marked to Show
Creating Inventory Adjustments via SuiteScript Returns Unexpected Error
Scenario When creating an Inventory Adjustment record using SuiteScript, an unexpected error is returned. However, when setting the same values in UI, the record is saved successfully. Solution One possible cause for this is because there are customizations that is trying to set the main body Location field on the Inventory Adjustment. The body location field on the Inventory Adjustment record is Adjustment… Continue reading Creating Inventory Adjustments via SuiteScript Returns Unexpected Error
Export or import NetSuite multiple select fields
NetSuite multiple select field types allow you to include multiple values in a single field. In a scheduled flow that uses a saved search, integrator.io exports the multiple select field as a string with each value separated by a comma. In a real-time flow (one initiated by a webhook listener), integrator.io exports a multiple select… Continue reading Export or import NetSuite multiple select fields
Fix error : Invalid price reference key
Scenario The error occurs in the Sales order Import step which includes mapping of price level and unit price for the item lines. The issue is caused by the destination field Items : Price Level (Name) in the mapping. Solution Change the destination field of price level to “Items : Price Level (InternalId)” and map… Continue reading Fix error : Invalid price reference key
Functions supported by the integrator.io EDI generator
The given below are the functions supported by the EDI generator _counter : The _counter function is relatively new and helps you to count the number of EDI segments generated for the same segment identifier. Set the counter to true for an EDI segment in your definition file. _iterationCount : The _iterationCount EDI function is… Continue reading Functions supported by the integrator.io EDI generator
Attach and detach objects in NetSuite File Cabinet
You can attach (with nlapiAttachRecord) and detach (with nlapiDetachRecord) records in NetSuite and files in the NetSuite file cabinet. You can specify if you want to attach a record or detach a record while configuring the import. Choose one of the following options: Add Update Add/Update Attach Detach The mappings page has the following locked… Continue reading Attach and detach objects in NetSuite File Cabinet
Set NetSuite date format on saved searches
Consider a scenario where you exported records from NetSuite via a saved search flow, but the date fields were exported in the European format D/M/YYYY rather than your preferred format, DD-MMM-YYYY. You might have wondered if the issue was because the Celigo export had used the date format in the company preferences setting, which had… Continue reading Set NetSuite date format on saved searches
postResponseMap hook
The post response map hook is invoked on a page of records after response or results mapping. This hook is a great place to execute logic on batches of records to optimize the response/results data to be merged back into the source records. For example: Perform calculations using the results of a lookup, and then… Continue reading postResponseMap hook
Fix the error {{# each data}} not found in the template.
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.