I have a whole bunch of SQL data sources. I am going to be changing the credentials at some point (both the user name and password) and then will change the password from time to time. It would be really helpful if there were a way I could just set the two values once, such as in company properties, and have those properties used by the data source. That way, instead of having to go through each data source, update the credentials, get data, accept the data, etc... I could just change it once in company properties.
7 comments
-
Excellent timing - we're actually launching a new feature called Connection Profiles at the end of this month to do exactly that. We're introducing it to PowerMetrics first but our goal is to ultimately support this with Klips as well. Stay tuned for the September product update for more details. I'd love to get your feedback on it.
-
Cool. Won't help us until it is available for Klips... we only have one PowerMetric because we have variable-based security requirements we can't solve with PowerMetrics.
-
I understand - it's a significant enough change that we want to start small (and think big). Ultimately, this may be a Klips feature in the near future but we have to handle data source migrations, etc. which makes it more complex than for new customers to adopt. We also have dynamic filters on our roadmap (as a replacement strategy for variables and dynamic data sources with similar functionality) but that will take a while to finish designing and implementing. If you have any more details on your security requirements, I'd love to better understand your needs.
-
I don't really understand why it would only apply to one or the other. I would think that a data source is a data source, regardless of whether it's being used for a PM or Klip. Certainly, it looks that way in the UI.
My client operates KF as an OEM, with all their customer data in a single database. The primary filter we apply is based on the user id (email) of the current user. In most cases, the data sources have a small enough amount of data that we can do this just fine with a hidden data filter on the Klip, but a couple of them have too much data for that, so we use dynamic data sources that plug the user's email address into the query. This works well for the Klips, but does not yet work with PMs, as you know.
-
For the existing Klipfolio data sources, you are correct, they can be used by both Klips and PowerMetrics. We will continue to support these and they will continue to work.
However, for the past 9 months, we've been investing in a next-gen, higher performance, data layer which we're launching at the end of the month. The first piece of this is connection profiles. We are releasing it to new PowerMetrics customers first (so we can make sure it's a great experience for a smaller group before we roll it out to everyone) but we've designed the feature so existing data sources can potentially be migrated over. However, if/when we do this has not been finalized.As for your scenario with the hidden data filter and dynamic data sources, this is exactly what we'd like to address with dynamic data filters - a completely different implementation based on our new data layer - but the result and the behaviour will be the same as you described. Existing data sources can also potentially be migrated over to use this feature but the timing of if/when we do this has also not been finalized.
We will definitely keep you posted on our plans via product updates and other means. I appreciate you sharing more details around your use case. -
Did this feature ever get release to PowerMetrics or regular Klip data sources? Every time we roll database credentials we have to update 100s of data sources with the exact same Username, Password, and DB address.
We're a long time customer of Klipfolio, but it's causing us to reconsider if you all are the right solution for us, as tools like Holistics.io have this shared data-source (specifically DB connections) and all the same visualization tool as Klipfolio.
-Erik, VP Product @ ReviewTrackers
-
We've waited for 3 years for this feature for DB connection sharing. We're now moving off of Klipfolio and onto Grow.com and Holistics.io.
Surprising such an easy and powerful feature was never built by the Klipfolio team.