We have a web service call which has paging parameters to get the desired number

silkik235 over 9 years ago

We have a web service call which has paging parameters to get the desired number of records per page.
As per our requirement, we expect the results from webservice in batches- for example, it'll first load 100 records from web service using "HttpQuery" component and displaying it in a grid in our SAIL form with paginginfo.
Once user clicks on pagination info or any similar component, it'll load next batch of 100 items from webservice response.
Can we achieve this scenario? If not, could you please suggest any workaround?

Discussion posts and replies are publicly visible

Parents

0 PhilB
A Score Level 1
over 9 years ago

Try defining a local variable of type a!pagingInfo with the startindex initially set to 1 and batchSize set to, say, 20, and then pass that a!pagingInfo into the rule that uses the a!httpQuery function and use the a!pagingInfo.startIndex and a!pagingInfo.batchSize as inputs to the a!httpQuery function. The paging info will need to be defined as the saveinto on the grid, and should subsequently update as the grid is paged through.

Alternatively, have a look at the bind() functions - they may be of service.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 PhilB
A Score Level 1
over 9 years ago

Try defining a local variable of type a!pagingInfo with the startindex initially set to 1 and batchSize set to, say, 20, and then pass that a!pagingInfo into the rule that uses the a!httpQuery function and use the a!pagingInfo.startIndex and a!pagingInfo.batchSize as inputs to the a!httpQuery function. The paging info will need to be defined as the saveinto on the grid, and should subsequently update as the grid is paged through.

Alternatively, have a look at the bind() functions - they may be of service.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data