Converting Issue to Project in Fusion adding extra custom form | Community
Skip to main content
S
Stacey_Robertson
Level 5
October 9, 2024
Solved

Converting Issue to Project in Fusion adding extra custom form

  • October 9, 2024
  • 2 replies
  • 1702 views

I have a request queue, project template and fusion flow to convert an issue to a project and attach the template.  For some reason there is an extra custom form appearing on the projects that are converted in Fusion.  This form is not shown on the template being applied.  I have checked the request queue settings, template and fusion modules that convert to project (template field is blank) and add template (calling for the correct template). 

 

Are there any other areas I'm missing that could potentially add a custom form to the project in the process?  If I manually convert to a project using the same template, they are fine. I've even tried adding the form that is appearing to the template and then going back and removing it.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by KatherineLa

One particularly obscure WF feature is that if you try and complete a custom field on a record, but there doesn't happen to be a custom form with that field attached TO the record - Workfront will find an arbitrary form and attach it for you to try and be helpful so the data isn't lost. 

 

So do you have Fusion completing any fields as part of your scenario that it might be accidentally attaching that form to hold? I'd look at the converted project and see if there's one stray field on the form that happens to have data in it.

2 replies

Lawson02
Lawson02
Level 6
October 9, 2024

Custom forms are called categories in the API. It would most likely be in CategoryID. I would check the conversion module and see what boxes are checked, that's most likely where your issue lies. It may also be in a module after the conversion which updates the new project and the form got added by accident to either CategoryID (top most form) or objectCategories (array of all forms). There could also be a conflict with another scenario if you have one that adds that form.

S
Stacey_RobertsonAuthor
Level 5
October 10, 2024

Thank you for the response, I turned off all of the modules past the conversion to test and there are no fields being mapped during the conversion that are not native fields, only setting the name, owner and company.  It doesn't even reference a template to use but I'm still seeing this form appear when the project is generated. I went ahead and logged a ticket with support to see what they see, I appreciate the suggestions.

K
Community Advisor
KatherineLaCommunity AdvisorAccepted solution
Community Advisor
October 10, 2024

One particularly obscure WF feature is that if you try and complete a custom field on a record, but there doesn't happen to be a custom form with that field attached TO the record - Workfront will find an arbitrary form and attach it for you to try and be helpful so the data isn't lost. 

 

So do you have Fusion completing any fields as part of your scenario that it might be accidentally attaching that form to hold? I'd look at the converted project and see if there's one stray field on the form that happens to have data in it.

S
Stacey_RobertsonAuthor
Level 5
October 10, 2024

Thanks for the suggestions, I had checked that also.  I'm only mapping the owner, project name and company fields.  I even disabled any updates past the conversion to see what I would get and this form still appears even though no template was specified.

K
Community Advisor
KatherineLaCommunity Advisor
Community Advisor
October 10, 2024

That is truly odd then. I can't think of any other default setting that could possibly be over-riding it. When you look at the output of the conversion module, does it show anything about a categoryID in the output? Or is the mystery form being attached later, and not by Fusion itself?

Terms & ConditionsAccessibility statement

Loading footer...