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.
Would you consider creating a metadata loader for SharePoint? A lot of companies that we are working with have a lot of data stored in SharePoint and they would like to catalog their metadata.
I am aware that it is possible to use the Files Loader when the SharePoint drive is mapped as a mapped drive in Windows Explorer, but the mapping and subsequent scheduling is very problematic, also because of security policies in large enterprises.
Having a SharePoint dedicated loader would be a great benefit.
currently, when running loaders from the Administration Console - Connections pane, there is no information about the status of the load. Would it be possible to include information such as success/fail message, run length, completion time or next scheduled run time?
This would much simplify monitoring of the scheduled loads and managing the schedule.
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?
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.
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.