#Trailhead토론 중인 항목 577개

Hi Arjun, the usual cause is that field-level security is additive: read-only on one profile or permission set gets overridden by Edit access the user has somewhere else. 

1. Effective FLS = the MOST permissive across the user's profile + EVERY assigned permission set and permission set group. Disabling Edit on just one of them means nothing if another still grants it. Open the field's View Field Accessibility for that user (or check each assigned permission set and group) and confirm none still grants Edit. This is by far the most common reason a field you set to read-only stays editable. 

2. Paths that bypass the read-only page setting entirely: 

- Flows and custom Apex or LWC run in system mode and ignore FLS and layout read-only unless they explicitly enforce it. If Total Price Change is edited via a screen flow, a flow-based quick action, or a custom component, that path will not honor your read-only. 

- If you are editing inside the CPQ Quote Line Editor (managed package), it renders fields from its own field set, not the Lightning Record Page, so the record-page read-only does not apply there. 

So first confirm FLS is read-only across ALL the user's permission sets and groups, then check whether the edit is happening in a flow, custom component, or the CPQ line editor rather than the standard record page. 

if this helps, please mark it as the Best Answer so it helps the next person, thanks 🙂

Good question, and the key distinction is that it is a license-level limit, not a permission one. A permission set can only grant access to objects your license already includes, it cannot add objects the license leaves out. 

The Salesforce Integration (API-only) license deliberately omits full standard-CRM-object access. In practice, when you build the permission set for that user, the standard objects Marketo needs (Account, Contact, Lead, Account Contact Relationship) are not even available to grant, because the license does not include them. So the permission set looks complete, but the user still cannot query those objects and the sync fails on exactly those (Account Contact Relationship is usually the first casualty). 

Marketo's sync reads the whole standard object model (Leads, Contacts, Accounts, Opportunities, Campaigns, Campaign Members and their relationships), so it needs a license tier that actually includes all of them. That is why Adobe specifies User License Salesforce plus API Enabled, it is the only combination that exposes the full set. The integration license is not a cheaper full license, it is a different tier with those objects gated out. 

if this helps, please mark it as the Best Answer so it helps the next person, thanks 🙂

Hi @Muhammad Arsalan

There was a post about the same error yesterday as well. The ID for this package has been changed several times in the past. 

I encourage you to get help from the Trailhead support team. 

https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000JeXW9

I tried it too, and it certainly won't install.

Build this custom report type is the easiest way.  

Then add a filter on report name and you can easily find which dashboard(s) are referencing the report you want to delete.  

If you are still getting the error, then the report is likely stored in a private folder, so follow this guide: