Hello! I hope all is well with the NS community. I am experimenting with pulling data from a saved search using oauth2 via restlet, but am noticing it is very slow. Example 70k records with about 10 columns takes two minutes. Is there a better way to use 3rd party programs (R, Python, PowerBI, some sql ide) to pull data from NS? Ultimately, I have data from 4 different searches and I am manually saving these to csv files and reading the content via R and then moving to power bi. I am just trying to find the best way to bypass that manual step and get the data right into the programs I use from NS. I believe activating suite analytics connect and maybe using ODBC is the way? Thank you!

I was able to iterate through 80k records, before the 5 minutes limit of restlet got hit oauth1.0, not sure if itteration will vary on record type or not. You do a schedule job on backend pull the data to azure or something by calling your restlet. From there powerbi has a direct connector. You can refesh as many as high as 24 times a day I believe in powerBI. Will remove the limit of Itterating through that many lines. One other solution that you can do is create the csv through a MR script and store it in filecabinet and make it available without login. Can be done while creating the file through code itself. If the file is same every time. PowerBI can pull that as well if you give the url so manual effort will be gone..

There are a few different ways. (1) ODBC. Let's you work with certain tools that are already built to use ODBC. I have heard it isn't enormously fast, so if speed is essential, maybe look at the other two methods, but I don't know this for sure. (2) REST API. There's a way to query and grab data from records via a REST API. I dont' know if all records are exposed this way. (3) Restlets/Public Suitelets. Probably the most flexible of the three methods, but you have to write your own backend SuiteScript for handling the requests. Restlets are generally preferred because they have security built in, but it's also possible to do a public suitelet and roll your own pre-shared key checking mechanism.

For large data exports, ODBC is the fastest as long as the queries are simple enough