5 Reasons Why I Don’t Think Write-Back To QVD Is A Good Idea
Disclaimer: My Personal Opinion :)
These times are very interesting when it comes to generating and utilizing data. Nowadays we are pushing the boundaries of data analytics from read-only into actionable – thanks to write-back, notifications, and many more add-ons and features.
Let’s talk about the write-back since it’s quite special and doesn’t have a long history in Qlik Sense environment. Write-back is about entering and storing data by users directly from the app somewhere. It’s a completely new stream. Without the write-back users are only consumers of the data in their apps. With it, we are changing the paradigm and switch from a one-way to a two-way road. And watching the amount of data, I would say it’s a highway in both directions now :).
Where is “somewhere”?
Write-back is about entering and storing data by users directly from the app somewhere. I used the word “somewhere” on purpose. For end-user, data storage should be irrelevant. If you use a good extension or add-on the write-back is a seamless process for your users and it doesn’t matter where the data is technically stored.
When you start discussions with developers and architects, data storage is a very important topic. There are three main categories when it comes to a data storage type for write-back:
Why QVD?
As I mentioned, the topic of data storage is open in discussions with developers and architects mostly. Those are people who work with Qlik or at least know the technology from their own environment. QVD is a native format developed by Qlik for storing the data. So, it’s natural, they’re asking about the possibility to write-back data into QVDs.
Why NOT QVD?
Yes, QVD is a file format developed and optimized by Qlik in many years… BUT it’s a file format developed and optimized for:
- storing data from Qlik during the reload of the app
- loading data into Qlik during the reload of the app
So, here is the question – do you think it would be a good choice to use it for a process that’s not realized during the reload of the Qlik app? I have a clear opinion. No. And here are my reasons:
When I have a discussion about data storages supported by Inphinity Forms, my answer to the QVD question is the following: “We can do it. If it’s very important to you, just let us know. But there are some reasons why I don’t think it’s a good idea…” And the discussion starts 😉.
It’s absolutely natural to ask whether QVD is a supported format for the write-back. However, before choosing it just think about the points above.
Interested in write-back?
If you are interested in Inphinity Forms write-back extension, you can:
- Contact us via the contact form or pick the date/time that suits you for a call with Radomir.
- Download a free trial and try Inphinity Forms by yourself
- Get inspired on Inphinity Universe demo portal
WRITTEN BY
- Webinar: Pronto Network Cooperative | 28TH MARCH | 3:00 PM CET - 26. March 2024
- Webinar: 2023 Recap: Inphinity Suite New Features & Functionality
29th February | 3:00 PM CET - 20. February 2024 - Webinar: Streamline your Planning, Budgeting & Forecasting with Qlik & Inphinity
6th December | 4:00 PM CET - 20. November 2023