Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Folks
I have this error coming up when I try to generate the cache for a dashboard, I have seen previous entries on here that refer to objects that use invalid dimensions and measures but I have gone through the entire list of objects in this file and still cannot get it to work.
Is there any way that I can interpret the log file message and understand the object reference that is causing the problem?
I've wasted hours trying to find this now, seem absolutely ridiculous that the log file cannot provide the object ID that is causing this problem.
Thanks.
I can't regenerate the metadata, the error I put on this thread is what happens when I try to regenerate the metadata!
Maybe you have some unsupported settings or objects: Triggers, Alternate states, "Always one selected value"?
When you say "unsupported" objects, do you mean that you cannot create a report using a dashboard that has any triggers at all on any objects? Or do you mean that you cannot use an object in a report that has triggers assigned to it?
There is an important distinction here, because if NPrinting cannot be run on any dashboard that contains ANY triggers then that is an insane situation, it means that every dashboard I have needs to be re-written just for NPrinting.
Where can I find documentation on Unsupported objects?
I mean unsupported documents having those objects.
your first source of truth is always Help.qlik.com:
cheers
Lech
Thanks for that, none of those things apply so still appears to be something inside an object, would just be good to have a method to find out which object rather than having to step through each property of each object!
Hi @NW1965
Please review the following article about this issue and how to work around and/or resolve it.
https://support.qlik.com/articles/000038346
Kind regards...
An Object is an instance of a Class , it is stored some where in memory. A reference is what is used to describe the pointer to the memory location where the Object resides. The message "object reference not set to an instance of an object" means that you are referring to an object the does not exist or was deleted or cleaned up. It's usually better to avoid a NullReferenceException than to handle it after it occurs. To prevent the error, objects that could be null should be tested before being used.
if (mClass != null)
{
// Go ahead and use mClass
mClass.property = ...
}
else
{
// Attempting to use mClass here will result in NullReferenceException
}
A NullReferenceException typically reflects developer error and is thrown in the following scenarios: