Fixed Filter values per Report instance on Dashboard (feature request)

Richard Wolters shared this idea 36 days ago
Idea Logged

Hi,

We very much like the improvements that were made in 9.3. What we are missing however is the following (as an example):

  • Let's assume we have a single report for sales per region. The report has a filter: Region
  • Now we want a dasboard with 3 reports: sales for region A, sales for region D and sales for Region F
  • We'd like to place the report 3 times (as a copy) on a dashboard, for regions A, D and F
  • Per copy of the report we'd like to predefine the filter and that filter should not visible nor editable for the consumer of the dashboard. The latter should be available as an option (every dashboard consumer can than pick his 3 favorite regions as an example)
  • As far as we know we currently need x copies of the report to achieve our goal. Besides redundancy ist causes a lot of additional work to keep those almost identical report in sync

Hopefully this makes sense. If you need more details or examples please let me know!

Kind regards, Richard

Comments (9)

photo
0

Hi Richard,


Thanks for reaching out to support with your issue. I think I was able to to achieve what you were looking for via the report bookmarks function - here you can set multiple pre-defined filters.


2b3edee78a07545349b525a2de13856b


You can then choose between these filtered bookmarks when adding the report to the dashboardv-5d208dace60798426591723f26ea9764


This results in having multiple "versions" of the same report on a dashboard.

b9a657aad82cc42710f8724350b990d6

Does this method look like a viable solution in this case?


Thanks,

Eric

photo
0

Hi Eric,

That's an interesting suggestion that I wasn't aware off. This will come in useful in some cases.

However in the described scenario the report exists in the primary and should be reused in different client orgs, each with their own data sources. Adding the bookmarks to the report could reveal confidential data from other clients and also the report can't be modified in the client org(as intended)


Regards, Richard

photo
0

Hi Richard,

Thanks for the clarification here, I neglected to consider your environmental variables in this case. There may not be a way to do this currently with Client Orgs and Data Source Substitution in play. Or if there is, it may involve some custom coding.... does your organization subscribe to our Extended Services plan?

I'm wondering if you guys are using web services in the environment? If so, you might be able to create a call for specific report instances / filter values, see here for details -

https://wiki.yellowfinbi.com/display/yfcurrent/Functional+Report+Services

That said, I think we'll be able to get this feature request submitted - Once I get a replication scenario going and chat with the team, I will likely go ahead and create a dev task. I'll keep you up to date here, and let you know if I need any additional info.

Thanks,

Eric

photo
0

Hi Eric,

I'm not aware of the Extended Services plan, perhaps because we are a reseller of YellowFin? I'll talk to Jean about this.

We prefer the no-code option in general: our customers can/should reuse our 'standard' content, present in the primary, if possible or use this as a template. If coding is involved we fear that it may slow down adoption in general. With the reuse in mind we'd like to keep the amount of the 'same' reports to a minimum, also for maintenance reasons.

It would be great to get this submitted as a feature request! Thank you for exploring this in so much detail.

Regards,

Richard

photo
0

Hi Richard,

I talked to a colleague about this, and they said that when data source substitution is in play, the only option is to use the "first filter value" as a default.

I've goa t data source substitution setup going, and Now I'm creating some content.... is the mandatory filter the same between all client orgs in this case? Would you be able to provide some annotated screenshots of the current setup for reference? Perhaps you'd prefer to organize a screen share, to help provide some additional info here?

Thanks,

Eric

photo
0

Hi Eric,

Perhaps to make it even more clear what we would like to achieve:

  • There is a report in the primary
  • The client-orgs use datasource substitution
  • In a client-org we'd like to place the 'primary-report' multiple times on the same dashboard, each with a fixed filter (let's say 3)
  • In another client-org a similar setup, but this time with 2 'versions/fixed filter values'
  • Every client-org has specific filtervalues (due to the datasource substitution)
  • The 'primary-report' is now 're-used' 2+3 = 5 times, showing 5 different sets of data

In the current setup we need to make as many copies of the 'primary-report' as there are specific filtervalues needed. This needs to be repeated in every client-org. This redundancy causes a lot of work to keep the reports in sync, per client-org but also for all client-orgs in the system.

When using the suggested 'first filter value' as a default we end up with duplicates of the same data.

Of course I'm more than willing to do a screen share to explain this in more detail.

Best regards,

Richard

photo
0

Hi Richard,

Thanks for the additional info here. So if I'm following, it sounds like all we need here is the ability to define these filters on the individual dashboard reports as per the client org, instead of just having the "first filter value" as default?

If so, I think I can get an enhancement request made for this. I'm also wondering if maybe there's a way to do this with an existing function, like a parameter. I'll triple check to see if anyone has any other ideas now.

Thanks,

Eric

photo
0

Hi Eric,

Exactly: per instance of the same report on a dashboard (for every client org) an individual default filter, as an additional option to the first filter value.

It would be great to see this implemented in a not to near future!

Thanks for the update already.

Regards,

Richard

photo
0

Hi Richard,

Thanks for the confirmation here. I've gone ahead and created a developer task to look into this functionality. I'll provide updates here as they become available. I'll in turn mark this ticket as Idea Logged for now.

Thanks,

Eric