Selection in screens with multi-data-models

c.rudolph

We have a requirement where a single screen needs to display data views that are based on different data models. The problem is that users have to apply the same selection multiple times (for example: select the year → Data Model 1, and then again select the year → Data Model 2).

Is there any workaround for this?

One idea we had was to create a predefined database procedure that would be called through a capsule procedure (e.g., “Year 2023” triggers queries for DB1 and DB2 through a label). But this seems quite excessive in regards to the requirement.

Is the only real alternative to handle this already at the DWH development stage so that the values are prepared correctly in advance?

We're using Board 12.6.

Thank you in advance!

Carolin Rudolph

Robert Barkaway

Hi Carolin, the only real way to achieve this is as you say to create a procedure that passes the selection across to the second database, either by extracting a layout that the second database can ingest and use to determine the required selection or by using an API call. Unfortunately there isn't really a more direct way to pass a selection between two different databases at present I'm afraid.