When using SuiteQL - has anyone experienced a prob...
# suiteql
n
When using SuiteQL - has anyone experienced a problem where the REST API does not return the correct # of rows from the API? For instance - with
Copy code
TransactionAccountingLine
I can do a
Copy code
SELECT COUNT(*) FROM TransactionAccountingLine where transaction = X
Which returns say, 32 - but when I actually run
Copy code
SELECT * FROM TransactionAccountingLine where transaction = X
I get fewer than 32 rows. This is not for all transactions - and its pretty random when it happens.
b
extra attention to the edge cases
n
Perhaps I’m missing something - but what edge case are you talking about?
They’re missing rows - if I query the next day, they appear.
b
the documentation goes over how count(*) behaves differently from normal selects
n
Yes - but they’re missing rows regardless. I don’t think it’s an edge case with
COUNT
as the missing rows exist in Netsuite - I just can’t access them.
b
as in you added up accounting impacts and they dont match the lines from your query?
n
Yes.
I can see the missing
transactionaccountingline
inside of Netsuite as well - the income statement is heavily off because of this (in the extracted version)
b
cant really tell more without seeing the data
I wouldnt expect TransactionAccountingLine to be missing unless there is something off with the permissions
n
That’s what I thought as well - but the weirdest thing is that it’s not the same transactions each time - so I don’t think it’s a permissions issue. I can tell they exist.