Solved: Correct localization - Page 2

thematgallery · 07-14-2023 02:30 AM

In terms of localization, there´s plenty to be missing, but I´ll be specific on this one. The "Go to details" system button that cannot be neither modified or translated. I have a card view where I want to implement this button, and it should be available for localization just as any other system words.

I know it is possible to skip using this by creating a button with LINKTOFILTEREDVIEW directly aiming at the detail view and filtering by ID, but with many different card views this could get unnecessarily annoying.

Thanks!

WillowMobileSys

@thematgallery wrote:

know it is possible to skip using this by creating a button with LINKTOFILTEREDVIEW directly aiming at the detail view and filtering by ID, but with many different card views this could get unnecessarily annoying.

What I noted above is the best approach from useability BUT if you insisted on having a button on the Card, then the correct alternative to using the "Go To Details" action is to create your own action button. The "Go to Details" button is just a LINKTOROW() function and can be implemented in your own "go to another view" action like this:

LINKTOROW([_THISROW], "View_Detail")

Creating this action on the data Table the Card view uses will add the action to the list you can choode to be placed on the Card view - allowing you to give it any name you wish.

NOTE: "View_Detail" is the system provided view for that data table. You can find it listed in the System generated vies section.

View solution in original post