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 had an idea, when you have an yxdb file, you have all the metadata including the field descriptions column from previous formulas or selects, it would be so usefull to have that in connect so that you can easily write a dictionnary from alteryx designer.
Connect applies a standard set of weightings to different categories of information (people, terms etc.) when returning search results. When combined with likes/dislikes, these determine the order in which results are returned - details below:
Alteryx Connect uses the following scoring parameters for the Lucene engine:
Likes and Dislikes, using the following formula: (Number of Likes) / (Number of Likes + Number of Dislikes).
Certified assets: +1.2
Report sheet: +1.8
Alteryx workflow: +1.5
It would be useful to have control over this weighting, e.g. when you have large numbers of Person records being returned before Terms; but advice from Customer Support has been that these are not currently customisable. I'd like to request that this ability be considered for inclusion in a future release of Connect.
In order for us to make sense of Connect assets in an environment with hundreds of users; thousands of canvasses and databases etc - we need to strongly categorise and describe every asset using mandatory tags.
Every asset needs to have mandatory tags
- The admin team set up the list of tags which are required for different types of assets
- For example - every Alteryx Canvas may need Product; Process; Team - every DB table may need Product and Tech Team
Admin team need to be able to define these tags and the acceptable values (which can be a tree)
When searching for assets - these meta-tags need to be available as filters
Asset is identified by the scanners and brought into Connect
Owner is then required to describe their asset using the mandatory tags set up by the admin team
Product (this is a tree that would be controlled centrally – admin can add or update this list; users have to select 1 or more products that this canvas relates to)
Team (tree based)
Is this regulatory (Y/N)
Public / Private
In this case – every asset needs 6 tags; with the taxonomy(valid values) controlled centrally
Hello...We've found that when we assign an alternative name to an asset, the alternative name becomes the first name listed, and the main name becomes listed within parenthesis. Could this be reversed? As it's always best to have the main name of the asset listed first, then any alternative names/alias to be listed within the parenthesis. It creates visual order having it displayed this way. We've ended up not utilizing the alternative name functionality to avoid any confusion for our users.