Transaction Number Doesn’t Match Transaction ID When Data is Pulled via ODBC

Hi All,

First time posting here! Glad to have a space like this instead of contacting support all the time.

So I’ve been using the ODBC driver for while and have been pulling sales order data, customer data, etc. Recently when looking at some sales order data, I’ve noticed that the “Transaction ID” (transaction internal ID) and “Transaction Number” (Document Number) are not matching up. It seems like the other fields such as status match what the internal ID is, but not the document number.

Has anyone experienced this before? Like mentioned I am using the SuiteAnalytics ODBC connector and I am pulling this data into Tableau Desktop. Thanks!

Add Comment
2 Answer(s)

The tranid is not the internal id, those should not match up.  Document Number is like the display of the document number, internalid is just a stringified number.

Intermediate Answered on June 10, 2020.

Sorry, I must have wrote this wrong. So what I am experiencing is that the transaction ID (internal ID) is not linking to the correct transaction number (document number).

So for example, say I have an internal ID of 12345 and the associated document number shown on from pulling the data out is SO-INC12345, However, when I look up the internal ID, it shows a different document number.

Does that make better sense?

on June 10, 2020.
Add Comment

I’ve never used the ODBC connector, but the first thing I’d check is what role you’re using for access and its associated permissions. In a Suitescript context, if your role doesn’t allow access, Netsuite sometimes returns other field values in place of ones you don’t have permission to access. The connector may be behaving in a similar way?

Beginner Answered on June 11, 2020.

Sorry for the late reply, but that might be possible….. Whenever I do look up these random internal ID (I take an opportunity and replace the id in the URL) it give me the error saying it belongs to another transaction type.

on June 18, 2020.
Add Comment

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.
  • This site made possible by our sponsors:   Tipalti   Celigo   Limebox   Become a Sponsor   Become a Sponsor