Add Same Field to the Same Custom Form Multiple Times

I have run into a similar scenario and the only way I could resolve it was to use the same numbering approach that you mentioned. I don't think you can add the same field twice because Workfront would have to have a "container" to store the data from each form field. Trish Sparkman DXC

Hi Tina and Trish, so this is true you can add multiple fields that are the same on your custom form. They will need an identifier to make them unique fields especially for reporting. Suggestion: we have several depts in our instance and I use abbreviations to represent the dept before field name. MKT - Lessons Learned; ADM - Lessons Learned MKT -Lessons learned - 1 (add a description so end users can see what your asking in multiple fields or don't be afraid to write out more on you title Lessons Learn from campaign; Lessons Learned from meetings; etc. just keep it short because if you report on this remember you want to read it quickly not a full sentence. if you want the field to be replicated I use numerics to the field. For example: Invoice -1; Invoice -2;, etc. just try to be consistent with nMing conventions so your field library is neat and you can understand who that field belongs to if you ever need it for another firm. Hope this helps and if there are better suggestions I would love to hear about it. This is just something we Found to work but always opened up fearing how others do this. Thanks Dawn Cejudo -WF -Admin inland Empire Health Plan Dawn Cejudo Sr. Application Specialist/Workfront Admin Inland Empire Health Plan Rancho Cucamonga, CA 909.890.5108

This is why I wished fields could be configured with a "Label" and "Fieldname" separately. So you could have multiple fields named "Lessons Learned" for tidy readability, and make the messy part on the backend: User Sees: Lessons Learned Actual Field Name on Backend: MKT_LessonsLearned Lessons Learned ADM_LessonsLearned01 Lessons Learned ADM_LessonsLearned02 Lessons Learned ADM_LessonsLearned03 ...and so on. This would also mean I wouldn't have to have field names like "What kind of collateral piece do you want to create?" and I could have "collateral_create" ;-) Kevin Quosig

They really need to fix this. I have a whole list of field names with 1, 2, 3 etc.... Dr. Rochelle L. Webb, CSM Interim Director, Project Management Office MHMR Tarrant County Ft. Worth, Texas 817-569-4146

Kevin, That would be an awesome idea to submit via the Idea Exchange. As for the why you can only have a field on the same form once, Trish nailed it. The data is stored in the database with a unique GUID, which is why it won't let you have it in there twice, you can only have the same GUID in the database table once. I had a customer of mine once set up a list of fields similar to the following: "Feedback field 1" - Do you need a second space for feedback? ()Y ()N - //display Feedback Field 2 if ()Y is selected// "Feedback field 2" - Do you need a third space for feedback? ()Y ()N - //display Feedback Field 3 if ()Y is selected// "Feedback field 3" And so-forth. This did require the customer to have a text field and a radio button field and then display logic set up to display if the Yes button is selected. Good luck! Dustin Martin Assigned Support Engineer Workfront

Here's the Idea Exchange on I upvoted a long while ago: The need is different (simplifying API calls), but the results would be the same: https://experience.workfront.com/s/idea/0870z000000PSfHAAW/detail Kevin Quosig

I upvoted it! Rochelle L. Webb, DM, CSM Interim Director, Project Management Office My Health My Resources (MHMR) of Tarrant County O – 817-569-4146 M - 817-897-3654 Confidentiality Notice: This e-mail transmission, and any documents, files or previous e-mail messages attached to it, may contain confidential information. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this message is strictly prohibited. If you have received this transmission in error, please immediately notify the sender by return email, and delete the original message from your system.

Upvoted this as well! Tina Plotner Project Coordinator Mountain West Farm Bureau

YES Kevin!! Upvoted :) Katherine Haven, PMP VP, Director, Business Technologies - PMO FCB