Issue with Copilot Studio Integration with Salesforce – Incomplete Data Retrieval

(2) Share

Report

Posted on by tjohnk

Hi Team,
I’ve integrated Salesforce with Copilot Studio using the standard connector setup. However, I’m facing an issue where the agent is only returning partial data—specifically, it retrieves only a subset of the expected records or fields.
Could you please guide me on the following:

Are there specific attributes or permissions that need to be enabled in Salesforce for complete data visibility?
Is there any configuration in Copilot Studio (such as RBAC or filter settings) that might be limiting the response scope?
What are the best practices to ensure all relevant records (e.g., full Opportunity details, Sales figures, etc.) are fetched correctly?

Appreciate your help in resolving this.

Categories:

General topics

I have the same question (0)

All responses (3)

Answers (0)

Vahid Ghafarpour 781 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

You mean when log in as service account you can view the records but copilot couldn't?

Was this reply helpful? Yes No
tjohnk 7 on at

Like (0)

Report
Copy link

Link copied!

I was able to create a connector with Salesforce, and while it is pushing some data in the preview, the data appears to be encrypted or incomplete. As a result, the Copilot agent is not able to provide accurate or consistent responses. I have created the connection using my Active Directory (AD) account, but this account has restricted access to several datasets in Salesforce. Is there a specific privileged account we should be using for this integration? Or are there any particular RBAC (Role-Based Access Control) settings we need to configure in Salesforce for the user account being used to establish the connector?

Was this reply helpful? Yes No
Suggested answer

CU26110138-0 16 on at

Like (0)

Report
Copy link

Link copied!

You might want to double check the Salesforce object and field level permissions because partial record returns usually come from missing FLS or a profile not having visibility on related objects. I work at eesel AI and we run into a similar pattern when folks set up custom actions that fetch CRM data so it tends to come down to RBAC or an unexpected filter in the connector.

On the Copilot Studio side, I’d also look at any query constraints in the action definition since even a small filter or limit can quietly trim your results. Best practice is to test the raw SOQL query in Salesforce first so you know the connector is the thing limiting data rather than the source. Hope that helps you chase down the root cause.

Was this reply helpful? Yes No