Drill Down Time KPI Report

Renato Marcello dos Reis shared this idea 5 years ago
Idea Logged

Hi Everyone,


I'm building a KPI report using a drill down funcionality. This feature works fine in the desing part of the report creation, but when I activate the report, the drill down link disapear.


Is this a bug or this feature doesn't work on KPI reports?

Replies (1)

photo
1

Hi Renato,

Thanks for reaching out. Drilling should work with KPI reports. Do you have some sort of Refresh Schedule set on the report?

I suspect this would be the case here. I built a quick test report with a Drill and you can see the hyperlinks, but that I'm also setting up a schedule:

Once I Save it though:

/wMdUjH+1ajVzQAAAABJRU5ErkJggg==

The links disappear, which is expected behavior. The reasoning for such is this: while the schedule refresh are set, report result will be cached until next schedule for refresh. During this time, running reports will fetch cached result instead of running a real time report. According to current functionality, drill through links will not be applied to cached report, therefore, it is an expected behaviour of yellowfin.

Of course I'm just speculating here until you can confirm whether a refresh schedule is set here, but if you can confirm whether this is true that'd be great.

Thanks,

Mike

photo
1

Hi Mike,Thanks a lot for your quick response. I appretiate your help on this case.


So, when I edit the KPI report and go to the refresh tab, it says that I have to change this configuration on KPI menu, because it's a KPI report. In the KPI menu, I have no option to change the refresh settings, because it's a "Time" KPI Type and doesn't require refresh configurations. The refresh settings only appear when I'm using KPI "Spot" or "Categorical" types.

photo
1

Hi Renato,

I apologize for not actually heading into the KPI settings here. It appears that indeed Spot and Categorical KPI types require refresh schedules, so drilling definitely shouldn't work on those two KPI types.

The Time KPI type though does state that it doesn't require a refresh schedule, so I'm not sure whether this is an oversight that would require an enhancement or whether this is intended behavior. I did just test this in 7.1 though, and it didn't work there either. Typically, if we have an instance of something working in a previous version and not in a current one it would be considered defective, but since this is not the case here, I'll go ahead and submit an enhancement request and just see what the dev team comes back with on this. Any potential updates regarding this matter will be posted here.

Regards,

Mike

photo
Leave a Comment
 
Attach a file