community
cancel
Showing results for 
Search instead for 
Did you mean: 

alteryx connect Ideas

Share your Connect product ideas - we're listening!

1 Review

Our submission guidelines & status definitions before getting started

2 Search

The community for a solution or existing idea before posting

3 Vote

By clicking the like in the top left corner of an idea you support

4 Submit

A new idea to suggest a product enhancement or new feature


Suggest an idea

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
  • Person: +2.4
  • Term: +2.2
  • Report: +2
  • Report sheet: +1.8
  • Alteryx workflow: +1.5
  • Table: +1.4

 

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

 

Example:

    • 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)
      • Business line
      • Team (tree based)
      • Is this regulatory (Y/N)
      • Public / Private
      • Plain-text description
      • In this case – every asset needs 6 tags; with the taxonomy(valid values) controlled centrally

CC: @DavidM @Arianna_Fuller

Clicking the ‘Use in Workflow’ button in connect downloads a workflow file with the Table which I can open in Alteryx Designer.

 

When I open in Alteryx it asks for Userid/PW but there is no option for SSO (single sign on):

 

If I leave the username and password blank then the connection fails and I get an error.

 

In the case of SSO the connection string should be:

 

SSO:  odbc:Driver={HDBODBC};SERVERNODE=saphXXX.europe.company.com:30415;Trusted_connection=yes;

 

instead of this: 

 

UseridPW:  odbc:Driver={HDBODBC};SERVERNODE=saphXXX.europe.company.com:30415;UID=USERNAME;PWD=__EncPwd1__

 

Please note ALL of our users use SSO so current functionality is useless to us.

 

I have raised this as a bug with support but as usual they ask me to post here.

 

This option should also ask if the connection is In-DB connection also per this post:

https://community.alteryx.com/t5/Alteryx-Connect-Ideas/Have-In-Db-input-as-an-option-when-selecting-...

 

 

0 Likes

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. 

 

Currently - CustyID, CID(CUSTOMER_ID)

 

Request - CUSTOMER_ID(CustyID, CID)

 

Thanks!

0 Likes

It appears that the connect doesn't currently respect the custom URL for any workflows published to the gallery. ie if the url is https://awesomeness.com/datacloud when I select to open a workflow from connect it redirects to  https://awesomeness.com/gallery#!app/<specific app info>

 

That means whenever I select a workflow to open the link is broken.