Expand my Community achievements bar.

Our latest Cookbook on Adobe Workfront Fusion is here!

Copying a Field in a Custom Form

Avatar

Level 3

01-03-2023

Description - I have a field that I would like to duplicate and rename without having to create another field manually. Example - I need to manually create fields with drop down options on the open/close time for one of our specific locations (this can get extensive when building it out for each day of the week). 

Why is this feature important to you - It would save me a ton of time when building out custom forms.

How would you like the feature to work - Have an option within the custom form area to copy existing fields (and rename them) similar to how you are able to do this with templates, projects, tasks, etc.

Current Behaviour - Inability to copy custom fields (need to manually create each).

 

5 Comments

Avatar

Level 10

03-03-2023

Hi @Kiesner10 

In addition to the benefits you mentioned, it would be useful if Adobe were to add a feature that allows users to create folders to keep their forms organized and easily accessible. It would also be helpful if users could grant access to others to manage these folders. Currently, copying similar fields is a time-consuming process, and navigating between pages can be tedious.

 

With this new feature, I suggest that when a user copies a field, they receive an alert if the field has the same name and type as an existing field. This would help to avoid confusion and ensure that the field is created under the correct type, such as task or issue.

 

Mvh

Kundan.

 
 
 

Avatar

Level 3

03-03-2023

Hi @Kundal - Those are some great additional call-outs! I agree that it would be very helpful to have folders to keep custom forms organized. It would be ideal if there was an alert when someone makes a copy of the custom field to ensure that there are no two that are exactly the same (and avoid confusion). 

Avatar

Community Advisor

06-03-2023

Another feature I'd like to see related to this is if you create a custom field with exact same name as a native field, you'd receive at the very least a warning, preferably not be allowed to create a custom field with that same name.

Avatar

06-03-2023

 

Agreed @Heather_Kulbacki; and for the uninitiated, may I invite you to elaborate on why it is best practice to avoid naming a custom parameter with the same name as a native field?

 

Regards,

Doug 

Avatar

Community Advisor

06-03-2023

Good call out @Doug_Den_Hoed__AtAppStore having both a native and custom field with the same name makes for a reporting nightmare - and reporting includes creating any filter/view/grouping on any list, not just strictly in the reporting area.

You don't know which field to pull into your report when 2 have the same name until you've tried them both to see which one gives you the data you're looking for.

It can also create the same nightmare for integrations, which field are you trying to populate or which one are you trying to pull data from - with the exact same name, there is no distinction.