Inform user of sparsely-populated results when retrieving profiles/permission sets in isolation

[Marius Blajevschi]

Hi,

I'm pulling profiles metadata into my project and it seems that the metadata that I get back does not contain any standard object permissions (eg. Entitlements).

Can IC2 pull standard object permissions when retrieving profiles? Is that something that SF does not provide in profiles metadata?

Thanks

[Scott Wells]

Let me refer you to this thread on the topic of profile/permission set retrieval:

https://groups.google.com/a/illuminatedcloud.com/forum/?utm_medium=email&utm_source=footer#!msg/qanda/IX3jV72n0qk/2N4xsEECBwAJ

You just need to retrieve the things those files authorize in the same request and they'll be populated appropriately. It's just a quirk of the way that those metadata types work during retrieval. Let me know if that doesn't resolve the issue for you.

[Scott Wells]

Resolving, but if you have any issues after reading the linked discussion, feel free to reopen.

[Marius Blajevschi]

Thanks Scott,

yeah, I see them now. I was not aware of this.

[Scott Wells]

Glad to hear. I've considered adding a warning when a user tries to retrieve just these two metadata types given the frequency of this question and the understandable confusion around how this works in Salesforce. I'll add that to my list.

[Marius Blajevschi]

That sounds like a good idea. Thanks Scott!

[Scott Wells]

Re-opening to track progress on a warning message when retrieving profiles/permission sets in isolation.

[René Görgens]

I solved a similar issue by doing a Refresh Metadata on profiles, then the project’s metadata are taken into account in my experience.

[Scott Wells]

This was actually addressed way back in 2.2.1.5:

https://illuminatedcloud.blogspot.com/2022/04/2215-release-notes.html

Here's the relevant excerpt:

Added a warning prompt when the user tries to retrieve profile and/or permission set metadata in isolation from a non-source-tracked organization. Such a retrieval will result in sparsely-populated XML documents that do not include authorizations of Apex, Visualforce, SObjects, or SObject fields. To retrieve complete profiles/permission sets, all authorized metadata objects must be retrieved in the same request. This prompt can be disabled if desired.

I should have resolved this at the time but I suppose I didn't find the corresponding item in the issue tracker.