QV27 Checklist for a good qlikview developer

If you are good qlikview developer, and like to work in steps, or good planed work. Then you should have some points in your mind - that should meet with your code.

This can lead to good product and code quality.

Data Model Performance

1. Synthetic keys removed from data model   
2. Ambiguous loops removed from data model   
3. Correct granularity of data   
4. Use of QVDs where possible   
5. Use integers to join tables where possible   
6. Remove system keys/timestamps from data model   
7. Unused fields removed from data model   
8. Remove link tables from very large data models   
9. Remove unneeded snowflaked tables (consolidate)   
10. Break concatenated dim. fields into distinct fields    
11. All QVD reads optimized   
12. Use Autonumber to replace large concatenated keys   

Interface Performance

1. Run QlikView Optimizer to test memory usage   
2. Minimize count distinct functions   
3. Minimize nested Ifs   
4. Minimize string comparisons   
5. Macros minimized or eliminated   
6. Minimize Show Frequency feature   
7. Minimize open objects on sheet   
8. Minimize set analysis against large fact tables   
9. Minimize pivot charts in very large apps   
10. Avoid "Show Frequency" feature on large data   
11. Avoid AGGR function when possible   
12. Avoid IF statements in calculated chart dimensions   
13. Avoid built-in time functions in GUI (inmonth, etc…)   

Design Best Practices                       

1. Use of colors for contrast/focus only               
2. Use of neutral and muted colors                
3. Use of templates/themes where available               
4. Display optimized for user screen resolutions               
5. Design consistency across tabs               
6. Formatting consistency across objects               
7. Most used selections at top - least at bottom               
8. Drop-down selections on all straight/pivot table columns               
9. Developer QV version matches production               
10. Test client types for rendering               
11. Use of Common Variables for expressions               
12. Use calculation conditions on large charts                

                       
Script Best Practices          

1. Naming standards used for columns, tables, variables               
2. Script is well commented - changes date flagged               
3. First tab holds information section               
4. Subject areas each have tab in script               
5. Use of Include files or hidden script for all ODBC connections               
6. All code blocks with comment sections               
7. All file references using UNC naming               
8. Business names for UI fields               
9. Security script in Inlcude file               
10. Turn Generate Logfile option on               
11. UPPER() function used on Section Access fields               
12. Publisher Service Acct added to Section Access               
13. Use numeric flags where possible