Pulling the Role Hourly Rate into a custom calculation? | Community
Skip to main content
C
ChrisPe3
Level 2
May 25, 2021
Question

Pulling the Role Hourly Rate into a custom calculation?

  • May 25, 2021
  • 2 replies
  • 1439 views

Hoping someone can lend some guidance. I'm trying to pull the Role Hourly Rate into a custom calculated field, and I cannot get it to work.

Anyone else using this in a calculation? If so, how did you do it?

Using "role:billingPerHour" I'm able to pull it into a view and a report, but it's not working for the field.

Thanks!

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    2 replies

    jerflo
    Adobe Employee
    jerfloAdobe Employee
    Adobe Employee
    June 3, 2021

    @Chris Perrin‚ can you tell me more about this? What object are you trying to place the calculation on? What type of custom form are you using? What are you trying to accomplish?

    C
    ChrisPe3Author
    Level 2
    June 3, 2021

    @Jeremy Flores‚ We're trying to calculate a total on each task that is based on the role hourly rate, but we need it decoupled from the planned or actual hours. Essentially duplicating what planned/actual revenue are already doing. It's a task form.

    Thanks!

    jerflo
    Adobe Employee
    jerfloAdobe Employee
    Adobe Employee
    June 3, 2021

    @Chris Perrin‚ I see. Have you tried dividing the planned revenue by the planned hours to extract the rate?

    Caveat: This would only work well for tasks that have a single resource assigned. If you have multiple resources with multiple rates, the above will give you more of a blended rate.

    C
    ChrisPe3Author
    Level 2
    June 4, 2021

    @Jeremy Flores‚ We have, but the problem with that is that if I'm using any other rate (user hourly, fixed hourly) for the planned revenue, then we're getting those rates from that calculation, and not the role hourly rate. That's why we truly need it decoupled.

    I figured I could also utilize Fusion to look at the role:billingPerHour, and populate that into a new field, but I'd hate to use a Fusion flow for that when it feels like it should be doable right in Workfront.

    So, is it a safe assumption that this is not a field that we can pull into a calculation, even though I can pull it into a report or a view, and call it through the API?

    Thanks!

    Terms & ConditionsAccessibility statement

    Loading footer...