From the top of my head:
• {tranid} -> SO12345
• {transactionnumber} -> 12345
z
Zack
04/02/2025, 2:28 PM
It seems weird that there is both. We had two different teams build integrations into our system to grab transactional data and one grabbed tranid and one did transactionnumber.
We are in a weird situation now where they don't match.
An example would be:
Tranid: 12345
Transactionnumber: 12346
The tranid is 1 lower than the number in all instances.
a
alien4u
04/02/2025, 2:34 PM
Most likely somebody modify or updated Auto-Generated Numbers at some point in your account.
• Setup -> Company -> Auto-Generated Numbers.
For what is worth, integrations and customizations should not relied on data that can change or be manually updated.
Best bet, always stick to immutable data points aka Internal IDs.
z
Zack
04/02/2025, 2:41 PM
Yeah, we are using internalid for the actual link, but we are displaying the doc numbers in a customer facing external platform. So the customers invoice email from NS doesn't match what they see in the external platform.
Luckily when they pay in the external platform, it links back to the proper invoice, but it's definitely causing confusing to them.
a
alien4u
04/02/2025, 2:42 PM
The most common field and the one used by default in many forms, searches and advanced PDFs print outs is {tranid}.
a
AK47
04/02/2025, 3:38 PM
@Zack The tranid is a system generated incremental number that can't be changed. Transactionnumber can be overwritten. As @alien4u mentioned, use tranid, but you should look into who is overwriting the transaction number and why.