Oracle Netsuite Connector

An out-of-the-box connector is available for the Oracle Netsuite Connector. It provides support for crawling CRM objects and sample profiling of data. The connectivity to Netsuite CRM is via Rest API, which is included in the platform. 

ORacle netsuite-1

Pre-Requisites

User Permission  

To use the Oracle Netsuite connector, the details specified in the following section should be available.

An admin/service account for crawling and profiling. By default, the service account provided for the connector will be used for any query operations. If the service account has to write privileges, then Insert / Update / Delete queries can be executed.

Operation

Access Permission

Connection validate

Read

Crawl schemas

Read

Crawl tables

Read

Profile schemas, tables

Read

Note: Navigate to Configuration  > Users & Roles for roles and permission. 

Technical Specifications

Connectors Capabilities

Supported Data Objects

Remarks (If Any)

Crawler

Tables

-

Table columns

-

Profiler

Table Profiling

Row count, Columns count, View sample data

Column Profiling

Min, Max, Null count, distinct, top 50 values

Full Profiling 

Not Supported

Sample Profiling

Supported

Connection Details

To connect to the Oracle NetSuite using the OvalEdge application, complete the following steps.

  1. Log in to the OvalEdge application
  2. Navigate to Administration > Connectors module. 
  3. Click on the + icon, and the Manage Connection with Search Connector pop-up window is displayed. Select the connection type as Oracle Netsuite. The Manage Connection with Oracle Netsuite specific details pop-up window is displayed.
  4. The following are the field attributes required for the connection.

    Configuration

    Description

    Connection Type

    By default, the selected connection type is displayed as the Oracle Netsuite. 

    License Type*

    Select the license type as ‘Standard’. 

    Connection Name*

    Select a Connection name for the Netsuite CRM database. The name you specify is a reference for your Netsuite CRM database connection in OvalEdge. Example: Netsuite CRM Connection DB1

    Netsuite Account Id*



    Database instance URL

    Example: https://netsuite_crm.com/

    Client/Consumer Id*

    Client ID generated after the app is registered

    in Oracle Netsuite

    Client Secret*

    Client Secret

    Token ID*

    Token ID

    Token Secret*

    Token Secret

    Ream ID*

    Enter the Account-id in the Account_Id format

    Plugin Server

    Enter the server name if you are running this as a plugin.

    Plugin Port

    The port number on which the plugin is running.

    Default Governance Roles

    From the dropdown list, select Stewards, Custodian, and Owner.

    No of the archive objects

    Select the toggle button to set the if the user wants to enter the count of no. of the archive objects. 

    Select Bridge

    Select option NO Bridge if no bridge is available for the connector 

  5. Once after entering the connection details in the required fields, 
  6. Click on the Save button or Save & Configure to establish and configure the connection settings. When you click the Save & Configure button, the Connection Settings pop-up window is displayed, where you can configure the connection settings for the selected Connector.

Note: The Save & Configure button is displayed only for the Connectors for which the settings configuration is required.

7. Click on the Validate button the entered connection details are validated. 

Note: It is up to the user's choice, you can save the connection details first, or you can validate the connection and then save it.

Error Validation Details

The following are the possible error messages encountered during the validation. 

Error Messages

Description

Error_validate_connection 

An alert message is displayed when provided details are incorrect.

Connection Settings

Crawler

Crawler has various settings tabs for crawling and profiling options. The crawler options are available for all the connections. Based on the connection selected, the options will differ. You need to provide the mandatory options for the crawler setting one of them is mandatory. 

2-Nov-08-2022-07-39-51-2305-AM

Crawler options

Crawling will discover the Report and Reports Columns and bring them into OvalEdge.  

  • Tables Views Columns: This crawling will discover the tables, views, and Columns and bring them into OvalEdge. This is the default option for crawling. 
Crawler Rule

