Workfront module Convert object - custom form data

Good Morning,

Thank you very much for all the detailed replies!

In the meantime I received an answer from the support which which coincides with the answers given here.

---

Convert object: This action first converts the request and once the conversion is done, attaches the custom forms. This can lead to data loss because the form will be blank when it's attached. 

Misc Action → Issue → Convert to Project: This action ensures that the custom form is attached to the project at the same time as the conversion and allows you to transfer the custom data from one object to another. 

Regards
Lars

I don't think the convert module can, see below for technical reasons. I've always used the misc. action version, and to be honest never noticed the convert object module, I'm guessing it's a relatively recent addition, and it's missing the check-box to save that metadata onto the new object like the misc. action does.

The two modules behave very differently on the back. The convert to object makes 2 calls, however the misc. action module makes 4 calls, and the 2 calls that are missing are the ones that would be required to post the metadata, see attached. In fact, inspecting the "convertToTask" call, the custom field values aren't even included in the call. The missing calls are the calls that would make Workfront go find the custom forms that would be required for the converted object to have the same parameters.

Hello,

In the meantime I modified the Fusion scenario and exchanged the module Convert object to Misc action -> Issue -> convert to project. Now the values are filled into the new project.

This raises the question for me, what other differences there are between both approaches to use those modules?