It does seem peculiar that Workfront read your request as a rollback of existing functionality rather than a request for something new. Perhaps they simply feel that two unique identifiers (GUID and Reference Number) are plenty for any object, and they don't want to create more overhead with a third one. Lots of different use cases were presented in this thread for identifiers in various forms. (We too had a custom-built project identifier, but we decided to scrap it when we transitioned to Workfront, as we could handle all that information via reporting and custom data fields. The executives needed some persuading, but we are totally accustomed to 7-digit reference numbers now. For us, the number is important only for its uniqueness.) My suggestion for those who want "special" sequential job numbers is to use the API to auto-create your own special brand of job number and then populates it into a custom field. Or perhaps Doug Den Hoed at the AtAppStore already has a solution that can do something like this...? ~Eric Eric Manning Language Line Translation Solutions