Hi All,
I'm using an LWC that displays large result sets through pagination (e.g. 50 records per page from 1800+ records). While users can load the data successfully on click of Next button, Agentforce doesn't seem to have access to the records loaded within the LWC. For example, after viewing the results, a user may ask Agentforce to "show accounts with premiums between $1M and $2M," "group results by State Name" or "filter the displayed dataset further."
Since the data appears to remain on the client side (LWC), Agentforce cannot analyze or refine the records already shown in the component. Is there a recommended pattern for exposing LWC loaded datasets to Agentforce context so the agent can conversationally filter, group, summarize, and refine those results, especially for datasets containing hundreds or thousands of records?
#Agentforce
LWC pagination and Agentforce are separate contexts, so records loaded into the component aren’t automatically available to Agentforce. The better approach is to expose the underlying dataset through an Apex action or Agentforce action, allowing the agent to query, filter, and group the full result set rather than relying on what the LWC currently displays. This is similar to how move out cleaning services rely on the underlying full property rather than just visible areas.
