New Functionality Causing Reporting Issues For Users

[Ryan_McGee]

The new feature that more overtly shows "No Access" has had an interesting result: For reporting, several users have a column that shows them the template name of the project in question. However, for Workers, who inherently have no template access, this means this column is always now saying "No Access".

Has anyone else seen this and/or developed a workaround?

[TerryHy]

I also have Reports and Project Views where there is a column to show Template Name, but now, those individuals are now seeing "No Access" in that column. So, I am having the issue as well. Not sure what the fix/workaround may be at this point. 

[KatherineLa]

In my instance, I replace the valuefield=<field> portion of the field defintion with valueexpression={field} instead. By making the field display as a calculated field instead, the text is visible to all users and not just those with access to the underlying object.

It does have the side effect of making that field no longer clickable for navigation, but at least for Portfolios/Templates, that was a reasonable trade-off in my instance for most scenarios. The report typically needed to display what Template was used, but there wasn't an expectation that the user would routinely be using that link to navigate TO the templates.

[Ryan_McGee]

Hi Katherine: Thanks for the reply. Sadly I am having a hard time figuring out exactly how to implement in the textmode I have, which I have shared below. Any help would be appreciated! I'll keep hacking away on my side as well.

displayname=Template Name
linkedname=project
namekey=view.relatedcolumn
namekeyargkey.0=project
namekeyargkey.1=template:name
querysort=project:template:name
textmode=true
valuefield=project:template:name
valueformat=HTML

[KatherineLa · Accepted solution]

That would read as valueexpression={project}.{template}.{name} 

For valueexpression formulas, you need a period between the fields rather than a semi-colon. That's usually what trips people up when they're learning. 

Here's a good overview: https://experienceleague.adobe.com/en/docs/workfront/using/reporting/reports/text-mode/text-mode-syn...

[Ryan_McGee]

Much appreciated, and so speedy!

[MichaelPe10]

The 'No Access' is also appearing on the project details for Portfolios and Programs as well as the template. This change is not good at all!

[KellieGardner]

I have reports that run with "admin rights" so that users can see all data in the system that need to see and those values are all replaced with No Access. Unfortunately, I have zero time available to update every report that was impacted and then have to consider the use case where someone looking at the report does have access and wants to be able to click through to the object. 

Agreed, this is an awful change.