topic Best practices document in Integration, Extension & APIs

Best practices document

Anonymous — Sun, 22 Apr 2018 16:55:25 GMT

Hi team,

Any best practices document for qlik sense..Please share..expected in details

thanks

Re: Best practices document

Anonymous — Mon, 30 Apr 2018 04:10:55 GMT

any suggestions..

Re: Best practices document

Anonymous — Mon, 30 Apr 2018 07:13:41 GMT

suggestion please

Re: Best practices document

Anonymous — Mon, 30 Apr 2018 16:09:08 GMT

suggestion please

Re: Best practices document

Anonymous — Mon, 30 Apr 2018 16:18:36 GMT

Best Practices --means in terms of data modeling, scripting, profiling

Re: Best practices document

adityaakshaya — Mon, 30 Apr 2018 18:45:15 GMT

Hi Rupesh,

Please find attached documents for your reference. Hope this helps you to understand the best practices.

Let me know for any further clarification.

Regards,

Akshaya

PS - If you find this as helpful, mark response as helpful or answered.

Re: Best practices document

Anonymous — Tue, 01 May 2018 14:11:36 GMT

i have added suggestions from this .any other suggestions, please

Re: Best practices document

adityaakshaya — Tue, 01 May 2018 14:57:01 GMT

Hi Rupesh,

Below is the Goverance Material shared by Qlik.

You can use this for your reference.

Regards,

Akshaya

Re: Best practices document

Anonymous — Tue, 01 May 2018 15:11:56 GMT

any ppt based diagram for flow from dev to prod like app dev work scenarios#3

Re: Best practices document

qlikdeveloper9999 — Wed, 22 Apr 2020 15:04:46 GMT

Hi,

As in many companies, the company I am working with is considering implementing a data warehouse from scratch. The visualization tool of choice is QlikSense, TalendD and a few mySQL enterprise DBs for data warehousing.

As we all know data warehousing is a complex subject. I have reviewed the documents attached to this post.

I am wondering in terms of best practices, should ETL process be implemented within Qlik using scripting and therefore having a bloated visualisation tool with complex data models and data manipulation.

Alternatively, the visualisation tool is kept as lean as possible and all the data is pre-processed in advance, keeping QlikSense scripting and data modeling at a minimum. One school of thought is that the engine is optimised to handle large amounts of records and so this later becomes really complex to maintain and bloated with business logic.

An feedback from experts in this field is much appreciated.

Re: Best practices document

lorenzoconforti — Wed, 22 Apr 2020 15:18:44 GMT

An approach I usually take is to have dashboards to handle specifically the ETL part; you load data from your various sources, you manipulate them in Qlik (scripting is pretty good) and then you save the resulting tables as QVDs

You then develop your front end Qlik applications which will feed from the same centralised QVDs generated at the step above; if you need to change your underlying data structure you change it only in one place and you keep your visualisation dashboards lean

Re: Best practices document

qlikdeveloper9999 — Mon, 27 Apr 2020 22:14:32 GMT

I have come across a solution following this approach. I am not sure whether this is the optimal and one of the best approaches to follow.

I believe that this approach works for small number of reports but I can't see it scale up. Maintenance can quickly become a nightmare.

Why data modeling has to be done in qlik? I understand that the engine is optimised but I can't say that it follows the typical enterprise data warehousing principles and methodologies.

Thanks alot for your time and comments. I am still trying to find an ideal/best approach.

Re: Best practices document

lorenzoconforti — Mon, 27 Apr 2020 22:41:41 GMT

You can do data modeling outside, it really depends on your data sources, how many you have and what kind of dashboards you're planning to develop. If you have a data warehouse where ETL has already been performed and the data is ready to be consumed, all the better. You still need to pull the data and you might want to do it once and make it available to all your Qlik dashboards

Keep in mind that, depending on the complexity of the dashboards you want to develop, you might still need to do some ETL in Qlik.

I've worked on projects where most of the ETL was done in Qlik and others where data was pretty much ready. We don't live in an ideal world and I found I had to adapt to different scenarios

Bear in mind it's pretty common to have ETL engines with BI applications like Alteryx, Tableau Prep, Power BI with Power Query