#Data Cloud73 discutindo

@Liliana Camargo that crawler reads the HTML the server returns. It does not run the page JavaScript, so a section that only exists after the browser executes a script is not in the fetch. That is a limitation of the connector, not a setting you missed.

The reliable fix is to put that content in the first HTML response. Server-side render it, or give the crawler a prerendered URL. If the site already has an API, a CMS export, or a PDF, ingest that instead of the rendered page.

I would not keep tuning the crawler and hoping it executes the script. It will not.

@Clinton Fernandes

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.

Hi @Mounika Aithagoni

You would decide based on these core points:

1. Data Ingestion: Best for data transformation, identity resolution, and unified customer profiles.
2. Zero Copy: Best for accessing large external datasets without duplicating data.
3. Real-Time Data: Zero Copy with live queries can provide access to the latest source data.
4. Performance: Ingestion is useful for frequently processed data. Zero Copy depends on external query performance.
5. Cost: Compare ingestion and storage costs against Zero Copy query costs.
6. Security: Consider data governance, access permissions, and compliance.

My suggestion: Use a hybrid approach based on business requirements. Always validate performance, data freshness, and cost through a POC before finalizing.

Hello @Antonio Bianco Ignacio

You can try the following options:

•  Clear the browser cache -> log out & log in again, then check the challenge
•  Check your challenge in incognito mode/Private Window or a different browser. 
•  If you still face the same error, delete and recreate it again, then try to check your challenge, or I recommend that you create a new playground and complete this task there.
•  https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000C4t16SAB
•  https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000JeMjKSAV

Hi Venkata, 

Best answer to your core ask: use Data Cloud's native Writeback feature (a Batch Transform/Data Transform with a Salesforce Object as the target), not a scheduled Flow. This directly solves your problem — it reads the entire DMO (all existing + new records) on a schedule, writes to CRM via Upsert matched on your key field (account_id), and isn't triggered by create/update events at all, so backfill and ongoing sync use the exact same mechanism. 

How to set it up: 

1. Data Cloud → Data Transforms → create a Batch Transform (or use an existing one) sourced from your DMO 

2. In the Writeback/target configuration: Target Type = Salesforce Object, select your account_data custom object 

3. Action Type = Upsert, map account_id as the matching key, map your other fields (e.g., model) 

4. Schedule the transform to run as often as needed (this is a genuine scheduled batch job on Data Cloud's side, not something bound by Flow governor limits) 

This directly answers your numbered questions: 

1. Recommended way: Writeback via Data Transform (above), not a flow-based approach, for anything beyond small volumes. 

2. Copy Field enrichment: works, but it's designed for real-time, per-record enrichment onto existing CRM records as they're viewed/queried — not a backfill mechanism for records that already exist and won't re-trigger. Not the right tool for "sync everything now." 

3. Scheduled Flow reading DMO at scale: it'll work for low volume, but Flow's Get Records/Update Records has standard governor limits (SOQL rows, DML rows per transaction) — it's not built for bulk DMO-to-CRM sync the way a Data Transform writeback is. Expect it to struggle or need batching logic once you're past a few thousand records. 

4. Correct — Copy Field enrichment is standard-objects-only. But Writeback via Data Transform is not restricted that way: Salesforce Object as Target Object explicitly supports custom objects, which is exactly your account_data case. 

For the one-time backfill specifically: you don't need Data Loader as a separate step — just run the Writeback transform once manually (on demand) for the backfill, then put it on a schedule for ongoing sync. Same mechanism handles both. 

Reference:

Hi @Lokesh Adhikari

This is happening because deactivating the Marketing Cloud Business Unit does not automatically remove its mapping with the Data Space. 

From the screenshot, the Data Space CA still has a dependency on the Business Unit sfmc_10984445, so Salesforce is blocking the deletion. 

You can try the below steps:

1. Go to Data Cloud / Data 360.
2. Open the Marketing Cloud connection / Data Stream setup.
3. Check the Business Unit to Data Space mapping.
4. Find sfmc_10984445.
5. Remove the mapping from the CA Data Space, or map it to another Data Space if required.
6. Save the changes.
7. Check if there are any remaining DLO, DMO, Data Kit, or other dependencies.
8. Try deleting the CA Data Space again.

Deactivating the Business Unit alone will not remove the dependency. 

Based on the error, I would first remove the Business Unit → Data Space mapping and then retry the deletion. 

Thank You, 

Venkat Yadav.