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

Hi Alteryx,

 

Currently, there is no way users get notified that more metadata/reports have been loaded in Connect. Would it be possible to enable notifications for these newly loaded assets? The idea would be that if e.g. somebody is an owner of a project (or any folder), he/she would be notified when a new dashboard (or any other object) within that project/folder is loaded.

 

Thank you.

Jan

Hi Alteryx,

 

Currently, it is only possible to map first name, last name and email via SAML. Would it be possible to enable mapping of aliases? The idea is, that we cannot map first name and last name with the Full Name field because they are not unique. At the moment, we are pushing email into both Full Name and Email fields, because emails are unique for us. In addition to this, it would be convenient if the Alias(es) field could be mapped via SAML as well. In this way, not only emails but also real names would be automatically present in Connect.

 

Thank you.

Jan

 

Alias.png

Establish lineage/relationship between SAP HANA and Tableau (reports)

 

Issue

By default in Connect, we are unable to see data lineage between SAP HANA and Tableau. The standard Alteryx loaders (i.e. Tableau & SAP HANA) in version 2019.2 are unable to detect the HANA object link due to a misaligned naming convention (“::” vs “/”). This specifically occurs when Tableau dashboards are pointed to HANA synonyms (“::”) as opposed to the views (“/”).  

 

Background

In SAP Hana, there are two types of objects – views (which are present in relevant schemas, e.g. “_SYS_BIC”) and synonyms. The synonyms are created for each view by default and always appear to be in the schema “PUBLIC”, however, this is not actually an explicit schema. According to SAP, public synonyms are the official access interface for the system views.

 

When loading the objects from SAP HANA, the object names contain the package name as well as the object name (view etc.). These two are differentiated with a “/” when loaded from the “_SYS_BIC” schema (e.g. “GSTP_VALIDATION/CA_01_C_PDA_GRA_001”), however synonyms from the “PUBLIC” schema are loaded with a differentiator of “::” (e.g. “GSTP_VALIDATION::CA_01_C_PDA_GRA_001”). An example below, where first row is the view and the second row provides the related synonym:

 

clipboard_image_0.png

 

