We are in 7.9. Is there a way that I can provide a direct link to one of the Re

@chasityd True, the above pointer helps you only when you are on a SAIL interface, as the a!recordLink() results in a SAIL component.

One of the ways to obtain the link is:
Step - 1: Use urlforrecord() function and obtain the url.
Step - 2(optional): If you want to direct the user to the 'Summary' dashboard of the record by default, the value obtained in Step - 1 should be sufficient. If you want to redirect the user to a dashboard other than 'Summary', use the Text functions and modify the url(obtained in Step - 1) in such a way that the identifier of the desired dashboard view is used in the link rather than the identifier of 'Summary' dashboard view.

For instance, link to 'Summary' dashboard view might look like this: https://xyz.com/suite/tempo/records/type/xyz/view/summary and this will be obtained by default when you perform Step - 1. Here 'summary' in the url represents an unique identifier of 'Summary' dashboard.

For instance, link to a dashboard view other than 'Summary' might look like this: https://xyz.com/suite/tempo/records/type/xyz/view/_YsHLXA where _YsHLXA(differs from view to view) represents an unique identifier created for an each dashboard view by Appian.

The above approach is being suggested as per the observations in my experience, so let's see if any other Appian practitioners comes up with a better approach(as well as flaws in the above).

Hope that gives you some leads!!

@chasityd True, the above pointer helps you only when you are on a SAIL interface, as the a!recordLink() results in a SAIL component.

One of the ways to obtain the link is:
Step - 1: Use urlforrecord() function and obtain the url.
Step - 2(optional): If you want to direct the user to the 'Summary' dashboard of the record by default, the value obtained in Step - 1 should be sufficient. If you want to redirect the user to a dashboard other than 'Summary', use the Text functions and modify the url(obtained in Step - 1) in such a way that the identifier of the desired dashboard view is used in the link rather than the identifier of 'Summary' dashboard view.

For instance, link to 'Summary' dashboard view might look like this: https://xyz.com/suite/tempo/records/type/xyz/view/summary and this will be obtained by default when you perform Step - 1. Here 'summary' in the url represents an unique identifier of 'Summary' dashboard.

For instance, link to a dashboard view other than 'Summary' might look like this: https://xyz.com/suite/tempo/records/type/xyz/view/_YsHLXA where _YsHLXA(differs from view to view) represents an unique identifier created for an each dashboard view by Appian.

The above approach is being suggested as per the observations in my experience, so let's see if any other Appian practitioners comes up with a better approach(as well as flaws in the above).

Hope that gives you some leads!!