Problem with Co-display reports.

Hi Pratap,

Thank you for reaching out. How are your filters and co-display joins set up here? This is difficult to say without knowing how the data is setup and confirming that the new data should indeed be displaying in the co-display report. Also, is the co-display report using the same View as the Main report? Might it be cached?

I look forward to your responses.

Thanks,

Mike

Hi Mike,

I am using the same view for both the reports. first report showing detailed data and 2nd showing just summary.

here I have attached screenshots.

Regards

Pratap

Hi Pratap,

Thanks for your response. Based on your screenshots, the corresponding columns in the sub-report match those in the main report, those values being "0". So I'm assuming if you were to filter those results to make them not 0, what you're saying is the bottom one wouldn't change correctly? Also, can you replicate then send a compressed copy of your entire logs folder located at <YellowfinInstall>/appserver/logs along with corresponding timestamps where you applied and ran the filters?

Thanks,

Mike

Hi Pratap,

Try making the filters, "Cached on demand" for the child reports. This assures that every time the report is called the data is refreshed and made an option for selection. Otherwise, you will need to manually cache or schedule a cache. I know that this is the case if the report was run on it's own and it might be the case for co-display also.

Hi Pratap/Larry,

Thank you for the input Larry!

Pratap, I too recommend trying Larry's suggestion of making the filters "Cached on demand" for the child reports, perhaps even before sending logs, to see if this solves your issue.

Regards,

Mike

Hi,

Thanks, Larry and Mike for your suggestion. But This will not work in my case.

Let me explain the steps to reproduce the issue.

I have created a simple report with two fields and a subreport showing total record count. both reports based on the same view and same parameter (Date Parameter which can't be "Cached on demand")

Opened report with a date range

and it brings the right result in main and subreport. 4 records and 4 record count.

now I have created a new record in my database which falls in the same date range. and pressed go (note that I am not reopening report just refreshing report with "Go" ).

It worked fine for the main report and reflected newly created record in the report but not in Sub Report. the count must be 5 at this point but it is showing 4.

now closed the report and reopened with the same date range . and it brings right result first time only.

Hope you understand the issue. we are facing the same issue in all the reports having subreports. (Checked same case on YF 7.3 as well as YF 7.4 ).

I think this is not an instance-specific issue and can be replicated in any instance. I have attached YFX file for the same Example report shown above.

Regards

Pratap

Hi Pratap,

Thank you for your detailed replication steps! I am definitely going to attempt to replicate this first thing tomorrow morning. I just have one further question first: when you add a new data value in your db and re-load the report, from that point on, you are able to see and keep the newly added data, correct? The issue is that if you add new data and re-filter, the new data shows in main report, but not in the sub-report, and when you reload the report, everything works as expected from that time on, correct?

Regards,

Mike

Hi Pratap,

I am able to replicate what you are seeing here:

Original results:

After adding a new Artist row in my database and repressing "Go":

Then finally, closing and reopening:

I've gone ahead and raised this as a defect in our internal tracking system. It looks like closing and reopening the report will have to be the workaround for this in the meantime. Any potential updates regarding this matter will be posted here.

Regards,

Mike

Hi Mike,

Can you please provide the defect ID and let us know when it is going to be fixed or this is fixed in any new version of yellowfin.

Thank you!

Sumit K

Hi Sumit,

There is no updates on this task as of yet, but I've gone ahead and requested one. I also added you to our client list of those who's being affected by this behavior. The defect ID is YFN-10474.

Regards,

Mike

Hi All,

This has been fixed and published in 7.4.11. You can download latest builds here.

It is also marked for next BMC 8.0.2 and BMC 7.3 builds.

Please download and test when you get the chance and let us know how goes.

Regards,

Mike

Regards,

Mike