Historical Hourly Cost not used in report custom columns

  • 1
  • Question
  • Updated 1 year ago
  • Acknowledged
We just encountered this issue also, and Naresh from Replicon support confirmed that this field is still not date-sensitive to pull the correct cost at the time each hour was actually incurred.  So, I logged in here and am disappointed to see a status of "Not Planned". If that field isn't date-sensitive, and therefore not pulling the correct hourly cost for each hour, than any and all reports with cost/profitability information are meaningless.

Note: This conversation was created from a reply on: Hourly Payroll cost is not calculated with the effective date.
Photo of kdurliat

kdurliat

  • 33 Posts
  • 7 Reply Likes

Posted 1 year ago

  • 1
Photo of Derek

Derek, Product Manager

  • 21 Posts
  • 2 Reply Likes
Hi kdurliat,

I understand that when you use the Hourly Cost field in the report you get the desired results, and this is occurring when you use Hourly cost in a custom field.  We currently don't have any plans to change this functionality, but I'd like to understand what you are doing that requires the custom field so that we can see if there is another way to help you.

Thanks,
Derek