Clicking on the last page/record returns an error attached.

@vinitl Hi, I have just put forward one more approach (simpler for you rather - Creation of one rule and including it in any place that you want to query analytics) and attached the updated main rule of yours accordingly. Please go through them and let me know if you have questions or issues.

Added to above, I would like to make some comments about the implementation of the attached main rule of yours:
1. It would be good to construct a filterset and thereby query the analytics upon interaction with the filters or paging grid rather than having these in with(). Becausee having these in with() causes the query evaluation and the filterset construction every time.
2. I would like to suggest to opt for a different approach for making of query. Configure a button (Name it as 'Search') and upon clicking this button perform the query analytics call with the filters as selected by user. This way we can restrict the costlier queries.
3. isnull has been used extensively. I would like to suggest to use rule!APN_isBlank (or an equivalent implementation) because isnull might evaluate to true even if a variable holds blank value in SAIL.
4. You might think of extending the rule and can make it much generic so that it can be reused much effectively. But please bear in mind that writing a rule as much as generic results in degradation of performance.

@vinitl Hi, I have just put forward one more approach (simpler for you rather - Creation of one rule and including it in any place that you want to query analytics) and attached the updated main rule of yours accordingly. Please go through them and let me know if you have questions or issues.

Added to above, I would like to make some comments about the implementation of the attached main rule of yours:
1. It would be good to construct a filterset and thereby query the analytics upon interaction with the filters or paging grid rather than having these in with(). Becausee having these in with() causes the query evaluation and the filterset construction every time.
2. I would like to suggest to opt for a different approach for making of query. Configure a button (Name it as 'Search') and upon clicking this button perform the query analytics call with the filters as selected by user. This way we can restrict the costlier queries.
3. isnull has been used extensively. I would like to suggest to use rule!APN_isBlank (or an equivalent implementation) because isnull might evaluate to true even if a variable holds blank value in SAIL.
4. You might think of extending the rule and can make it much generic so that it can be reused much effectively. But please bear in mind that writing a rule as much as generic results in degradation of performance.