New Deep-Linking Comment Settings in Dynamic View

egardner

I'm glad to see the second attempt to push the comment deep-linking in Dynamic View has gone more successfully than the first time! This is a feature I think will make a huge difference for a lot of people.

I know this feature is in its early stages, but I still feel there is much room for improvement going forward. As such, I'd like to ask questions about and suggest some future improvements.

We mainly use Dynamic View as a tool to manage permissions across stakeholders/users of many different access levels.

Question 1: are there plans to improve the deep linking interaction with the "filtered by current user" setting?

We often use multiple dynamic views from the same source, and 99% of the time, our users are working from a Dynamic View using the "assigned to current user" setting (selected at the Dynamic View level). This means, when leaving a comment for another user on one of their tasks, the comment recipient receives an error when clicking on the link in the comment notification/after redirected to the Dynamic View. I believe this is because the view is still filtering out anything not assigned to them and the deeplinking is not overriding the "assigned to current user" logic.

Please consider implementing the following:

• IF originating Dynamic View has "assigned to current user" setting active,
  • THEN deeplinking is allowed to temporarily override the current user setting.
  • AND when the comment recipient clicks out of the temporary deeplinking filter, the "assigned to current user" condition is re-applied to the view.

Question 2: are their plans to address when a user is mentioned in, and thus redirected to, a Dynamic View they are not shared to?

We often use separate Dynamic Views, each of which is curated to the department / user in question.

Please consider implementing one (or both) of the following:

• The ability to select one or more backup Dynamic Views (originating from the same source sheet or report) to redirect to should the comment recipient not have access to the originating Dynamic View,

AND/OR

• IF the comment recipient does not have access to the originating Dynamic View,
  • THEN, the user is redirected to:
    • the Dynamic View they've used most recently that stems from the same originating source (sheet or report).

Question 3: are there plans to fix the deep linking redirect logic for when a comment originates within a Dynamic View that lives within a collection?

Many of our Dynamic Views live within collections, and users do not have access to the Dynamic Views UNLESS accessed from within the collection itself.

Please consider implementing logic that combines the suggestions of my previous two questions. Not sure if this would be an additional opt-in (ex, a checkbox user can select to consider originating collection in deeplinking, located on the same tab where you select where you'd like it to redirect)

• IF the comment recipient:
  • IS shared to the originating collection,
  • THEN direct them to:
    • the originating Dynamic View WITHIN the originating collection,
• IF the comment recipient:
  • NOT shared to the originating collection,
  • AND IS shared to another collection that contains the originating Dynamic View,
  • THEN redirect them to:
    • the originating Dynamic View
    • from within the collection they ARE shared to that contains the originating Dynamic View.
• IF the comment recipient:
  • IS NOT shared to the originating collection ,
  • AND IS NOT shared to the originating Dynamic View
  • THEN redirect them to a Dynamic View that:
    • IS from the same originating source (sheet or report)
    • IS within a collection they ARE shared to.

Thanks,

Emma Gardner

IT Project Coordinator

Xanterra Travel Collection