Why can a Purview scan of Salesforce show incomplete / inconsistent data?

Juan Della Torre 20 Reputation points
2024-09-30T18:31:24.9366667+00:00

A scan of Salesforce objects in Purview shows schemas from objects as different than what is defined in Salesforce: in the example below, object shows 8 fields in Salesforce and 13 in Purview, and some fields in Salesforce are not showing in the schemas in Purview.

Hoping to get ideas of what could be wrong or how to troubleshoot.

SF OBJECT

Purview Scan

Microsoft Purview
Microsoft Purview
A Microsoft data governance service that helps manage and govern on-premises, multicloud, and software-as-a-service data. Previously known as Azure Purview.
1,164 questions
{count} votes

Accepted answer
  1. Ganesh Gurram 555 Reputation points Microsoft Vendor
    2024-10-04T04:10:16.1966667+00:00

    @Juan Della Torre - I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to accept the answer.

    Ask: Why can a Purview scan of Salesforce show incomplete / inconsistent data?

    Solution: The issue is resolved. During troubleshooting sessions, we figured that the problem was the way Permission Sets were defined in Salesforce. We tested a change that was successful and will now implement across.

    If I missed anything please let me know and I'd be happy to add it to my answer, or feel free to comment below with any additional information.

    If you have any other questions, please let me know. Thank you again for your time and patience throughout this issue.


    Please don’t forget to Accept Answer and Yes for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members.

    1 person found this answer helpful.
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Juan Della Torre 20 Reputation points
    2024-10-03T12:57:15.2966667+00:00

    During troubleshooting sessions we figured that the problem was the way Permission Sets were defined in Salesforce. We tested a change that was successful and will now implement accross.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.