Does Celigo Support NetSuite Multi Subsidiary?

NetSuite

TMNow | October 04, 2022

Introduction:

Celigo's? - NetSuite Connector has been the industry-leading solution for integrating NetSuite for years. It provides prebuilt integration for automation in any business scenario. Celigo(integrator.io) is helpful to import data between two applications. It is useful to manage businesses to grow. Now Celigo supports the NetSuite Multi-Subsidiary feature mappings that allow you to share master data that is coming from NetSuite by building Celigo flows.

What is NetSuite Multi-Subsidiary, and how does it work with Celigo?

NetSuite Multi-subsidiary:

• NetSuite Multi-Subsidiary helps all business processes to deal with multiple subsidiaries within an organization and handle any master data by placing orders.
• An organization can use a single NetSuite account to manage records and transactions for multiple legal entities, manage multiple businesses in different tax regions involving multiple currencies. OneWorld uses a single hierarchical structure for organizing both domestic and international subsidiaries.
• NetSuite Multi-subsidiary works in Celigo by exporting and importing data between two applications using field mapping.

How to set up a multi-subsidiary in Celigo?

First, we need to build the flow in Celigo like?

• Custom Flow
• Pre-Built Flow

Custom Flow:

• It means we need to make connections between two applications after we need to create flows manually from source to destination.
• Integration flows transfer data from a source application to a destination application. If you have customer record data in one application that you want to transfer to another application, an integration flow allows you to export data from the source application and import it into the destination application.?
• You can create a flow to sync your shipping data with your billing info or your inventory data with your customer lists. You can automatically stream the data in real-time using web-hook listeners, set up a flow to run on a scheduled basis, or manually trigger a flow to run as needed.?

Pre-Built Flow:

• The pre-built flow means we need to install integration packages in Celigo after giving a Connection between two applications from source to destination. Integration Apps are complete pre-built software integrations that anyone can use to connect enterprise applications easily and automate processes, simultaneously reducing the time and cost of integration maintenance. Integrator.io is an integration platform-as-a-service (iPaaS). The Celigo integration platform delivers everything a growing business needs to automate every business process across the organization.

BUILDING CONNECTIONS

Step A: Set up an integrator.io connection?

Step B. Supply required integrator.io account information

Step C. Test the connection:

STEP A: SET UP AN INTEGRATER.IO CONNECTION?

• Start establishing a connection to integrator.io in the following ways:?
• From the Resources menu, select Connections. Then, click + Create connection at the top right.?
• While working on a new or existing integration, you can simply add an application to a flow by clicking Add source or Add destination/lookup.?

STEP B. SUPPLY REQUIRED INTEGRATER.IO ACCOUNT INFORMATION?

• At this point, you’re presented with settings for providing integrator.io.
• Authentication Type:Token based Auth(automatic/manual) .
• Choose Environment: Production/Sandbox, Enter NetSuite account Id?

Important: Before creating an Access Token in NetSuite for integrator.io, please make sure you have installed the 'Celigo integrator.io' SuiteApp in your NetSuite account. You must refer to 'integrator.io' in the 'Application' field for all Access Tokens used by integrator.io. After creating an Access Token in NetSuite, 'Token Id' and 'Token Secret' will be displayed only once . Please copy and paste 'Token Id'? before you leave the confirmation page.

Flow Design :

1. If we export a customer's multi-subsidiary data to any other application using Celigo simply need to map the fields in a customer flow we have two methods. Listener flow/Real Time Flow: Creates a web-hook listener in integrator.io to receive incoming information from the source application and initiate the flow with the data sent. Here In this method, we export data from NetSuite customer multi-subsidiary data need to create, edit the data in NetSuite? it will come like an array format in Celigo and it finds the match Real-Time flow: Real-time flows are designed to run automatically when a new record is created or an existing record is updated in the source system real-time flow With NetSuite as source
2. First, we need to login into? integrator.io, click on new integration, and add a new flow. Later you can see a window with labels source and destination On the source side select NetSuite for real-time flow and create a connection with a NetSuite account with it. Later Under record type select the record you want to integrate with the other Later select the sublists you want to move to your destination platform under Sublists to include. then click on the preview to view your data from NetSuite

Transformation:

In Custom flow, we need to create a saved search. Record type:(customer) and Saved search type: (public) Transformation: Transform Rules is an integrator.io feature that helps you transform your significant Export or Import JSON data to a much smaller JSON structure that is much more readable and easier to understand.

Flow With NetSuite as a destination

Static lookup:

If we need to import the multi-subsidiary data which is coming from the source system. In Celigo field mappings, map subsidiary(name) field mapping type: Lookup, Options: Static value to value: NetSuite to match the fields. In case of any subsidiary, values are Created, Edited, and deleted in source or destination then static lookup needs to be changed manually if it is dynamic lookup it will update automatically after refreshing that lookup field

Dynamic lookup:?

We need to map subsidiary(name) field? mapping type: Lookup, Options: Dynamic: NetSuite Search, Search Record Type: subsidiary, search filters: Internal ID is NetSuite_subsidiary__c? in destination

FAQ:

?1. What kind of bundle is required to build the connection?

We need to install a Celigo integrator.io suite? bundle in NetSuite to build the connection between Celigo and NetSuite.

2. Do we need to make adjustments if we introduce a new subsidiary??

Yes, because if we are using static lookup in field mappings we need to change the values manually.If it is a dynamic lookup no need to change any field mapping values in Celigo lookup just need to refresh the lookup field the values automatically update in that field.

3. Do we need to enable any feature in Celigo to map NetSuite Multi-Subsidiaries?

No, we just need to include the subsidiaries sublist in Celigo and need to map the field using lookups.

4. What is the difference between custom flow and pre-built flow?

Custom Flow :

We need to give a connection first after we need to build the flows and mappings manually.

Pre-Built flows:

Install integration apps in Celigo and need to configure that flow, given the connection between the two platforms.

5. How to give the connection for NetSuite to Celigo?

Give the NetSuite account id and generate tokens in NetSuite after we need to give the token id and token secret in Celigo and click on save & close.

More Questions?

Visit:?www.techmantranow.com?

---------------------

Need help selecting?the right enterprise products & solutions for your business??Connect with TechMantra Now's Cloud ERP Software experts!