New Topic

Community Topic Idea Dashboards

David Registro

APAC SD Team

Nathan Schroeder

NA Business Team

Category Dashboards

Product Version 7.3

New column for Browse

YangyangCai shared this idea ago

Not Planned

Hi Team,

Currently our company is on the process of upgrading our clients site to 7.2.

And we found that the 7.2 provies fantastic improvement on browse interface. We planned to open the browse function for our clients.

In order to open the function for our clients, we need re-structure our content folders.

Currently, the information about each report shown in the browse only contains name, description, last modified, created by, run type, status, folder, sub folder, linked, broadcasts and tags.

Can we ask for a new column to show whether or not this report is on the dasbboard, which will save much time for us to do reports maintenance. Because sometims we create or import a report but does not put on the dashboard. And we are keen on removing any reduplicative reports on the background before we open browse function for our clients.

I am waiting for your reply.

Thanks,

Nancy

I like this idea 0

Replies (11)

Nathan Schroeder ●

Hi Nancy,

Thank you for bringing this to our attention. I believe that this idea could be a worthy candidate for inclusion in future Yellowfin builds. I am moving this post from "Questions" to "Ideas" so that the community can vote on it, and it can be reviewed by the product team. If you have any further questions or ideas, please let us know.

Thank you,

Nathan

Reply URL

YangyangCai ●

Hi Nathan,

Thanks for your reply and kindness.

Have a nice day.

Regards,

Nancy

Reply URL

Guest ●

Hi Nancy,

thanks very much for your idea. I will submit it to our product review committee to see if they approve of the enhancement.

In the meanwhile I have thrown together a little query to help you identify whether a report is in a dashboard tab or not, hope it does the job for you:

SELECT REPORTNAME,

CASE WHEN REPORTID IN (select entityID from ReportGroupEntity where EntityTypeCode = 'REPORT') THEN 'IN DASHBOARD' END AS DASHBOARD_STATUS

FROM REPORTHEADER

WHERE ReportStatusCode = 'OPEN'

ORDER BY DASHBOARD_STATUS

regards,

David

Reply URL

YangyangCai ●

Hi David,

Very appreciated your reply.

In terms of the query, does it possbile to run queries to put all reports in a dashboard tab to a new content folder?

For example, we have a service tab and a empty content folder called service, and we want to put all the reports on the service tab to this new content folder.

If the content folder arrangement can be done in the background, that will be a fantastic solution for us.

Many thanks,

Nancy

URL

Guest ●

Hi Nancy,

we don't support modifying the Yellowfin DB via the backend. However, having said that, I can give you a query to play around with as long as you are aware that you should make sure you have a backup of the Yellowfin DB before you start experimenting with it:

UPDATE ReportHeader

SET CategoryCode = <insert CategoryCode here>,

SubCategoryCode = <insert SubCategoryCode here>

WHERE reportName = <insert reportName here>

Hope you have some fun with that, and don't forget to backup your YF DB before the fun starts!

regards,

David

URL

David Registro ●

Hi Nancy,

I have spoken to the product team, and unfortunately at this point in time, there are no plans to have a column show if the report is used on a dashboard or not. It will open a can of worms, as there would need to be an extra security check , because if a person can see the report is used on a dashboard, but not actually access that dashboard, it would be even more confusing.

The request is still here , so it hasn't been deleted, just no plans to support this.

Sorry for the bad news.

Regards,

David

Reply URL

YangyangCai ●

Hi David,

We did not open the browser function to the majority of our clients.

Or maybe we have another category to select all the reports shown on the dashboard, like the draft category in the browser.

it would be appreciated if the function can be supported in the future.

Regards,

Nancy

URL

Guest ●

Hi Nancy,

