Copying Fields and Preserving Selections | Community
Skip to main content
Jared_Mauch
Jared_Mauch
Level 6
May 11, 2026
Question

Copying Fields and Preserving Selections

  • May 11, 2026
  • 2 replies
  • 26 views

We have several product fields (multi-select dropdown) on custom forms used by different groups. One group would like to adjust the fields by adding new choices on them that won’t apply to the other groups. No deletion or renaming of existing choices is needed. These fields have been used on thousands of requests and projects by the group, and I’d like to keep that data intact for them. I know that changing the fields will change them on all the other groups’ forms. I’ve tried making copies of the fields in Preview to see if the copy carries over the original field’s selection, but it didn’t work. Is there a way to copy the existing fields for this group’s forms (requests and projects) so that the copies retain all of the previous entered data while also allowing me to add the new choices they requested?

2 replies

ninoskuflic
ninoskuflic
Level 4
May 11, 2026

Unfortunately no. The system will treat that as a new field and cannot cary over the values selected on a previous (different) field. You can add the values and use code to show/hide values with advanced display logic for XY groups if you’re on the new workflow package or if you’re not at least use the same code to prevent other groups from selecting those values if that helps?

If this solved your issue, please mark it as solved so others can find the solution faster.
Jared_Mauch
Jared_MauchAuthor
Level 6
May 11, 2026

Thanks for letting me know. I suppose the system won’t let me swap in new request and project forms with these updated fields and still keep the older forms attached to previous requests and projects?

ninoskuflic
ninoskuflic
Level 4
May 11, 2026

If you just update the custom form (that is already attached to a project/issue/task/etc.) it should not remove it from the object itself. But if you remove a filed that holds the data on those old objects, the value will be lost from the form as well. 

If this solved your issue, please mark it as solved so others can find the solution faster.
skyehansen
Community Advisor and Adobe Champion
skyehansenCommunity Advisor and Adobe Champion
May 11, 2026

This by the way, is one of quick little things that Fusion does for me. I’ve used it extensively to update fields in this type of situation and it has been such a timesaver. 

    Jared_Mauch
    Jared_MauchAuthor
    Level 6
    May 12, 2026

    I’ll add this scenario to the list of benefits Fusion can provide as I continue to ask for it.

    skyehansen
    Community Advisor and Adobe Champion
    skyehansenCommunity Advisor and Adobe Champion
    May 12, 2026

    got it. Well … if you’re doing benefits in terms of time spent on fusion vs manual time spent doing the task, it probably takes me about 15 minutes to set it up and test (it’s 3 or 4 modules for me), then about a minute to run each batch. Let’s say a batch is approx 1000 objects. So if you’re spending a minute editing 2-4 objects + potentially introducing error into the system, I’m spending the same minute editing 1000 objects, and then a few minutes afterwards doing spot checks and cleanup. 

    (this isn’t a fusion question but other more advanced practitioners would probably even just skip batching and go straight for iterating through the thousands of requests that you have)

    If this is more a case of “we don’t have $$$$ for Fusion per year, but we have $$ to fix this one specific problem”, you could probably call one of the adobe partners like Doug over at atAppStore. If your company is looking at it from the POV of, “we just need it to fix this one problem” you can probably just pay for 1-day’s worth of use of one of his apps and just get it done.

    Terms & ConditionsAccessibility statement

    Loading footer...