#Trailhead Challenges토론 중인 항목 1,697개

@Kiran Kharade - Vashi Integrated Solution Ltd depends on what you mean by "view CPQ report data."

If the users need to open reports that are built directly on CPQ objects such as CPQ Quotes, Quote Lines, Subscriptions, Contracts, or other SBQQ__ package objects, then report folder access alone will not solve it. They still need the required object, field, record, and package/license access behind those reports. Salesforce’s CPQ permissions guidance states that CPQ access is controlled through CPQ licenses and package-specific permission sets (Get Started with Salesforce CPQ Permissions)

Recommended option is to give CPQ licenses only to users who need direct access to CPQ records, then create a restricted read-only permission model for them as much as CPQ allows.

For non-CPQ users, the safer approach is not to expose the CPQ objects directly. Create a separate reporting layer, such as a custom reporting object, summary object, scheduled snapshot, CRM Analytics dataset, or exported BI dataset, containing only the fields they are allowed to see. Then report on that object/dataset instead of the live CPQ package objects. That gives visibility without opening full CPQ record access.

A dashboard with a running user may work for high-level summary visibility, but it should not be treated as a clean replacement for proper CPQ licensing or record access, especially if users need to drill into report details. 

My recommendation is: direct CPQ report access usually requires CPQ access. For non-CPQ users, create a controlled summary/reporting layer and expose only the required CPQ data there. 

Hi @Angel Corpuz

In Salesforce Marketing Cloud, while you can technically use CC, it is not recommended for large datasets. CC is meant for limited or internal use and can create deliverability, tracking, and privacy issues at scale. The best practice is to include all recipients in a sendable Data Extension and send personalized emails directly, which ensures better performance, accurate reporting, and compliance. 

Yes, this is possible in Tableau, but there is one important limitation: if each sales representative is restricted by user-level security to see only their own data, Tableau cannot calculate a true rank across all representatives inside that same filtered view, because the other representatives are removed before the rank is calculated. 

The usual solution is to calculate the ranking before row-level security is applied. For example: 

1. Create a separate aggregated table or data source that stores each representative’s sales growth and assigned points.
2. Calculate the rank in that source using all representatives’ data.
3. Then use user-based filtering so each logged-in representative only sees their own final rank/points row.

Another option is to calculate the ranking in the database or ETL layer and expose only: 

• Representative name/login
• Growth %
• Rank
• Points

Then, in Tableau, filter by the logged-in user using USERNAME().

So the key idea is: 

Rank must be precomputed on the full dataset, then Tableau can securely show only the logged-in user’s own position.

Hi @Amrita Sinha

,  This usually happens if the dashboard references reports, datasets, or folders with restricted permissions, or if a recent refresh broke references. Check that you have create/modify access on the folder, all underlying reports exist, and datasets are accessible. If cloning still fails, try saving a copy with a new name or recreate the dashboard using the existing components.  

Mark if it is useful...