please ignore this...I'm just adding a comment so that you're not the last commenter (if you're the last one then the ticket stays on my work list)

regards,

David

Reply URL

YangyangCai ●

Hi David,

Hope you are having a good day toady.

I have tested the sql you sent to us:

SELECT REPORTNAME, CASE WHEN REPORTID IN (select entityID from ReportGroupEntity where EntityTypeCode = 'REPORT') THEN 'IN DASHBOARD' END AS DASHBOARD_STATUS FROM REPORTHEADER WHERE ReportStatusCode = 'OPEN'.

But it seems that it does not filter out the old reports we put on the tab which has already been deleted from our dashboard.

For example, the deal book summary shows up twice, only the second report (754270) is on the dashboard, and the first one is not on the dashboard or any tab because the tab has been deleted, but the status still shows up as IN Dashboard.

Because our team would like to delete any inactive reports not put on the dashboard, it would be appreciated if you could provide another sqls to handle the above scenario.

Regards,

Nancy

URL

Guest ●

Hi Nancy,

My day is OK thank you, hope yours is also.

As you probably know we are not meant to support backend SQL queries....however.....just for you I will do it (but don't tell anyone!)

Please try this out and let me know if it performs the way you wanted it to (I gave it a quick test and it seems OK):

SELECT REPORTNAME, CASE WHEN REPORTID IN (

select entityID

from ReportGroupEntity RGE

inner join ReportGroup RG

on rge.GroupID = rg.GroupID

where EntityTypeCode = 'REPORT'

and rg.StatusCode = 'OPEN'

) THEN 'IN DASHBOARD' ELSE 'UNUSED' END AS DASHBOARD_STATUS

FROM REPORTHEADER

WHERE ReportStatusCode = 'OPEN'

and reportname = 'Deal Book Summary'

regards,

David

Reply URL

YangyangCai ●

Hi David,

Thanks for your reply.

But the script does not work, it still returns two results.

I think when the tab has been deleted, the reports put on it would not be updated with new dashboard status.

Regards,

Nancy

URL

Guest ●

Hi Nancy,

I've attached a movie of my test, it is definitely working for me, please have a look and tell me what you think.

regards,

David

Files:

Reply URL

YangyangCai ●

Hi David,

Thanks for your reply.

I have watched the video, and confirmed that I could replicate your testing case if I create a new tab or a new report.

But this issue seems to caused by historical data when we do upgrade. Specifically, Deal book summary is a very old report, and I am pretty sure currently (20160727-autoit build) there is only one on the tab, and another one is not been used for any tabs. But the operation (delete related tabs) may be happened in the previous version (such as 20151209), for some reason do not update Reportgroup YF table. And because we use import & export function to do upgrade, so the YF data always been same across different version.

The following is our upgrade roadmap, much appreicate if you could use 20151209 7.1 or 20141128 to do testing. If this issue happened in the old patche, how do we remove the replicate reports?

a14a4dd710da7a49e26778a83a236222

Regards,

Nancy

URL

David Registro ●

For clarity, enhancement is still not something we have planned.

Reply URL

Guest ●

Hi Nancy,

I will try to investigate this further but unfortunately I won't be able to do so at the moment, I'm not sure if you're aware, but writing backend queries to perform special tasks is not part of the support agreement, and as you can imagine I have to prioritize genuine support cases above special requests, and at the moment I have too many genuine support tickets to deal with, however I will do my best in the near future to look into this. I hope you can understand.

regards,

David

Reply URL

YangyangCai ●

Hi David,

Thanks for your reply,

No worries, I fully understand.

I will keep track of this issue to do some testings as well when I have time, just keep me in the loop and let me konw your progress.

Regards,

Nancy

URL

Guest ●

Hi Nancy,

Tim has let me know that you told him my previous efforts at helping you were wrong, and then he showed you how to correct the SQL code, so in view of this development I am changing the status of this request back to "Not Planned" and ceasing any further extra-Support work on it.

regards,

David

Reply URL

YangyangCai ●

Hi David,

Thanks for letting us know.

Your query does work for the new reports and new tabs in current build, but do not work for the reports created or deleted in previous build.

You could close this ticket right now, I will do further testing on this one when I have time, because I think our scenario is a little bit difficult to replicate. It is not your fault, much appreicate your efforts.

Regards,

Nancy

URL

Guest ●

OK, and the suggestion Tim gave you seemed to be the way you should go.

Reply URL