cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

New field type

New field type

There should be a field type that numbers documents in a sequential order and is unique.
9 Comments
rania
Advocate
That automatically numbers documents*
dany.poudrier
Alumni

Do you mean like a sequence number so that each document under a workspace would be uniquely identified?

 

Can I ask how would you use that sequenctial number?

rania
Advocate

Hi Dany,

 

I am just seeing your response here - I would like a field that is like the autonumber field but that is guaranteed to be sequential. We use the autonumber field to number items in several different workspaces, and since we are a regulated company, missing numbers is a big issue for us. I know that there is a "work around" by using a sequencer scripting, however, I prefer to use features that are already built into the system. I think it will definitely make the system better as I am not sure why someone would want to use an autonumber field if it does not guarantee it will be sequential.

gasevsm
Alumni
Hi Rania,
You make a great point~! I foresee us not introducing new auto field, but augment the existing one to offer a strict increment of 1 option. Right now, the Sequencer last down the bits of this logic given the permutations of what users think of intelligent or significant part numbering scheme. Please consider adopting this model as it guarantees uniqueness across the tenant, and strict +1 increments.
Regards,
gasevsm
Alumni
Hi Rania,
You make a great point~! I foresee us not introducing new auto field, but augment the existing one to offer a strict increment of 1 option. Right now, the Sequencer last down the bits of this logic given the permutations of what users think of intelligent or significant part numbering scheme. Please consider adopting this model as it guarantees uniqueness across the tenant, and strict +1 increments.
Regards,
mpasumarti
Advocate

@gasevsm, It would of great help if you extend Autonumber field to take a prefix (preferably alphanumeric) and suffix (may be useful for some customers) along with a sequence number of required length. We are currently using script auto sequencer to auto-generate numbers such as CN18NNNNN, CR18NNNNN, CAPA18NNNNN, PNAF18NNNNN, etc., (where N is a number from 0-9) for various workspaces. In fact we are using two digit year number immediately after prefix. Addition of this feature could also be useful to customers like us.

gasevsm
Alumni
Hi sir. I totally agree we should have Sequencer or autonumber field embelished with all native in-product sequencer and pre,post padding rules, including being responsive and accountable for revision controlled items and importing number skipping rules. This isnt on our roadmap presently. As we free up cycles and start discussing next year deliverables in the later part of this year, we will consider the efforts. Meantime, Sequencer object gives us the most flexibility and control to define level of significance into a part number. Regards,
benderk
Autodesk
Thank you for submitting your idea. Have you tried the Modern Interface lately? We request that you review your idea in the context of the Modern interface. If your idea is not addressed, we invite you to create a new Idea in the context of Modern so that it can be addressed accordingly. Sincerely, Keri Bender | Global GTM Business Strategy Manager, Product Lifecycle Management
benderk
Autodesk
Status changed to: Archived
 

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea