Expand my Community achievements bar.

The next phase for Workfront Community ideas is coming soon. Learn all about it in our blog!

Can project custom form info be pulled into a task custom form?

Avatar

Level 4
Hi there, Is there a way to have data from a project custom form appear in the task version of the custom form within the same project? We have a standard series of field that we use to define projects (market, product line, asset type, etc.). We also have a task to define where the asset needs to be posted (on our website, our partner portal, a customer portal, etc.). Several of the fields are the same in both instances but there are additional items for the Task form specific to where the item is being posted. As a result, we want to have some of the same fields in both the project form and the task form so the person carrying out the task doesn't have to flip between task and project forms for the information. So my question is: Is it possible for a task custom form to be populated with the same data as a project form so we don't have to complete the fields twice or is that only possible when, like with an Issue conversion to a Project, there is an active field mapping process underway? If not, we'll likely leave them split and have the person flip back and forth OR we'll build the items for the task into the project form so the worker will lease the task and go to the project details to see where an asset needs to be posted. Thanks in advance, Chris Watson KVH Industries, Inc.
5 Replies

Avatar

Level 10
So far, the only way for data from the project's custom form to show up at the task level is by using a calculated field and the results aren't satisfying for me. Changes to the project's custom form would fail to populate at the task custom form level unless the task custom form was re-saved. title= >https://experience.workfront.com/s/article/Using-Calculated-Custom-Data-936956366 The other option is to use Home and have the project custom form fields placed at the task level using layout templates. This gives you up to 16 fields (I think), so as long as you stay under that total, and as long as everyone agrees to use Home, you're all set. title= >https://experience.workfront.com/s/article/Creating-and-Managing-Layout-Templates-1976479577#customi... -skye

Avatar

Level 10
Hi Chris, Further to Skye's sage advice... Should you go the calculated parameter route, I invite you consider our ad-hoc "https://store.atappstore.com/product/recalc-helper/">Recalc Helper and/or schedulable "https://store.atappstore.com/product/force-custom-data-double-recalc/">Recalc Parameters solutions to mitigate the stale data risk mentioned in the above help article. Alternatively -- and similar to her Home concepts -- you could either a) create a Task Report (and perhaps convert it to a >Custom Tab ) that includes the Project Fields of interest for reference, or if it's more convenient b) create a "https://wf-pro.com/2018/12/05/shared-columns-how-to-video/">shared columns Project Report to show the Project Level information (once) at the top of a Custom Tab, then followed by a report with the Task information of interest (for editing). Regards, Doug Doug Den Hoed - AtAppStore Got Skills? Lend a hand! https://community.workfront.com/participate/unanswered-threads

Avatar

Level 9
I have created a project level report and inserted it as a custom tab per layout so it's always within each project. For one specific type of project, I've also taken the second route (shared column report) that you mentioned Doug. However - I thought there was no in-line editing possibility in task reports. Christina Jarosz Ascensus

Avatar

Level 10
Hi Christina, I'm likely misunderstanding something, but (to restate, with a pictograph, below)...what I was suggesting includes both Project info with Shared Columns (for reference) and editable Task info. Regards, Doug Doug Den Hoed - AtAppStore Got Skills? Lend a hand! https://community.workfront.com/participate/unanswered-threads

Avatar

Level 2
We create three versions of every custom form (project, task, issue) and use the same fields on each form. So we don't have twice the numbers of fields; we have thrice the number of forms. This allows the information to be entered once and shown on all the objects. We developed taxonomy for naming the forms:
. so that the right form is added to the right object. For example, Article Review.Project, Article Review.Task, Article Review.Issue. It's a little cumbersome, but now we are used to it. Tami Johnson SAIF Corporation 503.373.8702