autonumber field - docket numbers

Being a new Workfront user and just working through Implementation, I am disappointed with the lack of numbering and even more so with their short sightedness of having a more diverse customer base than they had years ago. Very unfortunate.

We have a work around but this would be much better for us.

We add the year to the front of the Project Number, so our reference is P18_______

We could reuse the same sequential numbers every year and just change to the Year at the front. Love this idea!!!

@Anna - that totally makes sense! Yet, what people are looking for is essentially a calculated field that counts up from 1, with maybe some minor additional functionality (such as setting the base number, # characters, and a set of leading characters or numbers). We need both a backend system of truly unique IDs and a more rudimentary system that is easy for anyone to reference.

Workfront users and admins will definitely make mistakes using a more basic numbering system - guaranteed (myself included!), but it's still something that is easily available on other, similar systems. Again, keeping the 32-character Unique ID system will guard against major issues. Please reconsider!

LOL, community's down and it's sending reference ids for every refresh.

Reference ID: f5a6df72-a54a-11e8-b815-0a4ccd35c2c7

Reference ID: 144f7024-a54b-11e8-9d38-0a4ccd35c2c7

Can you imagine XX years from now, what possible reference numbers you'd be looking at on Workfront ?

I hope that WF will reconsider. We leverage the project reference number as a primary key to search for all of our projects. With the current volume of objects this number will grow exponentially and will become unreasonably long. Our only other option is to pursue a customized code generator or purchase Fusion.

I agree. I'm pretty sure there's more use to setting up a field with unique sequential numbers. It's disappointing to see Workfront's reply to this. We're not asking them to remove the current use of their reference number as I'm sure some users are already using it because they had no other recourse but to use a 6 - 8 alphanumeric code that had no rhyme or reason as it relates to the object.

I'm surprised at the official reply to this, why not have a unique field that auto populates a unique sequential number for projects within a particular group/request queue. The existing numbering system creates very long numbers over time which we have to concatenate and join with other information to create something (hopefully) unique. There's no need to remove the existing system, this would be an addition to it.

@Anna Asaytryan - 4 years ago, your user base may have been different from what it is now. There must be a way for us to have an autonumber field - maybe by calculated fields of some sort, not necessarily permanently attached to the object like the current reference number.

We were considering a customization to append a Job Number (year followed by a 5 digit sequential number, i.e. 18xxxxx) to end of the project name so that it can be visible at all times. Each year we would start the 5 digit sequence over again.

Now that it is under consideration by WF perhaps we will wait and see their solution.