Calculated Expression displaying incorrect value for Task's Estimate field | Community
Skip to main content
NicholasSily
NicholasSily
New Participant
June 17, 2024
Solved

Calculated Expression displaying incorrect value for Task's Estimate field

  • June 17, 2024
  • 1 reply
  • 1262 views

I have the following text mode for the column in the task report:

 

valueexpression={estimate}*{percentComplete}
textmode=true
valueformat=HTML
displayname=Calculated

 

 

on another column I'm using a valuefield, to show the estimate , which is a double. and it is appearing correctly, however when using the valueexpression approach the field shows as "0.0". This only happens for the estimate field, since I've tried with others and they showed the same information, regardless of valuefield or valueexpression approach.

 

 

Let me know if the text mode looks correct, or if anyone know what could be causing this issue

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 NicholeVargas

Hi Nicholas - I did some digging last night see what I could come up with. It appears to be something with the estimate field itself. I found this: The estimate field is a derived field and not an actual field in the system. 

 

I wasn't able to get the field to work in any kind of calculation and even tried a calculated custom field. Tagging in @nicholevargas to see if she knows why the field can't be referenced in a calculation.


Thanks for tagging me, @kelliegardner! @nicholassily The field for estimate, is a dynamic field in the API which means it cannot be manipulated in valueexpressions. I've asked the Technical Writing team to update our documentation and make that more clear, and if possible, list out any fields that are dynamic to avoid any confusion.

 

1 reply

KellieGardner
KellieGardner
New Participant
June 17, 2024

Text mode looks fine. You've confirmed that both your estimate and percent complete fields are showing something other than a zero?

NicholasSily
NicholasSilyAuthor
New Participant
June 17, 2024

Hey Kellie, yes indeed it's not supposed to be 0.

 

When I use the valufield the estimate displays the correct value as a double, however when using the field within a valueexpression, no matter what the expression is, it shows 0.

KellieGardner
KellieGardner
New Participant
June 17, 2024

We don't use the estimate field in my instance so I can't really test anything on my end as the values are all 0. But if the fields you are calculating both show something other than zero then when multiplying I would venture to assume it should return a value. 

 

Example: Your estimate field is a value of 1 and your percent complete is a value of 10 and when you run the calculation it should return a value of 10. 

 

If it's returning a zero when it should return a value (like in my example) then it might have something to do with the estimate field available through the API. I don't see any real documentation around it. 

 

 

Terms & ConditionsAccessibility statement

Loading footer...