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.
It would be great if it was possible to install/upgrade and configure Alteryx Connect using scripts. This would enable us to deploy Alteryx Connect using script deployment tools such as Urbancode Deploy. This functionality was recently requested by one of our customers, who has most of their application installations/upgrades automated this way.
currently, when running loaders from the Administration Console - Connections pane, there is no information about the status of the load. Would it be possible to include information such as success/fail message, run length, completion time or next scheduled run time?
This would much simplify monitoring of the scheduled loads and managing the schedule.
For assets identified in Connect - we are currently not able to identify an asset as being a UAT version of a Prod asset. Instead, these are listed as 2 completely different assets with no relationship between them.
This will be confusing for consuming users since they won't know which to use; and wasteful for the people capturing data about this asset since they will need to capture the info several times.
Request: Please create the ability to tag a given Alteryx / Tableau / Database server as "UAT / Dev / Prod", which will automatically tag the asset with this type. Then allow asset owners to relate the prod and Dev version together as the same thing, but in different states.
Thus, when you search you will find 1 asset with several different states rather than 3 assets.
Connect currently provides lineage for a datasource at the table level but we would like to be able to have this at a more granular level i.e. the column level so if a specific column changes in the table (e.g. data type change), we are notified of the change and able to identify quickly assets that will be affected.
In a large environment- especially an analytical environment - copies of data will often appear in multiple places. an example of this is where a copy of a shared dimension or a shared piece of reference data is copied in multiple different data marts.
In order to manage this - we need to be able to mark these as copies of each other so that we can point folk to the golden-source; and so that we don't need to document this asset multiple different times.
- Client List appears in the data lake; on the Sales data mart; on the Finance data mart; etc
- We would want to group all 3 of these together; and mark the Data Lake version as the master; and all the others as copies.
When I navigate to any Sales assets - it tells me that the Client List is a data asset which is used
When i click on this - it tells me that the sales version is a copy - and directs me to the one on the data lake
NOTE: There are circumstances where a copy may be deliberately filtered or incomplete (for example - regional subsets of clients) - in this case the relationship needs to be "Partial Copy" not "Copy"
Is there a way to make asset icons customizable? I am conscious of an option to upload an icon through the attachment, but this only applies to a specific page/asset.
What I have in mind is to customize the icon for individual asset types. For example, reports (workbooks) and report worksheets have the same icon, which is in our case for many users confusing. It would be great if we could customize the icons for example in the Asset Configuration tab of the Administration Console.
If files/tables with the same name are registered, it is impossible to identify on the data sources list. Our client would like a feature that to classify data sources by folder as like "All Schemas, Tables and Views".
The addition of the On-Premise PowerBI loader is very beneficial. The current loader grabs PBI workspaces, workbooks, dashboards, and database connections all important to the PBIX files. It would also be an huge benefit if Connect could capture Paginated Reports (RDL file extension) information.
We are implementing 19.2 of Connect after trialling 19.1. Our users are missing seeing the Search option and when I look back at the old version it seems much more obvious than from the 19.2 version. It would be good to have the search much more obvious from a UI perspective.