This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.

We are seeing a strange behaviour where the scanner / harvester registers the data sources; tables; databases across our Alteryx Canvasses (you can see this when you look at the detail of a canvas) - however it doesn't create these entries in the "DataSets" section of Connect.

When we scan the workflow - if you look at the workflow, you can see that the workflow knows the databases and tables that it's hitting.

However these are not added to the DataSets section of connect until you then scan the database itself.

This seems to be very inefficient because the Tableau workbook and the Alteryx Canvas both know their databases - and you can see this on the asset when you have completed a scan of just the workbook / canvas - but we can't seem to get these to add automatically to the datasets section.

when you harvest (extract metadata) from gallery you can get list of workflows and on each workflow you can get details such as used data sources, you have many options in workflow how to address database table (by DNS alias, by full database name, with or without schema name etc.). So if we were creating "DataSets" inside the Datasource folder it would potentinally end up in many duplicities and inconsistencies in the naming convetions. Also the "exploration" feature will only shows used objects in the workflows, not full object list from that datasource. So in our architecture we are just keeping info that such workflow is using the table (with some other identification such as technology type, server name ...) and we are trying to much with algorithm to already existing object (harvested from the technology specific harvester e.g. oracle loader).