Is there a custom field that can generate a unique number. We have a use case where we need a unique number generated but leveraging reference numbers on tasks, issues, projects, etc. may not be a sustainable solution.

[RandyRoberts]

I've been asking for this for years! I'm sure it's in the idea exchange somewhere.

It would be perfect for job numbers.

[CalvinFold]

@Lila Whitney‚, a common ask, but no.

They used to long ago, but changed it so that all objects have unique numbers across objects. It's a really common ask, and there is an Idea Exchange entry going back a couple years:

https://one.workfront.com/s/idea/0870z000000PSAoAAO/detail

I even provided an outline of how it might accommodate advanced features.

[ljanz]

It would be a great custom field option! Relying on the reference numbers is NOT sustainable. I was really disappointed when they decided to not make sequential numbers an option. I wish they would look into it again. It is such a COMMON ask.

[ljanz]

Just found this in the Idea Exchange, too: https://one.workfront.com/s/idea/0870z000000XhZOAA0/detail

[-WE]

Do you just need the number to be unique, or do you also need it to be sequential? Everyone in the thread is talking about sequential numbers (which is a common request and is possible with Fusion); but if you only need the number to be unique, there are several potential methods and no Fusion required. Happy to share a couple methods that we use if "unique" is the primary requirement.

[CalvinFold]

Unique, sequential, and without Fusion. Such as sequential project numbers.

[K_Donkers]

I agree with what Kevin stated (unique, sequential, and without fusion). Our customers use the unique number to interact with us so there would also need to be a way to provide this to them in email communications and their submission tracking. With the large volume of work that we do (approx 700 projects a month), we needed a short term solution to get by. We built a custom form field that gets copied from the request (submitted by a customer) to the project. It is based on the request reference number because that is what is sent to the customer. We have no way to control our email messages which also causes issues. Any solution for a unique number would also need to include some control over how that is presented to the customer. The other issue we see with our current solution is that the numbers are growing exponentially and we are worried our archiving system will not be able to accommodate the extremely long numbers at some point. It is creating a great deal of angst for our users and owners of other systems.

[Doug_Den_Hoed__AtAppStore]

Following this one folks; for years, in fact.

So: having mulled it over a lonnnnng time, this morning, I worked out a solution. It is crude, but effective, and will allow anyone to enter a unique, sequential number without Fusion (i.e. for free). Accordingly, it will come with no support, several cautions, and no apologies...but those for whom it will suffice are welcome to use it As Is.

I will submit it at my earliest opportunity under a post called “You want unique, sequential, without Fusion (i.e. for free)? Fine: then do this.”

Regards,

Doug

[ChristineZh]

Piggybacking onto this thread – does anyone know if there's a better way to reference an expense on a project than the crazy long expense ID? It would be great for a PM to be able to reference or check up on the status of an expense using this unique ID.