Drill-through report disappearing
Hiya,
I've created a custom drill-through report, not using a pre-defined view hierarchy. This drill-through is field>filter linked, and i have selected the option to open a pop-up window when the hyperlink (field) is clicked. I have found that this all works fine, yet every now and then the hyperlink will disappear completely and our users will not get a chance to view the drill-through report shown on the pop-up window.
When i proceed to edit the report's related content, i can see that my drill-through report has disappeared completely. As shown below:
Below is an image of how i set up the drill-through in the first place:
This hyperlinked field>filter relationship works fine for a few days and then will completely disappear, so i've been resetting it manually every now and then. It seems to disappear randomly but the max that it stays functioning is approx 2-3 days.
Both reports (parent and drill-through) use fields generated by a SAS program which updates SQL server. The parent report's database updates o/night, while the drill-through updates by the hour. I was thinking these differing refresh rates may have something to do with the drill-through disappearing. Any help greatly appreciated, cheers.
The same question
Hi Barry,
I'm sorry to say that I've never encountered an issue such as this previously - and it sounds like a strange one indeed....But I won't let that put me off!
I would tend to agree with your thoughts about the database updates having something to do with the issue, although I'm not exactly sure, it might be a table locking issue perhaps, maybe that causes Yellowfin to think the data source isn't available.
It would certainly be interesting to look through all of your logs that cover a period of 3 or so days when the issue occurred, so please zip up all log files in the folder <yellowfin>\appserver\logs and send them across. And if possible please give me a rough time of when you first noticed the report being broken.
I am wondering whether a restart of Yellowfin would fix the broken report when it occurs. The reason that this might work is the fact that Yellowfin works mostly from a local application cache rather than directly querying the Yellowfin database for the metadata, so if the report definition has been corrupted in the local cache then a restart would refresh the cache with the correct report metadata from the YF DB.
Of course it mightn't be easy for you to restart Yellowfin if it's occurring in your production environment, so there is another way we can test this - please download the file called "info_cache_enhanced.jsp" from the following Community Knowledge Base article:
https://community.yellowfinbi.com/knowledge-base/article/how-to-avoid-having-to-restart-yellowfin-after-backend-modifications-to-the-yellowfin-database
and then run it by appending it to your Yellowfin URL as follows:
http://<server>:<post>/info_cache_enhanced.jsp
and then click the "Clear" buttons under the Report Definition Cache and also under the View Cache. And if we are in luck that will fix the broken report.
Please let me know how this goes.
regards,
David
Hi Barry,
I'm sorry to say that I've never encountered an issue such as this previously - and it sounds like a strange one indeed....But I won't let that put me off!
I would tend to agree with your thoughts about the database updates having something to do with the issue, although I'm not exactly sure, it might be a table locking issue perhaps, maybe that causes Yellowfin to think the data source isn't available.
It would certainly be interesting to look through all of your logs that cover a period of 3 or so days when the issue occurred, so please zip up all log files in the folder <yellowfin>\appserver\logs and send them across. And if possible please give me a rough time of when you first noticed the report being broken.
I am wondering whether a restart of Yellowfin would fix the broken report when it occurs. The reason that this might work is the fact that Yellowfin works mostly from a local application cache rather than directly querying the Yellowfin database for the metadata, so if the report definition has been corrupted in the local cache then a restart would refresh the cache with the correct report metadata from the YF DB.
Of course it mightn't be easy for you to restart Yellowfin if it's occurring in your production environment, so there is another way we can test this - please download the file called "info_cache_enhanced.jsp" from the following Community Knowledge Base article:
https://community.yellowfinbi.com/knowledge-base/article/how-to-avoid-having-to-restart-yellowfin-after-backend-modifications-to-the-yellowfin-database
and then run it by appending it to your Yellowfin URL as follows:
http://<server>:<post>/info_cache_enhanced.jsp
and then click the "Clear" buttons under the Report Definition Cache and also under the View Cache. And if we are in luck that will fix the broken report.
Please let me know how this goes.
regards,
David
Hi Barry,
just wondering how you got on with this?
regards,
David
Hi Barry,
just wondering how you got on with this?
regards,
David
Hi Barry,
there has been no response for over a month now so the ticket will be closed, however, if you'd like to reopen it then all you have to do is to simply add a new post to it and its status will automatically change from "Answered" to "In Progress" and will appear in my work list.
regards,
David
Hi Barry,
there has been no response for over a month now so the ticket will be closed, however, if you'd like to reopen it then all you have to do is to simply add a new post to it and its status will automatically change from "Answered" to "In Progress" and will appear in my work list.
regards,
David
Replies have been locked on this page!