<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: A Cautionary Tale of QlikView	</title>
	<atom:link href="https://www.quickintelligence.co.uk/a-cautionary-tale-of-qlikview/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.quickintelligence.co.uk/a-cautionary-tale-of-qlikview/</link>
	<description></description>
	<lastBuildDate>Sun, 12 Jun 2016 21:45:08 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: Steve Dark		</title>
		<link>https://www.quickintelligence.co.uk/a-cautionary-tale-of-qlikview/#comment-5706</link>

		<dc:creator><![CDATA[Steve Dark]]></dc:creator>
		<pubDate>Wed, 07 Aug 2013 11:00:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.quickintelligence.co.uk/?p=1292#comment-5706</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.quickintelligence.co.uk/a-cautionary-tale-of-qlikview/#comment-5700&quot;&gt;Jane Jackman&lt;/a&gt;.

Hi Jane - usually my first day on site is often the basis on which I can win more days, if I get the &#039;where to start&#039; wrong that is also where it finishes!  People don&#039;t usually want to hear they have got things badly wrong - so it is a balancing act between propping up what is already there and starting to build proper foundations.  This is all part of the fun of QlikView consultancy!]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.quickintelligence.co.uk/a-cautionary-tale-of-qlikview/#comment-5700">Jane Jackman</a>.</p>
<p>Hi Jane &#8211; usually my first day on site is often the basis on which I can win more days, if I get the &#8216;where to start&#8217; wrong that is also where it finishes!  People don&#8217;t usually want to hear they have got things badly wrong &#8211; so it is a balancing act between propping up what is already there and starting to build proper foundations.  This is all part of the fun of QlikView consultancy!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jane Jackman		</title>
		<link>https://www.quickintelligence.co.uk/a-cautionary-tale-of-qlikview/#comment-5700</link>

		<dc:creator><![CDATA[Jane Jackman]]></dc:creator>
		<pubDate>Wed, 07 Aug 2013 10:13:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.quickintelligence.co.uk/?p=1292#comment-5700</guid>

					<description><![CDATA[Hi Steve,
I totally agree with you on all these issues. I think the problem is that senior managers are sold QV on the dream that it&#039;s really easy, anyone can do it and it doesn&#039;t need IT skills. So when you go into a customer months after they they started implementing apps to sort out &#039;a few problems&#039; you find a huge number of documents, odd practices and no foundations. 

Where do you start if you have been hired for just a few days? 

You really need to go back to basics, out a QVD layer in, design the best data structures, move as much as possible in the ETL and maybe provide a structured QVW for binary loads, but that won&#039;t fix XYZ chart for Fred Bloggs in Accounts in a few minutes which is what they hired you for.

 I get quite disheartened sometimes because what ever I end up doing I know it&#039;s not the best solution. It never can be.]]></description>
			<content:encoded><![CDATA[<p>Hi Steve,<br />
I totally agree with you on all these issues. I think the problem is that senior managers are sold QV on the dream that it&#8217;s really easy, anyone can do it and it doesn&#8217;t need IT skills. So when you go into a customer months after they they started implementing apps to sort out &#8216;a few problems&#8217; you find a huge number of documents, odd practices and no foundations. </p>
<p>Where do you start if you have been hired for just a few days? </p>
<p>You really need to go back to basics, out a QVD layer in, design the best data structures, move as much as possible in the ETL and maybe provide a structured QVW for binary loads, but that won&#8217;t fix XYZ chart for Fred Bloggs in Accounts in a few minutes which is what they hired you for.</p>
<p> I get quite disheartened sometimes because what ever I end up doing I know it&#8217;s not the best solution. It never can be.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Steve Dark		</title>
		<link>https://www.quickintelligence.co.uk/a-cautionary-tale-of-qlikview/#comment-2869</link>

		<dc:creator><![CDATA[Steve Dark]]></dc:creator>
		<pubDate>Sun, 31 Mar 2013 22:33:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.quickintelligence.co.uk/?p=1292#comment-2869</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.quickintelligence.co.uk/a-cautionary-tale-of-qlikview/#comment-2867&quot;&gt;Adam Cooke&lt;/a&gt;.

Indeed. Use of Excel and the Concatenate and Substitute functions have saved me lots of effort in the past.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.quickintelligence.co.uk/a-cautionary-tale-of-qlikview/#comment-2867">Adam Cooke</a>.</p>
<p>Indeed. Use of Excel and the Concatenate and Substitute functions have saved me lots of effort in the past.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Adam Cooke		</title>
		<link>https://www.quickintelligence.co.uk/a-cautionary-tale-of-qlikview/#comment-2867</link>

		<dc:creator><![CDATA[Adam Cooke]]></dc:creator>
		<pubDate>Sun, 31 Mar 2013 22:15:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.quickintelligence.co.uk/?p=1292#comment-2867</guid>

					<description><![CDATA[Hi Steve, looks like a good approach, might give it a try at some point next time im against hundreds of columns!]]></description>
			<content:encoded><![CDATA[<p>Hi Steve, looks like a good approach, might give it a try at some point next time im against hundreds of columns!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Steve Dark		</title>
		<link>https://www.quickintelligence.co.uk/a-cautionary-tale-of-qlikview/#comment-2852</link>

		<dc:creator><![CDATA[Steve Dark]]></dc:creator>
		<pubDate>Sat, 30 Mar 2013 17:56:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.quickintelligence.co.uk/?p=1292#comment-2852</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.quickintelligence.co.uk/a-cautionary-tale-of-qlikview/#comment-2839&quot;&gt;Adam Cooke&lt;/a&gt;.

Hi Adam.  
Almost regardless of situation I would avoid Qualify.  A way of achieving a similar, but more flexible, result is to build your load statement in Excel.  To do this, get a list of fields in the given table and paste these into Excel, into column A.  In column B put the following expression:
&lt;strong&gt;=CONCATENATE(A1, &quot; as [TableName &quot;, A1, &quot;],&quot;)&lt;/strong&gt;
Now, copy that expression the whole way down the list of fields.  Finally, copy and paste column B back into your QlikView document and you have code for qualified fields in a manageable way.  You can also then tidy up the field names, getting capitalisation and spaces sorted.

Different documents for different purposes is not an issue, in my opinion, as long as you have designed for each audience and properly thought through how to best leverage your ETL layer to support multiple presentation documents.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.quickintelligence.co.uk/a-cautionary-tale-of-qlikview/#comment-2839">Adam Cooke</a>.</p>
<p>Hi Adam.<br />
Almost regardless of situation I would avoid Qualify.  A way of achieving a similar, but more flexible, result is to build your load statement in Excel.  To do this, get a list of fields in the given table and paste these into Excel, into column A.  In column B put the following expression:<br />
<strong>=CONCATENATE(A1, &#8221; as [TableName &#8220;, A1, &#8220;],&#8221;)</strong><br />
Now, copy that expression the whole way down the list of fields.  Finally, copy and paste column B back into your QlikView document and you have code for qualified fields in a manageable way.  You can also then tidy up the field names, getting capitalisation and spaces sorted.</p>
<p>Different documents for different purposes is not an issue, in my opinion, as long as you have designed for each audience and properly thought through how to best leverage your ETL layer to support multiple presentation documents.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Adam Cooke		</title>
		<link>https://www.quickintelligence.co.uk/a-cautionary-tale-of-qlikview/#comment-2839</link>

		<dc:creator><![CDATA[Adam Cooke]]></dc:creator>
		<pubDate>Sat, 30 Mar 2013 01:06:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.quickintelligence.co.uk/?p=1292#comment-2839</guid>

					<description><![CDATA[Another great article! In my opinion extracting the ETL functions of the initial Qlikview document into ETL QVWs and then sitting both the applications on top of the same data model QVDs is a good way to maintain consistency and reduce head aches if the client absolutely insists on having two separate applications.

Idealy a combination of section access, show hide variables and good design should limit the need to copy paste qlikview documents.

I think best practice is to avoid the Qualify statement in production as you say, although if there are hundreds of fields involved and a short delivery time frame it may still get in there, just need to make sure to clearly comment the code!!! I wrote an article about handling challenging clients also on webofwork.com.]]></description>
			<content:encoded><![CDATA[<p>Another great article! In my opinion extracting the ETL functions of the initial Qlikview document into ETL QVWs and then sitting both the applications on top of the same data model QVDs is a good way to maintain consistency and reduce head aches if the client absolutely insists on having two separate applications.</p>
<p>Idealy a combination of section access, show hide variables and good design should limit the need to copy paste qlikview documents.</p>
<p>I think best practice is to avoid the Qualify statement in production as you say, although if there are hundreds of fields involved and a short delivery time frame it may still get in there, just need to make sure to clearly comment the code!!! I wrote an article about handling challenging clients also on webofwork.com.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Steve Dark		</title>
		<link>https://www.quickintelligence.co.uk/a-cautionary-tale-of-qlikview/#comment-2312</link>

		<dc:creator><![CDATA[Steve Dark]]></dc:creator>
		<pubDate>Wed, 13 Mar 2013 21:02:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.quickintelligence.co.uk/?p=1292#comment-2312</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.quickintelligence.co.uk/a-cautionary-tale-of-qlikview/#comment-2272&quot;&gt;HIC&lt;/a&gt;.

Thanks for your comment Henric.  It&#039;s always good to get confirmation that my thinking on these things are on the right track.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.quickintelligence.co.uk/a-cautionary-tale-of-qlikview/#comment-2272">HIC</a>.</p>
<p>Thanks for your comment Henric.  It&#8217;s always good to get confirmation that my thinking on these things are on the right track.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: HIC		</title>
		<link>https://www.quickintelligence.co.uk/a-cautionary-tale-of-qlikview/#comment-2272</link>

		<dc:creator><![CDATA[HIC]]></dc:creator>
		<pubDate>Tue, 12 Mar 2013 13:38:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.quickintelligence.co.uk/?p=1292#comment-2272</guid>

					<description><![CDATA[&quot;The use of the QUALIFY statement ..., whilst it can be useful for rapid profiling, should never find its way into a production environment.&quot;

Couldn&#039;t agree more.

HIC]]></description>
			<content:encoded><![CDATA[<p>&#8220;The use of the QUALIFY statement &#8230;, whilst it can be useful for rapid profiling, should never find its way into a production environment.&#8221;</p>
<p>Couldn&#8217;t agree more.</p>
<p>HIC</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/?utm_source=w3tc&utm_medium=footer_comment&utm_campaign=free_plugin

Page Caching using Disk: Enhanced 
Minified using Disk

Served from: www.quickintelligence.co.uk @ 2026-06-13 20:12:30 by W3 Total Cache
-->