I would try getting rid of: namekey, querysort, and linkedname. If you get it working you can add them back in one at at time and see if that affects anything.
I also think your aggregator.valuefield needs to be aggregator.valueexpression, with the same formula as your valueexpression. But I would a...
If anyone stumbles across this later, I've receive a reply from support.
"After consulting with our resources, it appears that the only current solution to address the issue is by adding a second rate to the billing rate."
However, current documentation doesn't specify that this is needed for non-US...
Description - Programs need to show the currency of the projects within that program
Why is this feature important to you - We have multiple programs where all the projects within that program are in GBP, but when viewing aggregated data rolled up at the program level, it defaults to USD. This is t...
Curious how many of you have non-USD projects AND use billing rates...? If you do, you might want to look into an issue that we've found. I've submitted a ticket, but still waiting on a response.
We discovered that on non-USD projects, the billing rate associated with a job role multiplied by the pl...
Are you unable to edit on all projects where these fields appear? Or just certain projects?
If all projects, is it possible that someone has edited the field sharing...? Maybe system-wide access to that field has been removed and only shared with certain users?
We did a step challenge one year - about this time of year! Anyone who wanted to participate had a weekly task with a custom form attached where they logged their weekly steps and closed their task. Then we had a chart report to track who was in the lead.