Spotfire Ideas Portal
When using external data, detail visualisations need a primary key in the datasource for markings to be applied.
In case of views or custom queries, the resultset has no primary key defined on the database level.
Would be great when we could select columns to be treated as primary key column independent of database status.
This would benefit for everbody working with external data and having the need to drill down to individual rows.
This is treated as a feature request but it seems like a bug. Nothing in the help files indicated that setting primary keys would not work with the Impala data connector. The results has been that we put in efforts to get this far but it fails.
Some additional information.
The question had already been raised in support ticket 01449120 and it turned out that the feature requested is already implemented, but only available for certain datasource drivers.
For oracle it seems to work, for other datasources like impala, db2 it does not work.
See https://docs.tibco.com/pub/sfire-analyst/7.5.1/doc/html/WebHelp/connect/connect_details_on_views_in_connection_d.htm for example of how to set primary key.
So idea is to make this exact functionality available for impala + db2 (and potentially others) datasources.