Hi Trailblazers,
I am currently working on an architecture pattern in Salesforce Data Cloud to sync data to Service Cloud using Data Actions tied to Platform Events.
Here is the setup and the challenge I'm facing:
Use Case: A Data Transform runs hourly to process data and send it from Data Cloud to Service Cloud via Data Action (Platform Events).
The Problem: On the initial run, the transform processes a 4 million record backlog. Attempting to publish 4M records via Platform Events simultaneously will hit standard platform limits (hourly publishing and daily delivery allocations).
Goal: Avoid hitting event bus rate limits during the initial load while keeping the recurring hourly sync real-time and efficient.
#Data Cloud
From an architecture perspective, I’d separate record access, field visibility, and reporting permissions. Salesforce FLS applies across the platform, so allowing users to read financial fields on Account also has implications for reports and list views.
I’d start with least-privilege access, report folder permissions, and restrictions on report creation and data export. If the requirement is to hide the same fields in reports while retaining record-level visibility, standard configuration has limitations, and a custom UI may be worth evaluating for specific use cases.
