tag:blogger.com,1999:blog-4084380583916091329.post6130903767342198237..comments2022-05-23T10:55:58.890+01:00Comments on One Qlik at a Time: Checking your data made itChris Johnsonhttp://www.blogger.com/profile/05704093510036584239noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-4084380583916091329.post-30295618034549772912012-09-21T11:39:40.532+01:002012-09-21T11:39:40.532+01:00Excellent post, Chris . I always check my data as...Excellent post, Chris . I always check my data as you describe. But I can suggest another check also. As you mentioned on your warning both table box and list box reflect only one records/value in the list if all fields in the record are equal. So if you need make sure that your extracted table has a unique key (in ERP database it calls primary key) you have to check how many records you have with the unique key in your extracted table. <br />Sometimes missed or wrong primary key can lead to the incorrect data in QlikView application. <br /><br />To check primary key I use Chat - Straight Tables. All fields which consist your primary key in your table I select as Dimension and wright count function as Expression (for example , count(TransNo) )<br /><br />If selected dimensions consists primary key all record have to have 1 in the Expression fields (just sort this field as Descending to get all incorrect records in first lines) . <br />Anonymoushttps://www.blogger.com/profile/02974343920607530181noreply@blogger.com