There is no way to get this information via the soap api.  The EmployeeRole object is not available via the soap api.

In the json of the post body, just include the custentity field at the top level.  Use the internalId as the value.

Use the customer search objects with  the search endpoint, but note the limits about the number of results per request.

The schema browser has a tab for the tables and columns available in the analytics schema (depending on your connection string you will either be using the analytics 2.0 schema or the connect 1.0 schema).  https://www.netsuite.com/help/helpcenter/en_US/srbrowser/Browser2021_1/analytics/record/transactionLine.html

Generally speaking you will want to use the following tables:

1. transaction
2. transactionline
3. item
4. untsTypeUom

Good luck.

Yes, you can use a vendor search to get all internal ids; however, the soap api limits you to 1,000 results per request, so you may have to paginate your response.

We highly recommend using the suiteanalytics odbc driver for this but what @sam-i-am said is correct.  The best way to reconcile the system is to have one or both of the systems keep track of the id of the other.

As an FYI–we answered this on stackoverflow for you with the actual code.

You’d have to add a user event script that’s hooked into the beforeLoad event.

Not sure about google sheets, but you can do this with excel and suiteanalytics workbook.  There doesn’t appear to be a connector for netsuite in google data studio.

I would recommend using the SAN code as your address label.  That will let you pick a particular address based on the SAN code.  If you are using the ODBC driver (suiteanalytics connect) you can easily pull the address information you need for the shipTo address.