NetSuite SuiteAnalytics

the netsuite suiteanalytics connector differs from our other docid\ wygqqfsbdfs8mq7cz6euf connector in that the netsuite (oracle netsuite) connector uses the netsuite rest api based web services and requires you to deploy an integration application in your netsuite instance on your own behalf there are differences in the netsuite rest api web services connection so we recommend incorporating both connectors for your production instance especially during a migration or integration effort so that you can assertain what data from your netsuite instance you are able to attain in your pipeline(s) this netsuite suiteanalytics connector is focused on using the netsuite2 com connectivity feature of netsuite, which has also become known as the analytics data source, or suiteanalytics connect if your netsuite instance currently only supports the older netsuite com option we highly suggest you work with your netsuite success team to switch to the newer version since the older version 2018 2 will not receive any new development as of october 2021 pre requisites for netsuite suiteanalytics connector a netsuite suiteanalytics license netsuite administrator access to setup the integration tokens and keys from the integration ability to assign the data warehouse integrator (dwi) role set your service data source connection attribute to netsuite2 com setup instructions below are the setup instructions for this connector broken into sections with ordered steps for ease of navigation and follow along details configure netsuite data source for suiteanalytics access your netsuite account by logging in to the netsuite portal click the home icon, or view the left menu for settings and click the set up suiteanalytics connect option view the details under the your configuration area to see the service service host , service port, and account id values and write them down for later retrieval begin configuring the netsuite2 com data source by clicking setup from the main header menu and click on the path setup > company > enable features in order to access the suiteanalytics enablement area click on the suitecloud tab check the box for client suitescript in the suitescript section click on i agree to accept the terms of service that opens check the server suitescript option in the suitescript section click on i agree to accept the terms of service that opens (optional) if using the dlh io standard docid\ wygqqfsbdfs8mq7cz6euf connector you will also check the checkbox for oauth 2 0, which allows different entities to be retrieved (optional for this connector) click the save button which is visibile when you scroll to the bottom of the page create an integration for suiteanalytics navigate to create a new integration by accessing the main header and selecting setup > integration > manage integrations > new in the create new integration page you will need to update the following items by updating the following form fields with the values name = datalakehouse io integration description = integrate dlh io with netsuite state = enabled token based authentication = check the checkbox to enable this option all other token based authentication area and oauth 2 0 checkboxes should be unchecked click the save button to save the integration the client credentials area will appear above the save button area and underneath the user credentials section please copy these as they will be used in your connection settings for dlh io note these keys, and secrets will not be visible once you leave this page so, please copy them somewhere to be safely stored and used when creating the connector user role & permissions required for integration access a new role is highly recommended to be created in order to assign the necessary permissions for suiteanalytics with netsuite2 com source connectivity a new role called data warehouse integration (dwi) is available, and we recommend also creating a new role which will be specific to the datalakehouse io and netsuite integration navigate to setup > users/roles > manage roles > new in the name field, enter a unique name for the role, ex dlh ns role scroll down the page to find the permissions tab click the setup sub tab from the permissions dropdown select the following and click the add button to add these permissions log in using access tokens suiteanalytics connect click the save button to save the new role you created next, we need to specify which user will connect to suiteanalytics when configured in dlh io, so navigate to setup > users/roles > manage users click the name of the user which you've identified to be the user profile that will connect to netsuite suiteanalytics in the resulting page click the edit button scroll down to the bottom and click on the access sub tab click the roles sub tab from the dropdown select the data warehouse integrator role click add click the save button to save the changes for the user find the data warehouse integrator role id the role data warehouse integrator is required when connecting to suiteanalytics this role id differs across all netsuite account, so find yours using the following steps and save it for when you create the connector in dlh io access the roles are by navigating to setup > user/roles > manage roles locate the internal id for the data warehouse integrator role by view the internal id column for the data warehouse integrator role from the list nb if you do not see the internal id column in the roles table list, then you must click on the customize view option then in the resulting page find the intenral id field in the field dropdown and click add then click save to add it to the role search list you may need to give the custom view unique name in order to save take note of this value and save it for when configuring your netsuite suiteanalytics connector in dlh io create the access token the access token is used in combination with the consumer key and secret from when you created the integration in a prior step a token id and token secret will be generated in the following steps prior to you being able to successfully configure the dlh io integration to your netsuite suiteanalytics instance log in with either a user having the administrator (not system administrator) or the access token management permission via setup > users/roles > access tokens > new choose the application name from the dropdown, for example, datalakehouse io integration select the user that was assigned the dwi role select the data warehouse integrator option from the role menu enter in the token name field, dlh integration non svc acct we use this term so that administrators understand that this token authorization is associated with a user and is usually not a service account if you are using a service account users specifically for the integration then you can leave this field blank click the save button note immediately take note of the token id and token secret shown as they will not be displayed once you leave the page get ready to enter the information from this step and any captured above into the dlh io netsuite suiteanalytics connector to integrate the two systems create the dlh io netsuite suiteanalytics source connector now that you have completed the setup steps in netsuite for the integrator and the suiteanalytics configuration, etc you should have all the information required to create the dlh io connector that points to your netsuite suiteanalytics account conduct the following steps navigate to dlh io and your account click on the source connector and select the netsuite suiteanalytics source connector enter the unique name/alias for this connection enter the target schema name that will be created in your cloud data warehouse destination target enter in the account id (this is just the numbers at the start of your netsuite account url, not the entire url string) enter the port number found in the previous configuration section (default 1708) enter the consumer key enter the consumer secret enter the token id enter the token secret enter the role id leave allow non pk tables as yes (default) unless otherwise instructed by support click save & test to save the connector at this point dlh io will attempt to reach your suiteanalytics account instance and confirm connection success the synchronization will be available to start once you create or confirm your destination target and docid\ jvybwq5ydjrq3ajxuqghs done data replication details this section provides information on how data is replicated, at what frequency and which replication/synchronization details are worth noting from dlh io replication frequency configurations details default replication frequency 24 hours minimum frequency 1 hour (lower on business critical plan) maximum frequency 24 hours custom frequency 1 24 hours replication definitions the following types of replication happen between this source and your target destination cloud data warehouse of choice when a sync bridge runs historical data load (also first time sync) occurs during the first/initial data sync of the sync bridge pipeline and any time you need to or are requested to conduct a historical re sync process for your data here, dlh io ingests all available data for the objects/tables you've selected or are available to you from the source based on your authentication access on that source this can take a relative elongated time to retrieve all data from the source and replicated to the target, as the name suggest it is retrieval all data, so if the source contains large amounts of data even in our parallel processing capability a customer could expect more than an hour for large data system if there are any concerns that a historical load or first time sync has not completed within a reasonable amount of time please contact https //support datalakehouse io incremental (aka deltas) data load after a first time synchronization/replication or a historical data load, all subsequent processes of replicating the data for a sync bridge (source to target) are referred to as delta or incremental loads here, dlh io captures the latest/newest records and/or events and any changes/updates to existing records and/or events in the source connector based on the frequency set in the sync bridge connector considerations or limitations none at this time