Carrying over request calculated field values to converted objects | Community
Skip to main content
Level 4
April 9, 2025
Solved

Carrying over request calculated field values to converted objects

  • April 9, 2025
  • 1 reply
  • 490 views

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!

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 skyehansen

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.

1 reply

skyehansen
Community Advisor and Adobe Champion
skyehansenCommunity Advisor and Adobe ChampionAccepted solution
April 9, 2025

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.

CBuckwalAuthor
Level 4
April 10, 2025

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