Hi @_Manish_Singh, @MartaSo is correct in that the Light license does not allow for create or delete with tasks. See screenshot below:   

Wanted to pipe up on an issue we ran into in case it helps anybody else.  On the "Select" package, which we chose, it was specified as not having "Advanced enterprise controls". When we questioned what "Advanced enterprise controls" meant, we were given a screenshot of and link to the Actions allowe...

Description - Allow the ability to sort the list of projects in Timesheets by their program's name and not simply the projects' namesWhy is this feature important to you - It would be helpful for users on a wide array of projects to be able to "lump" all of the projects from one program together. Ri...

Hi @Scott_Goodwin, thanks so much for starting me down this path. Was able to take an hour this aft and dive into API calls. Incase anyone else is a newbie on this topic like me and can learn from my experience, here's the steps I took using my fields "Form number" and "Form #" as examples: Generate...

Hi @skyehansen, thank you, appreciate the link - not sure a) I can convince my org to pay for a solution, and b) if this solution can run with SSO configured (at least I can't get tests from Doug's site to work as we don't have passwords with SSO configured). Hopefully it can help someone else thoug...

Hi @Scott_Goodwin, no, they're on two version of a "project details" custom form. So for example, there's Department 1 Project Details custom form with "Form number", and Department 2 Project Details custom form with "Form #". The two custom forms do have shared fields as well as the overlapping/dup...

Hi @Scott_Goodwin, thanks for chiming in. We're just starting to explore all the overlapping fields but most of them live on the project level. Anything you can think of given that knowledge? Many thanks.

I have a scenario where two separate departments were using our Workfront instance and created multiple similar fields for the same types of data (for example, one department had a field called "Form number" and the other had a field called "Form #"). We'd like to do a mass clean-up and consolidate ...

Super fair!! The user I'm deactivating IS a system admin, so it makes sense in this scenario, but even for myself as a core admin it's worth considering cleaning up my own "Run As" reports. 500 reports - that's a darn shame!! Job security? Haha. Thanks again!

Many thanks @KellieGardner, appreciate it!