Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I have gone through Handling Metadata in QlikView by sinanozdemir and when I try to implement it ,it works for some tables and not for some.
I have attached a application.

Can any one look and see and let me know why is it?
Regards,
Sivasankar
I completely removed the whole data set and created a new data set without characters table. Again I couldn't see the comments for all the tables.
Find the attached example
Regards,
Siva Sankar
May be hic can confirm whether it is an issue or any steps to follow to prevent this error.
Regards,
jagan.
Well, I am on version 12 and the above proposed solution works. I have been using Comment for a while and never had a problem at all. I will take a look again tomorrow. Meanwhile, let's see if someone else has an idea. I am also not aware of any limitations. If there are any, they should be included in the help.
Hmmm, the QV12 Release Notes don't contain a list of fixed bugs. Apparently there weren't any bugs to fix. It's probably the switch to the Qix engine that fixed the Comment statement problem.
IMHO the quickest way to get an answer to your question is to contact Qlik Support.
Good luck,
Peter
Hi Peter/ Sinan,
Thanks for the reply. Did you try open the attached qvw file in version 12 and let me know if you are able to see the comments for all the tables in Table
Sorry, nocando. Skipping QV12 until SR1 is released.
I am confused by this situation right now because never had an issue. However, it looks like you need to model your data in a way that the tables which have the same primary keys need to be placed after each one:


Again, if this is something that I have never had a problem with. This might be related to only INLINE tables, but I think we need a confirmation from Qlik so I will try to contact them as well to see if I get an answer.
Sorry for the inconvenience.
Hope this helps.
It seems like I don't have sufficient privileges to contact the Qlik Support directly. I will keep searching this issue. Stay tuned.
I submitted a case regarding this behavior with Qlik Support team and they registered it as a Bug and working on it.
Will wait for the fix in next release.
Regards,
Siva Sankar
Thanks shankarece. I will also update the document.