I’m noticing that the Transaction Number field (TransactionNumber) on Journal Entries doesn’t seem to be unique and can be repeated for multiple different GLs that exist within a particular company. Why is this? Is there a recommended way to uniquely identify GLs other than by their nwId?
An Automatic Number such as the TransactionNumber on General Ledger does not need to be wholey unique. In the Automatic Number Definition application you are provided levers to pull which indicate uniqueness.
In the case of GeneralLedgerDetails, the number is unique by TransactionType as it is defined as the dependent field on the Automatic Number Definition but also by the line number as defined by the Unique Index of the table.
Other Automatic Number Definitions might use a company, organizational unit, order type, etc… to keep Automatic Numbers unique by those traits.
Thanks @Aaron.C … so what I’m seeing is there are 195 different Automatic Number Definitions over the GeneralLedgerHeader/TransactionNumber field, each incrementing individually, but, not appended with a type or anything. I find that a bit curious why Nextworld wouldn’t mark the first Accounting Currency Adjustment transaction as something like “ACA-00000001” instead of just “1”. Could a customer implement such a scheme for their GLs if they were so inclined?
@ian.p Dependent Field and Dependent value are Available Hidden fields on the app you screenshot. When a dependent field is defined you must create an Automatic Number Definition for every value combination desired to be unique. TransactionType happens to be a quite large Key/Value Set
As far as the Number Format. I wouldn’t be the right person to speak to that piece other than if the customization pattern allows for Number Format then I would think a customer would be able to create and link a format such as the one you suggested to the Number Definition through customization