Calculated field with $$OBJCODE doesn't get recalculated | Community
Skip to main content
tibormolnar
tibormolnar
Level 4
August 18, 2025
Question

Calculated field with $$OBJCODE doesn't get recalculated

  • August 18, 2025
  • 2 replies
  • 398 views

Hi All,

a calculated custom field of mine is behaving like a bad boy. Can someone please help me with taming it? : )

I have a form that is attached both to the Task and Issue objects.

The form contains a calculated field (called ObjcodeDebugCombined) that is meant to flag up if certain settings on the Task/Issue record are not aligned to the expectations, i.e.:

  • On a Task: the Task Constraint is not "Fixed Dates" OR the Duration Type is not "Simple"
  • On an Issue: the Issue type is not "Request"

Here's the calculation:

IF(($$OBJCODE="TASK"&&({durationType}!="S"||{taskConstraint}!="FIXT"))||($$OBJCODE="OPTASK"&&{opTaskType}!="REQ"),"failed","")

 The problem is that this field is not recalculated when it should be. More precisely:

  1. When a Task/Issue record is created (with the custom form attached), the field is calculated correctly.
  2. When another custom field is updated on the Task/Issue record, it (ObjcodeDebugCombined) is recalculated properly.
  3. When a native field (e.g. name, planned start date, etc.) is updated on the Task/Issue record, it is not recalculated.
  4. When I click "Recalculate Expressions" on the Project, it is not recalculated.
  5. When I click "Recalculate Expressions" on the Task/Issue, it is recalculated.

The problem is scenario 3., because updating the Task Constraint / Duration Type / Issue Type field falls into this, i.e. updating those does not trigger the recalculation, so ObjcodeDebugCombined shows "failed" even after the user has fixed the incorrect setting.

I believe that the problem is related to the $$OBJCODE wildcard, because when I created similar fields without it, separately for the Task and Issue records, those just worked fine:

IF({opTaskType}!="REQ","failed","") IF({durationType}!="S"||{taskConstraint}!="FIXT","failed","")

Obviously I need a single field that works for both Tasks and Issues.

I appreciate any ideas.

Thank you,

Tibor

2 replies

skyehansen
Community Advisor and Adobe Champion
skyehansenCommunity Advisor and Adobe Champion
August 19, 2025

Are you sure it's failing?

 

What I see, if I copy the calculation straight into my preview sandbox is that the calculation is initially successful, and if I change the system fields (for task constraint, issue type, or duration), the calculation will temporarily change accurately and then flip back to what it was either several seconds later or when I refresh the screen. Which potentially indicates a bug of some sort. I recommend if you can, to try and catch it in a recording and send it in to the Workfront support team for more review.

    tibormolnar
    tibormolnarAuthor
    Level 4
    August 27, 2025

    Hi @skyehansen ,

    thanks for confirming that it's not working as expected for you either.

    I've created a screen recording and submitted it to Adobe. Will post an update here when I hear from them.

    Tibor

    tibormolnar
    tibormolnarAuthor
    Level 4
    September 12, 2025

    Hi @skyehansen ,

    FYI, Adobe has confirmed that this was a bug and they fixed it.

    My calculated field now gets properly recalculated every time a native or custom field is updated on the Task/Issue record.

    Tibor

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    September 1, 2025

    @tibormolnar just checking in! Were you able to get this resolved? If one of the replies above helped—whether it completely solved the issue or simply pointed you in the right direction—marking it as accepted can make it much easier for others with the same question to find a solution. And if you found a different way to fix it, sharing your approach would be a great contribution to the community. Your follow-up not only helps close the loop but also ensures others benefit from your experience. Thanks so much for being part of the conversation!

    Kautuk Sahni
    Terms & ConditionsAccessibility statement

    Loading footer...