After you have accessed data on NetSuite, you will have to transform it based on two main factors,
- The limitations of the database that is going to be used
- The type of analysis that you plan to perform
Each system has specific limitations on the data types and data structures that it supports. If for example you want to push data into Google BigQuery, then you can send nested data like JSON directly. Keep in mind that in the case you are working with the web services SOAP API you will get XML responses. Of course, when you are dealing with tabular data stores, like Microsoft SQL Server, this is not an option. Instead, you will have to flatten out your own data, just as in the case of JSON, before loading into the database.
Of course, when you are dealing with tabular data stores, like Microsoft SQL Server, this is not an option. Instead, you will have to flatten out every data, just as in the case of JSON, before loading into the database.
Also, you have to choose the right data types. Again, depending on the system that you will send the data to and the data types that the API exposes to you, you will have to make the right choices. These choices are important because they can limit the expressivity of your queries and limit your analysts on what they can do directly out of the database.
With the NetSuite web services API you also have two main additional sources of complexity. When it comes to data types you have to keep in mind that SOAP is using XML to describe the service and the data, so the data types that you have to map are coming from XML and might have automatically been transformed into the primitive data types of the language that you are using.