Ability to set default filter values when access filters are used

Hi Gadi,

Thanks for the input! In thinking about this more, I tend to think that this will be difficult to implement, but do agree that there are cases where it could be quite useful.

I am going to go ahead and convert this one into an idea so we can get the product teams input.

Regards,

Nathan

I wonder if creating a freehand SQL option to retrieve default filters values would solve most issues. We don't allow that option as yet, but maybe something to think about.

This is what I have been thinking

In the same way that we can create a list of cached values using freehand sql we should be able to do the same with getting a default value

We should be able to implement this using Source Filters as well (using the same methodology that we would have to use for create a list of values)

This should be very easy to implement

You could even do it without freehand sql if Source Filter is used (where the Source Filter has to return 1 or many rows dependent on whether the operand is EQUAL or IN)

If you want to discuss this more give me a call - we would love this (have customers who would really like this feature)

Thanks Yoav, noted your interest on the enhancement ticket.

Hi Jenny thanks for the suggestions.

Unfortunately at this point in time this is not currently planned, though something that will be reviewed in the coming weeks, so we can work out we can address in the future, and when exactly that may be.

Sorry for being vague on this, it's just hard to provide more info without this fully being explored.

I'll keep you posted on any updates.

Regards,

David

Hi Nick,

This is definitely at the top of our improvements list, I know we were planning on bringing this in 8.1, though I think it's been pushed back a bit. There is a bit of work do it, as we need similar functionality for data source substitution. Pretty sure we're going to be implementing it via this feature first. We will let you know once it's ready for a release, it will happen!

Regards,

David

Thanks David. Good to know it is still in pipeline.

So the feature you have linked to, would it be similar to setting custom query filter values? or more static?

For example a query that returns a dataset mapping each access filter value to a single default value?

Id A -- Default A

Id B -- Default B

Or more along lines of independent query that returns a single value and won't be filtered by acccess filter or allow parameters?

Regards, Nick

Hi Nick,

It would be like a custom query filter, not a hard coded static filter. In saying this none of this is done as yet, but we're aware of the situations where it's needed so will ensure source filters and data source substitution is supported.

Thanks,

David

Any update on this?

Hi Roopinder,

We're making some changes in the upcoming v9 to accomdate these scenarios. Will update this idea once it is officially out.

If you would look to find out more on v9, please reach out to your local Yellowfin CSM, or alternatively email support@yellowfin.bi to open a private support ticket and we can see how we can further assist.

Regards,

David

Sorry to chip in so late but setting the default value for each customer / enduser / clientorg might be difficult as different endusers might have different idea's about what the default filter should be.

As I see it the access filter (or any filter) is used give you option's and one of the should really be to run the report with a set default filter option. A simple checkbox to set default to first value found would be enough. Especially with the idea to have filter value's remembered on dashboards also.

In our case that would be a nice solution. For new endusers the report is then shown with data and they have the option to change. Instead of an empty report or all values (in our case hospital so it is not OK to show just all data).

Regards,

JeRoen

Thanks JeRoen for the feedback, it's always good to get more use-case scenarios to help us ensure we're really thinking about the change impact.

There are a few ways we want to tackle this, but I do think having it default to the first option in the list is going to be the best outcome for most people. This way people will always see data, and it will only be for the first thing in the list, so they won't see everything straight off the bat, but they will see something, and then have the ability to change it again and save the bookmark for themselves.

Will keep you posted on updates, but I can assure you this is one of the enhancements we've been reviewing internally to get some traction.

Thanks,

David

Hello David,

Thanks for letting me explain my use-case.

I do not understand very well what the ability to have bookmarks would solve about the question asked. Only when you have a lot of filters you want to change or very large filters and you want a complex combination of values. For that the current bookmarks is fine.

In my case I have only one filter I want a dynamic (for each user) value for. We are talking about access filters after all, of which you will have, in most cases, just a few. To use a bookmark you need to open the sidebar, click bookmarks and click the bookmark you want. To adjust a filter I open the sidebar, click the filter and then the value. So both situation demand 3 clicks.

So with 20 reports endusers have to manually create 20 bookmarks (for each report one) to get the value they want. As about 50% of endusers will only have 1 option in the filter (hospital filter so just one but different between users) there will also be people who have 2 or more. For those 50% you do want to show the report/dashboard immediately without the need to select a filter or bookmark. The the first value scenario would be very good in that situation.

Also bookmarks do not work on dashboards. Has this changed in 9?

Regards,

JeRoen

Hi JeRoen,

Bookmarks on dashboards are supported on v9.

Everything else you're after is something that needs to be looked at for the enhancements pitched. There are essentially 2 enhancemnets that are being looked at;

-The ability to set the first value as a default value

-The ability to set a default value based on a custom query.

Both are being looked at updates will be posted across these ideas. Until then there is not much more I can offer unfortunately.

Sorry for the vague answer.

Regards,

David