Now that it's live, don't forget to accept your certification badge on Credly today! Learn more here.
We are currently experiencing an issue with Email verification at this time and working towards a solution. Should you encounter this issue, please click on the "Send Verification Button" a second time and the request should go through. If the issue still persists for you, please email support@alteryx.com for assistance.

Alteryx Connect Discussions

Find answers, ask questions, and share expertise about Alteryx Connect.
SOLVED

Exporting metadata data

No-Sass
8 - Asteroid

We've loaded our Tableau server and Gallery workflow metadata into Connect. Instead of arbitrarily loading all of our SQL Servers and the 1000's of databases, we'd like to be specific in our approach and only load those databases which appear in our Workflows & Reports. Is there a way to extract/report/access this metadata info?

2 REPLIES 2
joshuaburkhow
15 - Aurora
15 - Aurora

Looks like you haven't gotten a response yet on this. Did you get it figured out? You do have the ability to restrict what is loaded into connect. 

Joshua Burkhow - Alteryx Ace | Global Alteryx Architect @PwC | Blogger @ AlterTricks
No-Sass
8 - Asteroid

Actually we did!!

 

We created a workflow that scrapes all of our workflows stored in our shared folders. The workflow parsed out all of the metadata for each workflow and we were able to isolate all of the Data Input connections down to the table. We then took that data and summarized it to get an idea of: A)what sources were being used and B) what sources were being used MOST. We then took that data and used it to target the SQL servers that were being used and loaded only those into Connect. 

 

For the workflows that were already loaded into Connect via the gallery, we took an export of the gallery data from the Admin page and did the same parsing breakdown of the data. It was a slightly different format than the .yxmd files but basically the same process. 

 

Really helped narrow down what data sources were necessary to load via the SQL loader into Connect.