In the Crawler Rules, when setting up the regex rules, the user will be able to write rules that will either include and/or exclude reports or reports columns. 

  • Include Report Regex: Includes only reports which match regex with report name
  • Exclude Report Regex: Excludes reports which match regex with report name

Crawler options

This crawling will discover the Report and Reports Columns and bring them into OvalEdge.  

  • Tables Views Columns: This crawling will discover the tables, views, and Columns and bring them into OvalEdge. This is the Default option for crawling

Crawler Rule

In the Crawler Rules, when setting up the regex rules, the user will be able to write rules that will either include and/or exclude reports or reports columns. 

  • Include Report Regex: Includes only reports which match regex with report name
  • Exclude Report Regex: Excludes reports which match regex with report name

Profiler

Profiling a data source also helps in identifying relationships between the tables at the entity level and patterns between them. Many attributes can be specified in the profile settings.

The attributes are as follows:

Fields

Description

Order:

Order is the sequence in which the profiling is done. 

Day: 

The day of the week in which profiling is set to run.

Start/End Time:

The start and end time that profiling is set to perform.

Number of Threads:

A thread is a process where a query is executed on a database to do single or multiple tasks. The number of threads determines the number of parallel queries that are executed on the data source. 

Profile Type: 

There are four main types of data profiling. 

  • Sample Profiling runs the profile on a given sample size. The data on columns (like Min, Max, Distinct, Null Count, etc.,) will be different when compared with full profiles as we calculate them only on sample size. The sample profile is based on two main values. To execute a sample profile, first select the Sample profile type as “Sample” and enter a sample profile size (count of records to be profiled).
  • Auto and if the table row count is more than the Rowcount Limit configured in the setting. The sample size should always be less than Rowcount Limit when Profile Type is Auto, and Row Constraint is checked as True. When the profile type is set as Auto, it first runs as a Query type, and later it transfers the type from Query to Sample if the conditions are not met. In Query mode, when you check Rowcount Constraint as TRUE and if the table row count exceeds the Rowcount Limit, the profile type is automatically transferred from Query to Sample. 
  • The Query profiling is when the Rowcount Constraint is checked as TRUE and if the input table row count is less than the Rowcount Limit, then the profiling is executed on the entire table. If the input table row count exceeds the Rowcount Limit, then the profiling skips execution for those tables to avoid performance issues. A profile type set to “Query” will always depend on the Rowcount limit and the row count constraint must be set as “True”. 
  • Finally, there is the Disabled profile type, which prevents profiling on the selected data source. 

Row Count Constraint:

When it is set to true, it enables the data rule profiling. 

Row Count Limit:

The number of rows of data to be profiled. 

Sample Data Count:

Total number of rows to see within the table data page in the Catalog.

Sample Profile Size: 

Total number of rows to be included in profiling.

Query Timeout: 

Length of time in seconds to allow the query to run on a remote database before timing out

Once the setting for profiling has been configured, go back to the Crawler screen and click “Crawl/Profile” to begin the profiling. 

3-Nov-08-2022-07-46-41-2288-AM

Access Instruction

The user is asked to provide relevant information on the data source/connector that has been crawled. It allows the Crawler admin to write the instructions.

Other

When you navigate the Others tab, the Send Metadata Changes Notifications to and Context URL sections are displayed. 

Send Metadata Notification to

  1. Select whether the notifications for the Data Owner and Data Steward under the specific Roles need to be sent or not.
  2. Select the desired role from the Roles dropdown menu and click the Save Changes button. The notifications will be successfully sent to select Data Owner and Data Steward.

Context URL: 

Enter the browser URL for the selected data source. 

Example: https://azure.microsoft.com/en-in/services/event-hubs/#overview is entered in for the tableau connection.

Note: Click on the + Add New URL option to add multiple URLs. The new textbox to provide the URL details is displayed in the Context URL section.

Additional Information

  1. Is NetSuite also available On-premise?

     Answer: NetSuite is a cloud solution and therefore does not have any on-premise software.