Faceted Search Report pagination on REST Data Source does not work after filter/selected facet

Hi Carsten,

Thank you for a quick response. I wish I would have posted the question earlier 😀.

Synchronization is a great feature and I use it extensively. Unfortunately, my post is just an example for testing purposes. Real data is in thousands and growing. Concerned of filling up XE data limit. Also as the data is dynamic real time is appreciated (status changes by users in the source system, etc.). I use facet filters and send them to REST Data source to get appended to URL to limit returned number of rows.

Will attempt to build a custom pagination with post processing query. If the approach fails - will return first 100 and will wait for 21.2 😊. It's 73 days till Christmas.

As a side note, paginated IR has the same pagination bug when going against filtered REST Data Source.

Thank you!

Thank you Carsten! That would be great. I did attempt to use REST Source Plug-in from sourforge as an example, but could not quite make it to work to capture filtering and order by variables.

Anything you can put together as an example that support filter and order by string creation will be appreciated.

Thank you.

Hi Carsten!

Thank you very much for a plug-in sample! It does fix the pagination issue and provides great insight into construction of filtering capabilities for the REST call.

However, I do have some follow up questions about filtering and order by capabilities (struggling to decide if new threads need to be open, or leave it here as it goes together with your sample code):

a) while I am able to loop through the filter parameters in IR. The same code does not work in faceted search.

The code:

does not return filters set by facets (debug prints Parameter Count: 0). How does one access facet filters in REST plug-in?

b) while running some tests I notices that filters are applied locally (looking at Generated Component SQL in debug window) regardless whether I executed "p_result.local_filters( p_result.local_filters.count + 1 ) := p_params.filters( f );" command or not. Is this a bug? Tested with IR.

c) we can loop through order bys with this loop "for f in 1 .. p_params.order_bys.count loop", but how does one add/remove order bys from the local execution? Tried something like this, but it does not work:

for f in 1 .. p_params.order_bys.count loop

p_result.local_order_bys( p_params.order_bys.coun + 1 ) := p_params.order_bys( f );

end loop;

Thank you.

Very helpful Carsten. Thank you!

a) You are correct. The first debug prints out the filters. It does seem there is a need for another loop to parse out the colon separated list. Also, I need to do some more digging to figure out where search type filters are stored. For the time being I have opted to use filter parameter under Search Results. It does seem a little more straight forward to create a filter string from the facet variables and pass it to REST Data source via parameter to execute. Works as expected. And you are correct to get a faceted search experience I only pass the general status to REST end point to limit the population - no counts there. Everything else is done locally with counts. So, its kind of mixed experience.

Frankly, there are two other show stopper issues currently I am dealing with. Started two new threads:

b) will just pass them back per your recommendation;

c) Sounds like it's always applied locally by default. Makes sense.

Thank you again. This has been very informative.