When broadcasting a report with current filters, they are not applied to linked filters.

Siim Neljandik shared this problem 5 years ago
Resolved

When I tried to share a report that had an inner join to the same view in it, the inner join fields did not have any of the linked filters applied to them.

Replies (4)

photo
1

Hi Siim,

so far I haven't been able to replicate this sort of issue over here, but I would like to clarify a couple of points with you because I suspect I may be doing the wrong steps.

In the title of this ticket you mention "broadcasting" a report, but in the ticket's text you mention "tried to share" a report. These are two different features in Yellowfin (Broadcast and Share), so could you please confirm which one it should be (or both).

Also, I'm not really sure of how your report is set up - I'm not sure about the inner join to the same view. So I'm hoping you could please provide some appropriate screenshots so I can get a full understanding of how your report is configured.

thanks,

David

photo
1

Hello,

The title was correct, I am only talking about the broadcast feature.

The report has a basic appended sub-query where the join is an inner join. The field that we are joining on is exactly the same field. The reason why I am suspecting that this is somehow to blame, is that this is the first time we see this problem with a broadcast and generally we use outer join.

Currently I made a workaround to this problem by setting the default filter values to the ones used in the "current filter values" broadcast and set the broadcast to use the default filters.

Sadly I can't share the faulty and working broadcasts here, however if you wish to go over any details of this problem then we can set up a call.

Thanks,

Siim

photo
1

Hi Siim,

thanks for clearing things up because with that information I was able to replicate the bug and so have raised product defect YFN-11694 so that it gets fixed.

Apologies for the inconvenience caused by it, and thanks for notifying us of its presence.

regards,

David

photo
1

Hi Siim,

Developers have looked into this issue, and determined this behavior is expected. In turn I'll go ahead and mark this ticket as Resolved at this point.

Thanks,

Eric

Leave a Comment
 
Attach a file