Thus, the lineage is not established when the SAP HANA objects from schemas are loaded (containing the “/”, and at the same time, the Tableau dashboards linked to the synonyms (“::”). This is because the object names are quite clearly different, and the loader doesn’t currently resolve the synonym to view translation (as per standard SAP HANA SQL parsing behaviour).

 

Loading problem analysis (using standard Alteryx loaders)

On SAP HANA side, when running the loader, user can (optionally) define schema name(s) they wish to load, however:

  1. When schema is set as “_SYS_BIC”, the loader only loads the views from this particular schema, with no synonyms.
  2. When schema is left as blank (i.e. no value entered), the loader loads everything, however in the “_SYS_BIC” schema, only synonyms are loaded and not the views.
  3. When schema is set as “PUBLIC”, the loader does not return anything - fails as there is no corresponding schema in SAP HANA (it is only virtual space, not an explicit schema)

The SAP HANA instance in question is very, very large and due to volume limitations, as well as the potential risk of performance degradation, it is not feasible to load everything.

When we’ve examined the H2 staging tables, we find that Connect has loaded (therefore is technically aware of) the synonyms from the “PUBLIC” schema but they are not ever loaded beyond the staging tables. This is obviously required if we wish to represent these relationships within Connect.

 

Idea/Fix:

  • SAP HANA loader – it seems there is a problem of loading synonyms from the “PUBLIC” schema and the loader should be adjusted in order to allow this.
  • Tableau loader – needs to be able to refer to synonyms defined in a SAP HANA data source, meaning whenever there is a “::” in object name and the schema name is blank (i.e. empty string representing the “PUBLIC” schema), then it should be defaulted to “PUBLIC”. This logic would ensure that a schema name is always present, even in cases where the schema name is retrieved as blank (which then would become “PUBLIC”).
  • In case the schema name is left blank for any reason, it should be populated as “PUBLIC”.
  • @DanH suggested to customize the Tableau loader as a temporary fix to replace the “::” with “/”, which is certainly possible but comes with a risk of incompatibility with future releases. Also the customers strong preference is to deliver a solution which only utilises standard loaders.

Hi,

 

In standard Alteryx Gallery loader (to Connect), would it be possible to implement an option of selecting the public workflows only and ignoring the ones stored in users' private studios?

 

Thanks

Michal

Hi Alteryx,

 

From 2019.2 version of Alteryx Connect, there is a new functionality of adding custom fields. However, right now, it is only possible to add plain text (text type) in there. 

 

Would it be possible to add there also URLs (hyperlinks)? We want to add new custom fields with hyperlinks pointing to other Connect pages.

 

Thank you

Michal

Hi Alteryx,

 

Would it be possible to implement a toggle for switching between business and technical names of metadata objects? We have both business people as well as technical IT people using Connect. While technical people are interested to see the original names of tables, views, schemas etc. from the sources, the business would like to see some names they can more relate too. 

 

We are using the alternate names, which works well, however we are missing a toggle, in which each user can define what he wants to see.

 

Thank you

Michal

Hi,

 

Would it be possible to implement an option to enable a banner with custom notification for users? This would be meant to inform users about scheduled maintenance windows, that they can experience slow performance (e.g. during metadata loading) or to inform them about any important information. 

 

Thanks

Michal

 

 

Hi,

 

Are you considering building a standard SAP BW loader for Alteryx Connect. I am concious there are some custom solutions available on the market (like DVW loader), but that is not standard and does not allow data lineage with other systems?

 

Thank you

Michal

Our users should primary look for certified objects. How ever the advanced search does not have the possibility to search for certified objects.

Certified objects should appear in the top of any search.

 

Today it has no effect on the search if a object is certified. Certified objects should be boosted in the search.

 

In the administration console, Connect configuration, search boost it should be possible to ad weight to certified objects

Hello, for me it would be great if the Connect did not compile all the scripts after saving a single config file as its compicating me work with config files.

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.

 

@SeanAdams @Revathi

We're working through an implementation of Connect - and it appears that every time Connect scans the Alteryx or Tableau environment, it does a full reload of all canvasses / workbooks.

 

However - we have several thousand tableau dashboards & alteryx canvasses - so this creates a significant delay on running the loaders, and we'd want to run these loaders every few hours so that Connect has up-to-date information (or at most 24 hours out of date).    Running a full export and scan is causing this load to take a very long time to run.

 

Can we change the default behaviour for all the loaders to use a delta-load rather than doing a full scan - i.e. only pull out assets that have changed since the last load?

 

 cc: @nganesha @Kosi

 

 

PowerBI Report Server is now offered as an on-prem solution. It would be great if there was a loader available to capture PowerBI reports not in Azure. If this could also capture SSRS reports which also reside on the PowerBI Report Server this would also be very beneficial.

Can't really tell if you've clicked the Like button already...

Seems like it goes from a dark grey to a light black. 

And the tooltip always shows "Like"

 

Please change the Liked object to blue; like when you hover over it. 

And also update the tooltip for Liked objects to say "Unlike".

When reading in multiple files/tabs with different field schema, there will be an error. It can be done by using macro. It would be great if there is a tool to read in all.

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.

Unavailability of Connect during H2 DB backup (using backup button in administration console as described in documentation - https://help.alteryx.com/connect/current/Administration/DBBackup.htm?tocpath=Administer%7C_____8) while even View is not possible, no matter the capacity of Java Virtual Maschine, can be limiting while large number of data is stored (so backup and following rerun takes a lot of time).

Connect provides users an ability to Certify/Decertify asset or mark the asset as "Do Not Use". 

 

Problem Statement: Canvases are published to production gallery and scheduled when there is a need for the output without any single person dependency. but when the canvas output is no longer required, users not always remove the canvases or schedules from production gallery. 

 

Idea: In order to ensure the Server is utilized only for those canvases that are in use, we would like to have a re certification process of assets at regular intervals. eg. Re certification of a canvas required every 6 months from the date of publication to gallery. 

 

With Connect - we can request users to certify or decertify or mark as Do not use but we will not be able to capture or track the re certification of an asset.  

 

Ask: Functionality in Connect to recertify assets at regular intervals or ability to decertify assets in bulk based on the publication date, so that we can request the users to certify again.  

 cc: @ @jalvarezv  @LizaNemchynova @

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.