Viewing Calculated issue filed >> Converted Project >> Hours Report | Community
Skip to main content
M
MattWindsor
Level 3
May 8, 2025
Solved

Viewing Calculated issue filed >> Converted Project >> Hours Report

  • May 8, 2025
  • 1 reply
  • 485 views

Hi Community,

 

I'm trying to add a Primary Contact of a issue onto an hours report, but can't make it work. We are using a request queue, converting that to a project, and want the Primary Contact to show on the report.

 

So far, I've added a calculated field onto the custom form and when the new requests come through this is correctly showing the Primary contact (not the  request entered by user). This is good.

 

The problem is when the issue is converted to a project, the calculated field updated to to the owner of the project, which then shows on the report. This is quite annoying! Lol

 

The calculated field I'm using {owner}.{name} and I assume this is recalculating tot he project owner.

 

I've also tried using a collection, but couldn't get the resolvables nested statement to work.

 

Any help will be very appreciated.

Thanks

Matts

 

 

 

 

 

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 is getting a bit complicated since you wish to change the primary contact after the request is submitted. (it means you need to set the calculated field in stone much later in the process)

 

If the only thing you want, is to get it on the report, you should just use your text mode in your view.

 

For this, there's no need to use a collection. The request-to-project link is a 1:1 link, not a collection. i.e. you should notice that you cannot convert multiple requests into 1 single project. Only 1 request gets converted to 1 project.

 

Therefore you should (or can) just go with sample textmode in your view column, like this:

 

valuefield=project:convertedOpTask:owner:name
valueformat=HTML

1 reply

skyehansen
Community Advisor and Adobe Champion
skyehansenCommunity Advisor and Adobe Champion
May 9, 2025

Have you thought about throwing an ISBLANK expression in there, somehow? It would work similar to this:

https://experienceleaguecommunities.adobe.com/t5/workfront-questions/carrying-over-request-calculated-field-values-to-converted/m-p/747657

M
MattWindsorAuthor
Level 3
May 9, 2025

Hi Skye,

I've tried, oh how I've tried, but can't make this stick. I've followed the example in the link but I must be doing something wrong in the set up.

I've created the first field to capture the Primary Contact {owner}.{name}

The calculated filed is written as this... 

IF(!ISBLANK({convertedOpTask}.{DE:C+D Original Issue Requestor}),{convertedOpTask}.{DE:C+D Original Issue Requestor},{owner}.{name})
When the issue is created and the Primary Contact field amended, then this shows correctly in field 1. Second sets to enteredBy which I'm also ignoring.

 

But when the issue is converted to a project, the first field updates to the project owner (which I don't mind as I shouldn't be using that. But the second which I'm planning to pull into my report also updates to the project owner.

Do you have any ideas how to fix this please?
I'm sorry this is so long and thanks for your time.
Matt

skyehansen
Community Advisor and Adobe Champion
skyehansenCommunity Advisor and Adobe ChampionAccepted solution
May 10, 2025

This is getting a bit complicated since you wish to change the primary contact after the request is submitted. (it means you need to set the calculated field in stone much later in the process)

 

If the only thing you want, is to get it on the report, you should just use your text mode in your view.

 

For this, there's no need to use a collection. The request-to-project link is a 1:1 link, not a collection. i.e. you should notice that you cannot convert multiple requests into 1 single project. Only 1 request gets converted to 1 project.

 

Therefore you should (or can) just go with sample textmode in your view column, like this:

 

valuefield=project:convertedOpTask:owner:name
valueformat=HTML

Terms & ConditionsAccessibility statement

Loading footer...