Spotfire Ideas Portal
In extending Spotfire to replace legacy reporting, or in cases where SQL queries were developed and known to be good, the manual creation of column attributes, filters andjoins is tedious and pasting in a SQL on an information link can speed development. This still though requires DB columns to be mapped from the DB. I would expect that an infolink would allow the Data source connection to be defined and then allow the SQL to be pasted in and the result set would be imported/wrangled like any other. Its different though from the in DB query process.
It is understood that the current process has known issues in the case that the DB changes
Thanks Christian. I certainly hope not as there are many features and attributes and filters and parameterizations and code blocks used by information links that would be broken.
Also found that data connectors do not support or have the data source JDBC connection parameter definitions and work off local ODBC definitions and if trying to access huge DB definitions like Oracle ERP can take 10 minutes to just read the DB Schema but is good if using the data source JDBC definitions. TINCO support did not have a resolution for the data source performance.
Data Connectors already support this feature (pasting adhoc SQL queries and creating the data connection for you). While Tibco doesn't say much I have a feeling that Information Links are no longer strategic for the product and all their investment is going into Data Connectors. So moving to Data Connectors might be a good idea overall.