Support link operation in other columns than the action menu

Hello

The Link feature is currently supported in the action menu:
https://docs.nocobase.com/handbook/ui/actions/types/link

Is there a possibility to also support it in columns, in the future?
In addition to the current popup link option.

For example:
If you use the first column of a table as a title. You could open a new page this way, instead of the action menu.

Thanks!

Hi,

Thanks for your suggestion.

Currently, the Link feature is not supported directly within table columns.

However, as a workaround, you can use a popup menu with the open mode set to “Page”. This will behave similarly to opening a new page when the action is triggered.

Hi

Thank you for your reply and suggestion.

Yes, this is how it is currently set up. However I noticed it can slow down the app quite a bit, if you use too many popup screens.
Popup > popup > popup with on each filtered results.

But it works, indeed!

My workaround is to use one of the existing options (page, dialog, drawer), usually drawer, and then I have a variable for the say product by Id page and I append the $env variable for that page and the record id inside markdown.

This is a huge time waster an not good UX. A plugin to allow developers to specify a centralized “collection list” and “collection by id” page for each collection would be ideal. Just filter pages where the current record is that collection type and allow a selection.

EDIT: I want to quickly praise the nocobase team for their work. I’m seeing if I can make my own plugin to do this. I just have to append to the url the popup and it will go there!

UPDATE 2: Ah, popups are tied to the form field, makes sense, but if you delete that form field, then the popup also goes I believe. Hmmm, this might not be such a great idea or very difficult. I’m seeing a need for a popup that is not tied to the field, but the associated resource collection… it’s so close to working, I just don’t know how to not end up in a situation where everything links to the popuup of one field and then that field is deleted…

Hi, we’ve already taken this issue into consideration, and it has been addressed in version 2.0.