You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Browser App (Hosted external to Microsoft 365 platform)
Additional environment details
N/A
Expected or Desired Behavior
Get next on paged request from cache is not undefined
Observed Behavior
Get next on paged request from cache is undefined
Steps to Reproduce
Make a call to retrieve the top 20 user from pnp lib
/graph/users?$count=true&$top=20&$select=displayName%2cid%2cdepartment%2cjobTitle%2clocation%2cimageUrl%2cmail&$filter=accountEnabled+ne+false
Make a second call with same args to retrieve the request from the cache
In the result, next is not defined, but hasNext is true
/graph/users?$count=true&$top=20&$select=displayName%2cid%2cdepartment%2cjobTitle%2clocation%2cimageUrl%2cmail&$filter=accountEnabled+ne+false
In 3.21 version, next is defined but return the result from cached request.
I will try to push a minimum env to reproduce this behaviors
The text was updated successfully, but these errors were encountered:
Hi, Unfortunately we do not support pagination with caching. We did for a brief time with 3.21 but it had some negative side effects, so we had to revert it.
Major Version
3.x
Minor Version Number
24.0
Target environment
Browser App (Hosted external to Microsoft 365 platform)
Additional environment details
N/A
Expected or Desired Behavior
Get next on paged request from cache is not undefined
Observed Behavior
Get next on paged request from cache is undefined
![image](https://private-user-images.githubusercontent.com/2726957/330104244-36b23dbf-940e-4220-8f83-b1104dcda3e1.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjEyNDg2ODEsIm5iZiI6MTcyMTI0ODM4MSwicGF0aCI6Ii8yNzI2OTU3LzMzMDEwNDI0NC0zNmIyM2RiZi05NDBlLTQyMjAtOGY4My1iMTEwNGRjZGEzZTEucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDcxNyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA3MTdUMjAzMzAxWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NDNiYzk0YzUyMTJmMWQyZGUxZTM4Yjc2OTJhMmJmN2QxZDJhYzlhNGU1OGE2MDQ0ZTg5N2NkNTVjYTllZGZmZiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.iV8DjPdLFXIZBSLiRbSFcuemipiDGM2PK-iOsbUOP7s)
Steps to Reproduce
Make a call to retrieve the top 20 user from pnp lib
/graph/users?$count=true&$top=20&$select=displayName%2cid%2cdepartment%2cjobTitle%2clocation%2cimageUrl%2cmail&$filter=accountEnabled+ne+false
Make a second call with same args to retrieve the request from the cache
In the result, next is not defined, but hasNext is true
/graph/users?$count=true&$top=20&$select=displayName%2cid%2cdepartment%2cjobTitle%2clocation%2cimageUrl%2cmail&$filter=accountEnabled+ne+false
In 3.21 version, next is defined but return the result from cached request.
I will try to push a minimum env to reproduce this behaviors
The text was updated successfully, but these errors were encountered: