Sync NetSuite customer refund created against the customer deposit to Shopify

When you sync a paid order as a sales order with a customer deposit, and if there is a refund request even before the order is fulfilled, a refund adjustment is required instead of item restock. In this scenario, the fulfillment and invoice records are not created in NetSuite and a customer refund is created… Continue reading Sync NetSuite customer refund created against the customer deposit to Shopify

Published
Categorized as Celigo Tagged

Proposal For Location Setting in NetSuite Sales Orders

Proposal summary  This proposal covers the Shopify Integration to update the line level location in sales orders according to the location in Shopify  Requirement   The location in shopify order has to be added in the item line in NetSuite sales order  Prerequisites    Please provide us the shopify API key and password to establish… Continue reading Proposal For Location Setting in NetSuite Sales Orders

Adding a Shopify Metafield Product Mapping in NetSuite Connector(FarApp)

Log in to app.farapp.com. Select the Shopify connector and the relevant account. Go to Mappings > Products. Click Add Mapping. The Add Shopify Mapping window opens. You will be able to view all required, standard, and uncommonly used fields for the current channel, for a shopify metafield select the standard and there you can select metafields. In… Continue reading Adding a Shopify Metafield Product Mapping in NetSuite Connector(FarApp)

Netsuite Custom Field to Shopify Product Variant Meta field – Celigo Custom Flow

We can bring the custom field value retrieved using a Netsuite saved search to the Shopify product variant record meta field. For this first, we need to create a normal Item Search in Netsuite and add it in Export. The result of the search should include the custom field value As a next step, we… Continue reading Netsuite Custom Field to Shopify Product Variant Meta field – Celigo Custom Flow

BAD REQUEST

{“type”:”error.SuiteScriptError”,”name”:”400_BAD_REQUEST”, SOLUTION The 400 (Bad Request) status code indicates that the server cannot or will not process the request because the received syntax is invalid, nonsensical, or exceeds some limitation on what the server is willing to process. If the server is programmed with a file size limit, then you might encounter a 400 error. {“fulfillment”: {“location_id”:60986949890,”tracking_number”:null,”line_items”:[    {        “id”:”11751945470210″,”quantity”:2   } ]         }} How… Continue reading BAD REQUEST

Integrating with Postman

Postman provides an API development toolchain aimed at integrating with your workflow.The Postman team develops an open ecosystem in conjunction with industry partners tobuild integrations that facilitate your API projects. Integrations allow you to automatesharing data and functionality between Postman and other tools you might use for your API development. 1.Body field corresponding to item… Continue reading Integrating with Postman