Question

Pagination not working on grid field (version 23.3) for non-admin users

Forum|Forum|8 months ago
November 12, 2025
10 replies
0 views

Hi everyone,

I'm having an issue with a grid in my interface. When using System Administrator account, the data loads correctly when the next page button is clicked.

But when using a Basic User account, the grid shows the same first-page data, and the paging control is not updating as well.

I checked all related objects used in the code, all have Viewer access for the Basic User's group.

Code snippet:

a!gridField_23r3(

data: local!grid.data,

pageSize: 5,

pagingSaveInto: fv!pagingInfo,

validations: {}

)

Thanks in advance for any insights!

harshas2775

As long as the user can see page 1 there is no configuration that can disable/hide the next page data. So it is not due to any configuration or security issues. Suggest you to have the basic user test from a different browser or check the same grid after clearing cache/cookies.
Also investigate if a specific user is facing this or all basic users. Depending on the users affected further investigation can be done. Let us know how it goes/ what you find.

R

ronalynm4283Author

I tested this using my basic user account on a different browser and cleared the cache, but the issue still occurs. I don’t experience this on my system admin account, and I also checked with other system admins who confirmed everything works fine for them. Based on this, it seems the issue is specific to basic accounts.

harshas2775

Try creating one more basic user account and verify if the behavior is same.

shubhama926776

Can you check if the Basic User has Viewer permissions on the Data Store (not just the CDT/Entity/Record)? Also, does your query have any security filters or record-level security that might be limiting what Basic Users can see?

https://docs.appian.com/suite/help/25.3/Data_Stores.html#security

Also, Does local!grid use fv!pagingInfo in the query's pagingInfo parameter?

R

ronalynm4283Author

I’ve checked the data store permissions, and the basic user account I’m using currently has viewer access. For the query, I didn’t find any security filters or additional security measures applied. Regarding Local!grid, it doesn’t use fv!pagingInfo in the query.

stefanhelzle0001

I am pretty sure this line makes no sense:

pagingSaveInto: fv!pagingInfo,

This should be a local used to perform paging in the query.

R

ronalynm4283Author

Thank you for sharing this insight. I’ll work on updating the code and will post an update in this thread once the issue is resolved.

mikes0011

Brainy

Checking in to agree with Harsha - nothing in terms of account-type security would generally allow a given user to load the first page of a grid but then fail to be able to see the second page. I'm guessing that if you fix the issue Stefan pointed out - the "pagingSaveInto" currently being something nonsensical - that might smoothe over internal issues in such a way that the error goes away (i suppose there's a chance that the error it gives basic users is somehow not as strong when seen by an admin, though if so I can't imagine why or how).

H

harshitag0021

Hi,

Instead of using fv!pagingInfo, try to use local!pagingInfo with startIndex and batchsize as required. Then you can use the local!pagingInfo into pagingSaveInto.

for example: -

local!pagingInfo: a!pagingInfo(startIndex: 1, batchSize: 10)

I hope this will resolve the query.

Sign up

Login with SSO

Login to the community

Login with SSO