Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!
The Product Idea boards have gotten an update to better integrate them within our Product team's idea cycle! However this update does have a few unique behaviors, if you have any questions about them check out our FAQ.

Alteryx Connect Ideas

Share your Connect product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

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.

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.

 

Example:

- 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.

 

User experience:

  • 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"

 

 

CC: @DavidM @Arianna_Fuller

Hi Alteryx team,

 

Would it be possible to implement a legend in the nexus diagram with what each asset icon means? It could be in the bottom right corner of the page as a section so that it is easy to navigate and understand for business users what objects they're looking at. This is especially useful for more complex relationships diagrams with multiple types of data assets.

 

Thank you

Michal

Hi Alteryx team,

 

Would it be possible to implement an overview table with a complete history of metadata loads? I can imagine there could be a table in the administration console (in Jobs) where you could see the history and number of runs for each source system so that it can be referred to at any time when you need to know the frequency and past runs?

 

Thank you

Michal

Hi Alteryx,

 

Would it be possible to allow some basic customization of the login page? In our use case, we have the access into Connect restricted for the users and when they navigate to the login page and find out they don’t have access, we want to inform them they need to contact some internal Connect support to grant them access. So generally, it may only be like a one line with a custom text.


Thank you.


Jan

Hi Alteryx team,

 

apart from the current known issue of format of email notifications (which in some cases shows a code instead of a proper notification), can you work further to improve the visual of the email notifications?

 

Currently, the notifications do not contain any indication (information) that it is coming from Alteryx Connect so very frequently, it is even captured by the spam filters or users have no idea what they are receiving.

 

The expectation would be to include perhaps the Alteryx Connect logo, perhaps name of the instance or some other details, possibly even customizable by the administrator (to some extent only, obviously).

 

Thank you

Michal

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

Hello Alteryx team,

 

would it be possible to include a switch between All Projects and Top-Level Projects views when looking on a Tableau site in Alteryx Connect?

 

JanLaznicka_0-1585737355729.png

 

 

For many users, the navigation in Tableau is through the 'Explore' tab and then Top-Level Projects view rather than All Projects. This reveals the real tree structure of the specific Tableau site. In Alteryx Connect, currently, there are always all projects listed when looking at a specific site, so also sub-projects.

 

The hierarchical structure is already brought in, when opening a workbook, the route includes both projects and sub-projects. The idea is that there would be a switch between the 2 views when looking at a site.

 

Thank you very much for considering this idea.

 

Regards,

Jan Laznicka

 

 

Hi Alteryx,


Currently, when a user edits an asset, all the contributors (those who have made the changes to this asset in the past hence listed as contributors of that asset) are notified by email. As a result, these contributors have their mailboxes often flooded with notifications.


In our use case, we rather want to apply pull principle (users can subscribe if they want to be notified) instead of push principle (users are notified on every single change).


Would it be possible to implement a maybe a toggle for turning off the notifications for contributors? Thus, only owners and users who subscribed would be notified when an asset is changed.


Thank you.


Jan

Hi Alteryx,

 

In Connect, when navigating through different data sources, a different number of objects are shown in the default view. For example, for Hadoop we only see initial 5 tables in a schema (with an option to see around 35 more), for other data sources like SQL Server, it will show initial 50 or so with couple of hundreds more. The same applies to the glossary or reports – for each data asset type it differs.


In order to increase user experience, would it be possible to unify the number of objects displayed on a page in a default setting?


Thank you.


Jan

Hi Alteryx team,

 

It would be great if it was possible to load SAP HANA systems using ODBC DSN instead of the normal host name.

 

From our experience, there is often more than 1 node present for SAP HANA systems and when entering the master node into the loader interface, we can't easily switch to a failover node when an unexpected event happens. Sometimes, it is not only the matter of nodes but for example a migration of an instance to cloud might result in a different host name. As a consequence, the loadcode is different and it is not possible to migrate the previous enrichment to the asset pages created under the new loadcode.

 

A solution for this would be the possibility of loading SAP HANA systems using the ODBC DSNs (this is already possible for example for Hive and it would be great if it was available for all applicable systems).

 

Thank you very much for considering this idea.


Regards,

Jan Laznicka

Hi Alteryx team,

 

In Connect, users are able to open workflows, open reports (like Tableau) or use data source in a workflow using the blue button on an asset page. With the new functionality of cataloguing APIs, would it be possible to implement this button for API endpoints as well, meaning users would be able to trigger the API directly from Connect?

 

2020-03-04 13_25_00-Get posts.png

 

Thank you very much.

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

Connect offers functionality for users to chat about data & analytical assets.

However - in order to meet regulatory obligations in a regulated Financial Services company - this communication needs to be surveiled by compliance.

 

Please could  you provide an API for this data to be monitored by compliance teams in near-real-time?

 

cc: @dataMack

 @DavidM @Arianna_Fuller

Hi Alteryx,

 

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.


Thank you.


Jan

Hi Alteryx team,

 

In Connect, there is a Table Details section of each page within Data sources, however it only shows the size for Files. It is not relevant for databases. Currently, database tables/views always show the size 0.0 bytes, which indicates the table is empty but it is not true.

 

Since it is not relevant, it should not be visible for DB objects at all. Instead, it would make sense to implement some basic statistics of the object like number of rows, number of columns etc.

 

2019-11-06 22_50_55-growth_published.advantaged_assets.png

 

Thank you,

Michal

Hi Alteryx team,

 

Would it be possible to implement custom URL in the HDFS loader when using Knox Gateway? This could be implemented in the same way as in the normal Input Data tool.

 

When connecting to HDFS using the Input Data tool, the URL is automatically generated, however, it is possible to change it. Sometimes this is necessary as the 'sandbox' part of the URL is for some companies not applicable, they have for example their company names instead of it:

 

JanLaznicka_0-1585161087518.png  JanLaznicka_1-1585161125093.png

 

 

However, in the Alteryx Connect HDFS loader, this is not possible as there is no such field in the interface:

 

JanLaznicka_2-1585160401795.png

The 'sandbox' part of the URL is then automatically brought through 2 formula tools:

 

JanLaznicka_3-1585160565194.png  JanLaznicka_4-1585160575989.pngJanLaznicka_5-1585160621052.png

 

This makes it impossible to load the HDFS metadata into Connect using the out-of-the-box Alteryx loader. Implementing a field into the interface like in the standard input data tool would solve this problem.

 

Thank you very much for considering this idea.

 

Regards,

Jan Laznicka

 

 

 

 

 

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 team,

 

Would it be possible to include the "Status" column in all applicable asset lists? Currently, when looking at Tables in SAP HANA, there is a "Status" column containing the certification states. But for example for Views, though certifiable, there is no "Status" column in the list. Applying the same column structure could simplify navigation in the system and also help with operations such as bulk certification, where a user needs to select only assets in the same certification state.

 

1.png2.png

 

Thank you.

 

Jan

 

Hi Alteryx team,

 

Currently, there is the Open button functionality for opening the Tableau projects, workbooks and worksheets. While I understand you may be relying on Tableau API, would it be possible to implement the Open button for Tableau data sources is well?

 

The idea is that when you click Open in Connect, you will be taken into the Tableau data source or possibly into a new workbook which is connected to this Tableau data source.

 

Thank you,

Jan