We don’t force them either, we’re not the script police ;) Often though, we’ll find that a client isn’t using any standards, so in that case we suggest ours as a starting point on which they can base their own conventions. Would be very interested to hear what you think of it, and of course any suggestions and improvements would be much appreciated.

Thanks Barry. It’s always good to have a written down set of coding conventions. We don’t force our own on clients, but we do recommend things. Will be looking with interest at your document!

If you like that, you might also like our coding conventions: http://www.bitmetric.nl/bitmetric-qlikview-coding-conventions/

The page’s in Dutch, but the document is in English. You need to leave a valid email address (it will be emailed to you), but don’t worry, I won’t spam you. Unless you’re in the Netherlands…. ;)

Hi Gysbert – thanks for sharing Barry’s link. Another good one of Barry’s to mention on this topic is his post on aligning code. Getting everything right includes the stuff that users can’t see as well as the stuff they can. http://www.qlikfix.com/2014/06/16/aliases-indent/

Hi Chris,
I presume that where you are seeing things out of alignment you are using the Full Browser (a.k.a. Ajax) client? If you use the IE client then things will display exactly as in the Desktop, and in some cases will be quicker. Personally I try to avoid IE, so therefore don’t use the plugin. Generally things work okay, but as you say there are a few places where it does not. If you know all your users have the same client you could un-align things in Desktop so it renders right in the browser (though this feels wrong).

I have seen big problems when the font scaling is turned on in Windows 10 (and 8, I think). If this is causing issues, due to fonts scaling larger than images in the frame, you may want to encourage users to set their font scaling to 100% – this may not be desirable on a very high res machine though. This is one place where Sense has an edge – design that is responsive to resolution.

The other major issue which I don’t think has been addressed yet (though I have not tried V12 server) is that if you have a Grid Style Multibox where the title should appear above the drop down it will always show to the right. The upshot of this is you can’t use that feature if any of your users use the Full Browser client.

Thanks for your comment.

Totally agree with you and thankfully I didn’t fall foul on any of them. My only bug bear is that having spent an age getting everything aligned and sized as I want them, when I view the finished article through access point then some of the objects are out of alignment, which can be frustrating. Any tips to solve this?

Hi Barry,

I know we have had this conversation previously, and I still say I prefer using the AS statement. My reasoning for this is simple, and that is that you can see a field in the front end and then do a search for it in the load script and find exactly where that field came in and what has happened to it during the load. This is also one of the reasons I do not like LOAD * (there are others also). The RENAME FIELDS use of a Mapping Table is something that people should be aware of though – as it can be a useful trick.

Thanks for your comment.

I would always advise fixing field names as soon as possible, so in your case that would be going into the QlikView app you are doing a binary load from into QlikSense. If you are not able to go back and amend that, then Barry’s suggestion of using a MAPPING table with RENAME FIELDS is a good alternative. You can also use the RENAME FIELD statement, but that is tedious if you have many fields to do.