We use autonumbering for our transactions, with pr...
# general
j
We use autonumbering for our transactions, with prefixes, e.g. IV13455 for Invoices. We’ve recently enabled OneWorld and we now have multiple subsidiaries that will be creating transactions in the system. We’d like to keep a common number sequence across each transaction type, but prefix the tranid values with a subsidiary-specific prefix, such as “SubA-“, “SubB-“. I’d expect to get records that look like this: SubA-IV13455 SubB-IV13456 SubC-IV13457 SubA-IV13458 SubA-IV13459 I thought that enabling Subsidiary-Specific Transaction Auto-Numbering would achieve this, but instead we are ending up with this: IVSubA-0001 Two issues here: the numbers are reset to 1 and seem to have a different increment tracker for each Subsidiary, and secondly the Subsidiary prefix is coming AFTER the Transaction Number prefix. Any suggestions on how to achieve our desired naming convention using AutoNumbering?
m
1-Disabled numbering by sub 2- readjust the invoice number to have only basic number like IV13455 3- Use workflow to set field value : field Ref No and check formula : {subsidiary} || '-' || {tranid}
j
if AutoNumbering is on, can you override the tranid?
m
Don’t think but you can disable the feature
j
but then it won’t generate the right number
we need to keep the number sequence, as we have 14 years of data already
m
If your last number is IV13455 with auto numbering , you can use a prefix for invoice like IV , update the initial number and enter the value 13456 So if you generate a new invoice , the number is IV13456 Then you can use the wf
j
you said to override the tranid I’d have to turn off autonumbering though
1
m
I replace the tranid with a formula that concatenates the tranid with the subsidiary. If an invoice have this reference IV13455 for the SUB C, then the value after the wf will be SUBC-IV13455
Try in your sandbox
j
Maybe I’m confused, but you are saying to achieve this I’d have to turn off autonumbering. If I turn it of, the numbering of the records won’t be correct though.
m
Have you looked at the Advanced Numbering feature? It's pretty new and I'm not really across it, so I"m not certain if it will solve your issues, but it supposedly offers a lot more flexibility with the numbering rules.
👀 1
j
I’ll take a look, thanks for the suggestion
m
I'm confused, I misread. I thought you were talking about the Advanced Numbering feature, not Auto Numbering. But of course, you should leave Auto Numbering enabled and create a workflow as I explained. I tried it and it works correctly.
Having Auto Numbering enabled does not prevent the modification of the tranid.