UI Builder - Event Open /list Page

[Ben Draeger]

Hi all, 

I'm looking to setup an event for a single score visualisation, but I'm running into issues getting it to open a specific list on the /list page within workspace rather than the /simplelist. 

The /simplelist page destination works when the visualisation is clicked:

But if I instead want it to open a specific pre-configured list on the /list page, it fails with an undefined property error in the browser:

I've confirmed the sys_id for listid is valid on the sys_ux_list table and the configId is the correct sys_id linked to it. Also tried it with just the listId and also with '-1' for tinyId. 

What am I missing for setting the destination for list pages? 

[l457]

Is it a custom workspace and/or a custom list page? Does it navigate to the correct route and the error happens on the list page? Have you changed anything if its some oob page?

On sow you'd only need listid, not sure what configid could be used for. It does not seem to do anything if you use a list config sysid which makes sense as its bound to app props instead on the oob list page.tinyid is just a hashed set of key value pairs [sys_tiny_url] so that should be left empty.

[Tanushree Maiti]

Refer this links if helps.

KB2008867 Click-through not working in for Single Score Data Visualisations 

Simple list option missing in UiB dynamic Event mapping 

UI Builder - How to make Data Visualization single score open table 

Issue with Simple List page UI Builder - list view parameter 

[Ben Draeger · Accepted solution]

Thanks @Tanushree Maiti this article did help Simple list option missing in UiB dynamic Event mapping.

I found the issue when trying to set the event via script instead of form. UI builder doesn't clear the payload when changing between SimpleList and List pages in the event configuration.

For example:

SimpleList config

Change to List page, nothing in the fields

Change to Script instead of Form and the payload still exists and causing issues with the List page: 

Deleting and re-creating the event resolved the issue.