On another note regarding SuiteQL via the REST API, is anyone else running into issues querying the Transaction table externally? We have a defect case open with support currently and I was curious if anyone else is having issues since the 2023.1 upgrade.

"issues" is not very descriptive, what's the query that you're trying to run, what error you're getting, etc.

It was more of a probing question to see if anyone has noticed any oddities with queries that were working fine for a while and stopped working after the 2023.1 upgrade. Specifically, we're getting timeouts now due to an invalid parameter warning while running simple "select [whatever columns] from transaction [your where clause here]". We had run into an issue with the EntityAddressBook table previously not being found and needed to add the Perform Search permission to the role; something we did not need previously. I've been hearing rumblings of schema changes behind the scenes and was curious who else is running into issues.

I'm running fairly complex queries against the transaction table over multiple netsuite instances, and didn't notice any issues before or after the upgrade Permission changes are to be expected between versions

Excellent. That's the kind of feedback I was fishing for. Just following the troubleshooting trail.

That said, all our queries have

FETCH FIRST 1001 ROWS ONLY

in them. (to know if hasMore or not) I don't paginate via SuiteQL REST API. I either use

WHERE transaction.id > LAST_RESULT_ID

OR

WHERE transaction.id IN (id1, id2, ... id1000)

We're bumping into an error while trying to get just one row via Postman: SELECT * FROM transaction FETCH FIRST 1 ROWS ONLY. We're getting an "Invalid search query. Detailed unprocessed description follows. Search error occurred: Invalid or unsupported search." You mentioned permission changes between versions. Perhaps something changed and we need to buff up our role.

Also SELECT * is not a good idea, especially not via the REST API

Well, I just tried SELECT id FROM transaction FETCH FIRST 1 ROWS ONLY and it worked.