Expand my Community achievements bar.

Wondering how Workfront Proof works? Join our AMA on May 8th and ask our Community experts!
SOLVED

Carrying over request calculated field values to converted objects

Avatar

Level 4

I have a calculated field used to add a request tag to a request, based on user selections on the request custom form. The field is on a custom form that is attached to the queue topic. The field calculates great on the request but when the request is converted to a task or project, the calculation doesn't carry over and shows N/A in the task or project. The custom form containing the field is set for project, task and issue objects. A sample of the text mode is below.

 

IF({categoryID}="666902770070b579b760058a798a62b7",{DE:Mail-Email-Outreach Request Type},

IF({categoryID}="66673189002fd1bf87687601fe100381",{DE:Existing Email-Mail List Request Type}, "N/A"))

 

Is there any way I can add to the text mode so the calculation carries over to the request custom form with the calculated field, which is linked to the converted task or project? I would like to see the request tag calculated field when in the converted task or project. Thanks!

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

this kind of calculation is dynamic -- recalculating as you go. My guess is that it's going to N/A because your project's first custom form is not the same as your request's first custom form.

 

For a more permanent solution, you should look into utilizing some sort of "IF(!ISBLANK" somewhere into your calculation. A quick example is something along the lines of:

 

IF(!ISBLANK({DE:Your calculated field}),{DE:Your calculated field},<Your original calculation goes here>)

 

In other words, if this field is not blank, then keep the value as it is, otherwise if it's blank, make the calculation happen.

View solution in original post

3 Replies

Avatar

Correct answer by
Community Advisor

this kind of calculation is dynamic -- recalculating as you go. My guess is that it's going to N/A because your project's first custom form is not the same as your request's first custom form.

 

For a more permanent solution, you should look into utilizing some sort of "IF(!ISBLANK" somewhere into your calculation. A quick example is something along the lines of:

 

IF(!ISBLANK({DE:Your calculated field}),{DE:Your calculated field},<Your original calculation goes here>)

 

In other words, if this field is not blank, then keep the value as it is, otherwise if it's blank, make the calculation happen.

Avatar

Level 4

Thanks! That's a great idea. I'm going to try adjusting the calculation to include "IF(!ISBLANK", as you suggested.

Avatar

Level 4

I got it to work with a slight adjustment to your suggestion by adding {convertedOpTask} to my calculated field. 

 

IF(!ISBLANK({convertedOpTask}.{DE:my calculated field}),{convertedOpTask}.{DE:my calculated field},<Your original calculation goes here>
Thanks very much