Best approach for selectively transferring custom fields from request to project level.... | Community
Skip to main content
A
ab_cdef
Level 3
March 8, 2025
Solved

Best approach for selectively transferring custom fields from request to project level....

  • March 8, 2025
  • 2 replies
  • 866 views

This is more of a strategic question rather than a technical issue.

 

I have a custom form at the request level that contains hundreds of fields. When a request is converted into a project, I need to retain about 95% of those fields but exclude a few that would only cause confusion at the project level.

 

If I needed to transfer all fields, the solution would be straightforward - I’d simply make the custom form at both the request and project levels and attach it to the project when doing conversion in Fusion.

 

However, since I need to exclude a handful of fields from the custom form, what’s the best approach? My plan was to create a separate project-level custom form containing only the required 95% of fields and use Fusion to map the data accordingly, but considering the number of fields, this could become a time consuming/tedious task.

 

Is there a more efficient way to handle this? Any insights or past experiences would be appreciated!

Best answer by Sven-iX
create a separate project-level custom form containing only the required 95% of fields

This is the way. When you convert an issue, and use a template that has the 95% project form, only the project fields get populated. This even works when you manually convert an issue and add the 95% form.

2 replies

Sven-iX
Community Advisor
Sven-iXCommunity AdvisorAccepted solution
Community Advisor
March 8, 2025
create a separate project-level custom form containing only the required 95% of fields

This is the way. When you convert an issue, and use a template that has the 95% project form, only the project fields get populated. This even works when you manually convert an issue and add the 95% form.

    A
    ab_cdefAuthor
    Level 3
    March 9, 2025

    First of all, thank you @sven-ix  & @doug_den_hoed__atappstore for your input!!

    And @doug_den_hoed__atappstore, moving the 5% to an admin-only view and edit section is a fantastic idea!

    @sven-ix , I just realized that in my case, the project is not created by converting the request but is instead a completely new object. Given that the request and project are not directly connected, is there a way to copy 95% of the custom fields from the request to the project?

    As I understand it, the "copy custom forms"" feature in Fusion wouldn't work in this case.

    So.... is there an alternative way to achieve this?

     

    Sven-iX
    Community Advisor
    Sven-iXCommunity Advisor
    Community Advisor
    March 9, 2025

    Rats - then you need to use Fusion and map the fields from object the the other

    How come the request is not being converted? 

    Doug_Den_Hoed_AtAppStore
    Community Advisor
    Doug_Den_Hoed_AtAppStoreCommunity Advisor
    Community Advisor
    March 8, 2025

     

    Hi @ab_cdef,

     

    I concur with you and @sven-ix, and if you're looking for the easiest path, suggest you manually copy Form Full as Form 95 Percent, then delete the 5% you intend to exclude...or (noting such an exclusion does indeed lose data) move them to a special Save Just In Case section within the form, viewable and editable by Only SysAdmins, if this half of the sentence resonates.

     

    Regards,

    Doug

      Terms & ConditionsAccessibility statement

      Loading footer...