Replicate NetSuite Data from PowerShell

Write a quick PowerShell script to query NetSuite data. Use connectivity to the live data to replicate NetSuite data to SQL Server.

The CData ODBC Driver for NetSuite enables out-of-the-box integration with Microsoft's built-in support for ODBC. The ODBC driver instantly integrates connectivity to the real NetSuite data with PowerShell.

You can use the .NET Framework Provider for ODBC built into PowerShell to quickly automate integration tasks like replicating NetSuite data to other databases. This article shows how to replicate NetSuite data to SQL Server in 5 lines of code.

You can also write PowerShell code to execute create, read, update, and delete (CRUD) operations. See the examples below.

About NetSuite Data Integration

CData provides the easiest way to access and integrate live data from Oracle NetSuite. Customers use CData connectivity to:

Access all editions of NetSuite, including Standard, CRM, and OneWorld.
Connect with all versions of the SuiteTalk API (SOAP-based) and SuiteQL, which functions like SQL, enabling easier data querying and manipulation.
Access predefined and custom reports through support for Saved Searches.
Securely authenticate with Token-based and OAuth 2.0, ensuring compatibility and security for all use cases.
Use SQL stored procedures to perform functional actions like uploading or downloading files, attaching or detaching records or relationships, retrieving roles, getting extra table or column info, getting job results, and more.

Customers use CData solutions to access live NetSuite data from their preferred analytics tools, Power BI and Excel. They also use CData's solutions to integrate their NetSuite data into comprehensive databases and data warehouse using CData Sync directly or leveraging CData's compatibility with other applications like Azure Data Factory. CData also helps Oracle NetSuite customers easily write apps that can pull data from and push data to NetSuite, allowing organizations to integrate data from other sources with NetSuite.

For more information about our Oracle NetSuite solutions, read our blog: Drivers in Focus Part 2: Replicating and Consolidating ... NetSuite Accounting Data.

Getting Started

Create an ODBC Data Source for NetSuite

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

The User and Password properties, under the Authentication section, must be set to valid NetSuite user credentials. In addition, the AccountId must be set to the ID of a company account that can be used by the specified User. The RoleId can be optionally specified to log in the user with limited permissions.

See the "Getting Started" chapter of the help documentation for more information on connecting to NetSuite.

Connect to NetSuite

The code below shows how to use the DSN to initialize the connection to NetSuite data in PowerShell:


$conn = New-Object System.Data.Odbc.OdbcConnection
$conn.ConnectionString = "DSN=CData NetSuite Source x64"

Back Up NetSuite Data to SQL Server

After you enable caching, you can use the code below to replicate data to SQL Server.

Set the following connection properties to configure the caching database:

CacheProvider: The name of the ADO.NET provider. This can be found in the Machine.config for your version of .NET. For example, to configure SQL Server, enter System.Data.SqlClient.
CacheConnection: The connection string of properties required to connect to the database. Below is an example for SQL Server:
Server=localhost;Database=RSB;User Id=sqltest;Password=sqltest;

The SQL query in the example can be used to refresh the entire cached table, including its schema. Any already existing cache is deleted.


$conn.Open()
# Create and execute the SQL Query
$SQL = "CACHE DROP EXISTING SELECT * FROM " + $SalesOrder
$cmd = New-Object System.Data.Odbc.OdbcCommand($sql,$conn)
$count = $cmd.ExecuteNonQuery()
$conn.Close()

The driver gives you complete control over the caching functionality. See the help documentation for more caching commands and usage examples. See the help documentation for steps to replicate to other databases.

Other Operations

To retrieve NetSuite data in PowerShell, call the Fill method of the OdbcDataAdapter method. To execute data manipulation commands, initialize the OdbcCommand object and then call ExecuteNonQuery. Below are some more examples CRUD commands to NetSuite through the .NET Framework Provider for ODBC:

Retrieve NetSuite Data


$sql="SELECT CustomerName, SalesOrderTotal from SalesOrder"
 
$da= New-Object System.Data.Odbc.OdbcDataAdapter($sql, $conn)
$dt= New-Object System.Data.DataTable
$da.Fill($dt) 
 
$dt.Rows | foreach {
  $dt.Columns | foreach ($col in dt{
    Write-Host $1[$_]
  }
}

Update NetSuite Data


$cmd = New-Object System.Data.Odbc.OdbcCommand("UPDATE SalesOrder SET Class_Name='Furniture : Office' WHERE InternalId = @myInternalId", $conn)
$cmd.Parameters.Add(new System.Data.Odbc.OdbcParameter("myInternalId","001d000000YBRseAAH")
$cmd.ExecuteNonQuery()

Insert NetSuite Data


$cmd = New-Object System.Data.Odbc.OdbcCommand("INSERT INTO SalesOrder SET Class_Name='Furniture : Office' WHERE InternalId = @myInternalId", $conn)
$cmd.Parameters.Add(new System.Data.Odbc.OdbcParameter("myInternalId","001d000000YBRseAAH")
$cmd.ExecuteNonQuery()

Delete NetSuite Data


$cmd = New-Object System.Data.Odbc.OdbcCommand("DELETE FROM SalesOrder WHERE InternalId = @myid", $conn)
$cmd.Parameters.Add(new System.Data.Odbc.OdbcParameter("myInternalId","001d000000YBRseAAH")
$cmd.ExecuteNonQuery()

Ready to get started?

Download a free trial of the NetSuite ODBC Driver to get started:

Download Now

Learn more:

NetSuite ODBC Driver

The NetSuite ODBC Driver is a powerful tool that allows you to connect with live NetSuite data, directly from any applications that support ODBC connectivity.

Access NetSuite like you would a database - read, write, and update Leads, Contacts, Opportunities, Accounts, etc. through a standard ODBC Driver interface.