Jira Code : MICL-173 OAuth 2.0 relies on the access and refresh tokens to authorize access to protected resources. However, if these tokens are compromised, attackers can gain access to sensitive data. Here are some of the complexities that you may encounter when working with NetSuite OAuth 2.0: Access Token and Refresh Token: NetSuite OAuth… Continue reading Limitations of OAuth 2.0
Author: Aranya T R
OAuth 2.0 Client Credentials Flow
Jira Code : MICL-260 Creation of this mapping is a required step for the OAuth 2.0 client credentials flow to work. STEP 1 : Create Integration Records for Applications to Use OAuth 2.0 Go to Setup > Integration > New. Enter a name for your application in the Name field. Enter a description in the… Continue reading OAuth 2.0 Client Credentials Flow
Proposal for Automatic Purchase Order Creation based on Sales Order Data
Jira Code : MAMS-101 Proposal summary This proposal describes the Automatic Purchase order creation based on Sales of items and report ofthe sales data. Requirement The client would like to view the sales and stock details of items for a particular time period on acustom page. And based on the sales of items, need to… Continue reading Proposal for Automatic Purchase Order Creation based on Sales Order Data
NetSuite Connection in MuleSoft Composer
MuleSoft Composer MuleSoft Composer for Salesforce enables Salesforce admins to connect apps and data to Salesforce and automate integrations quickly and easily with clicks, not code — all inside of the Salesforce UI. NetSuite Connection in MuleSoft Composer Whether you are using NetSuite as a data source (take a data from NetSuite and copy it… Continue reading NetSuite Connection in MuleSoft Composer
Manage and configure metafield definitions for Shopify products and its variants
In addition to the metafields, the integration app gets the metafield definitions for product and their variants from Shopify. This allows you to create additional data constraints for metafields and enable the merchant to edit metafield values in context. For every metafield that is synced to Shopify, the integration app searches for the matching metafield… Continue reading Manage and configure metafield definitions for Shopify products and its variants
Template for Restlet API Request
Description Jira Code : MICL-180 The below code can be reused for fetching the details from NetSuite using the Restlet GET API Only we need to change the parameters , validations and saved searches Solution
Creating the Saved search in UI through Console
Steps Open the NetSuite account where you need to create the Saved search 2. Open the Console screen as below by Right clicking the screen and select Inspect 3. Run the below Code in the Console screen IMPORTANT : Need to give the TITLE Then the corresponding search will be created in the NetSuite account.
Create Integration Records for Applications to Use OAuth 2.0
Before users can authorize an OAuth 2.0 application for NetSuite access through REST web services, RESTlets, or SuiteAnalytics Connect, an integration record must be created for the application. It is also possible to edit an existing integration record. Administrators or users with the Integration Application permission can create integration records. The following procedure describes how… Continue reading Create Integration Records for Applications to Use OAuth 2.0
Set Up OAuth 2.0 Roles
An administrator can create a new role with OAuth 2.0 permissions, or modify existing roles to add OAuth 2.0 permissions, then assign users to these roles as needed. OAuth 2.0 Permissions The following OAuth 2.0 permissions can be added to roles as appropriate. OAuth 2.0 Authorized Applications Management: Is primarily for the Administrator role, or… Continue reading Set Up OAuth 2.0 Roles
Error when updating metafields on a product using Celigo Flow
Error {“errors”:{“key”:[“must be unique within this namespace on this resource”]}} Solution You can use the Product API to update or create a metafield when you call PUT /products/PRODUCT_ID.json But after you save a product you don’t get the metafields, so you need to call first /metafields.json?metafield[owner_id]=PRODUCT_ID&metafield[owner_resource]=product