How to Schedule/Trigger a Cached Filter Refresh

Eric Hagfors ●

Hi Kevin,

Thanks for reaching out to support.

1. We have a web service call that can run scheduled tasks on demand, see here -

https://developers.yellowfinbi.com/dev/api-docs/current/#operation/addToScheduleQueue

2. It appears there isn't a way to currently run all (report?) cached filters per client org, I could make a dev request to investigate potentially adding this to a future edition of the software if that sounds like a good way forward here.

Thanks,
Eric

Reply URL

1

Kevin T. ●

Is there any API to get the list of report IDs? And is there any API that can refresh the cached filters for just one client at a time (the above scheduled task call still refreshes all orgs right?)

Kevin

Reply URL

1

Eric Hagfors ●

Hi Kevin,

We currently have the 'getreports' call, if you would like to see any additional parameters for that I could make a request to developers on your behalf to look into implementing this.

https://developers.yellowfinbi.com/dev/api-docs/current/#operation/getReports

No per client filter refresh API that I can see, that would be another developer task if you'd like to see this implemented, just let me know.

Thanks,

Eric

Reply URL

1

Kevin T. ●

We're asking these questions because we have 900 reports and multiple client orgs, which causes the cache filter refresh to take almost a day to run. Some client orgs are used more frequently than others, so if we could select only certain ones to update, that would help. Other than that, are there any other possible solutions? This is really hampering our regular usage of Yellowfin.

Kevin

Reply URL

1

Eric Hagfors ●

Thanks for the additional info. I've gone ahead and created a developer task to look into potentially adding this functionality to a future version of the application. I've attached this ticket to the task and added your organization as an affected client for tracking purposes. Updates to the task will be provided here as they are available. I'll mark this as Idea Logged for now; you can reach out to your CSM and request escalation of task ID YFN-26959 if needed. Feel welcome to reply here with any related inquiries.

Thanks,

Eric

Reply URL

1

Jesse Kahtava ●

Has there been any movement on this feature? We, too, would find it very useful.

URL

1

Mark McGuire ●

Hi Jesse,

I hope all is well,

We have no updates/progress on this as of yet, however, I have chased this up with our development team.

Regards,

Mark

URL

1

Mark McGuire ●

Hi Jesse (and Kevin),

I hope all is well,

I have since discussed this with the wider team and I would like to inform you of where we stand with this;

As mentioned we discussed this internally of which we are not sure the concept of refreshing a cache filter for an org makes sense. Cached filter refreshes happen for a specific piece of content (view, report). Views and reports can be created within orgs, or created at the default org and shared. So whether the cache is refreshed for the default org, a specific org or all orgs, would depend on where the content was created, and who it was shared with.

There are currently two ways to do this (to our understanding)

REST not legacy SOAP services. We support but do not maintain SOAP.

This endpoint - https://developers.yellowfinbi.com/dev/api-docs/current/#tag/caches - has sub-endpoints for updating the cached filters on views and dashboards - eg. https://developers.yellowfinbi.com/dev/api-docs/current/#operation/refreshViewCachedFilters and https://developers.yellowfinbi.com/dev/api-docs/current/#operation/refreshDashboardCachedFilters

If you (or client) has implemented views for each org, then you could just call this for each view in a particular org. If the view was shared from the default org, then it will update for all orgs (we assume).

This endpoint - https://developers.yellowfinbi.com/dev/api-docs/current/#tag/schedules - will run a specific schedule that has already been created. A schedule is automatically created if, when defining a filter, a scheduled refresh is configured. in theory, the REST user could log into the client org, and they should be able to request and run schedules created for that client org. Although, keep in mind, if you (or client) are sharing content from the default org, those schedules will exist at the default org level.

In addition, we also found this one https://developers.yellowfinbi.com/dev/api-docs/current/#operation/refreshDataSourceFiltersRPC - this is done per data source. We assume that would work with data source substitution per org. Some testing may be required here to put this to the test.

Let me know your thoughts, happy to assist where I can.

Regards,

Mark

Hi Jesse (and Kevin),

I hope all is well,

I have since discussed this with the wider team and I would like to inform you of where we stand with this;

As mentioned we discussed this internally of which we are not sure the concept of refreshing a cache filter for an org makes sense. Cached filter refreshes happen for a specific piece of content (view, report). Views and reports can be created within orgs, or created at the default org and shared. So whether the cache is refreshed for the default org, a specific org or all orgs, would depend on where the content was created, and who it was shared with.

There are currently two ways to do this (to our understanding)

REST not legacy SOAP services. We support but do not maintain SOAP.

This endpoint - https://developers.yellowfinbi.com/dev/api-docs/current/#tag/caches - has sub-endpoints for updating the cached filters on views and dashboards - eg. https://developers.yellowfinbi.com/dev/api-docs/current/#operation/refreshViewCachedFilters and https://developers.yellowfinbi.com/dev/api-docs/current/#operation/refreshDashboardCachedFilters

If you (or client) has implemented views for each org, then you could just call this for each view in a particular org. If the view was shared from the default org, then it will update for all orgs (we assume).

This endpoint - https://developers.yellowfinbi.com/dev/api-docs/current/#tag/schedules - will run a specific schedule that has already been created. A schedule is automatically created if, when defining a filter, a scheduled refresh is configured. in theory, the REST user could log into the client org, and they should be able to request and run schedules created for that client org. Although, keep in mind, if you (or client) are sharing content from the default org, those schedules will exist at the default org level.

In addition, we also found this one https://developers.yellowfinbi.com/dev/api-docs/current/#operation/refreshDataSourceFiltersRPC - this is done per data source. We assume that would work with data source substitution per org. Some testing may be required here to put this to the test.

Let me know your thoughts, happy to assist where I can.

Regards,

Mark

URL

1

Mark McGuire ●

Hi Jesse,

I hope all is well,

I just want to touch base to see if you had chance to read through my last response. If you can get back to me that would be great.

Happy to assist where I can.

Regards,

Mark

URL

1

Mark McGuire ●

Hi Jesse,

I hope all is well,

I'm touching base again to see if you've had chance to read through my detailed response. If you can get back to me I would appreciate this greatly.

Regards,

Mark

URL

How to Schedule/Trigger a Cached Filter Refresh

Replies (5)