#Data Cloud69 diskutieren mit

Resolved by creating a new policy in Data Governance

Hi , 

Deactivating the Business Unit is not sufficient. The Data Space still appears to have a dependency on a Business Unit that contains one or more CMS Workspaces. Check the Marketing Cloud Business Unit for existing CMS Workspaces and remove any remaining Data Space mappings. Also verify whether any deployed Data Kits are still associated with the Data Space before attempting deletion again. 

Hi , 

This looks similar to a previously reported issue. In that case, the required DMO/Data Stream dependencies had not been created yet. Please verify that all prerequisite steps in the module were completed successfully before creating the Calculated Insight. 

Hi @Alyssa Jenson , I put Agentforce Coworker

to work on a single account and saved serious time. From one screen, I compared two promotions, checked the customer sentiment score and updated contact details instantly.  

It’s a game‑changer for efficiency and customer experience — all in just a few clicks! 

Link:

Hello, 

For a local handyman or home-service website, I’d keep the design simple, clean, and action-focused—visitors should immediately understand what services you offer, where you serve, and how to contact/book you. Use a clear homepage structure with a strong hero section, a short list of key services, reviews, before/after photos, service areas, pricing or “get a quote” CTA, and a simple contact section. Keep the colors consistent (2–3 main colors), use plenty of whitespace, and make buttons like Call Now / Get a Quote / Book a Service easy to spot, especially on mobile. Before calling the design finished, I’d test it on different phone sizes, check loading speed, make sure every link and form works, confirm the phone number is clickable, check spelling/content, add trust signals like reviews and licenses/insurance if applicable, and make sure a first-time visitor can figure out what you do, where you work, and how to hire you within a few seconds. Hope this helps!

Hi @Ionuț Buzatu

- It seems like a  Data Kit/deployment limitation or Salesforce issue 

• Check the deployment logs for the detailed error.
•  Verify SFMC connector authorization in the target org. 
•  If individual SFMC streams still fail, raise it with Salesforce Support as a Data Cloud Data Kit deployment issue. 

Hi Shivani, 

This is a known issue tied to the data stream/datasource mapping not being fully processed yet in fresh Trailhead playgrounds, not something wrong on your end. 

A few things to check and try, in order: 

1. Go to Data Cloud > Data Streams and find the stream tied to Lead_Data_for_Training. Check its Last Refreshed status, if it's never run or is still processing, wait for it to complete, then retry Model Builder. 

2. Go to Data Cloud > Data Model, search for Lead_Data_for_Training, and confirm it has a Category set and is actually mapped to a data source under the default Data Space. If the mapping is blank, that's the root cause, the DMO exists but has no linked datasource yet. 

3. If your org has more than one Data Space, switch to a different one and back to default. This forces Model Builder to re-resolve the datasource reference and has fixed this exact error for others. 

4. Hard refresh Model Builder (or open in incognito), since this screen sometimes caches a stale data model list from before the stream finished processing. 

5. If it's still broken, the official Trailhead module itself documents a fallback for this exact scenario: 

"If you can't find the Lead Data for Training DMO, use the Lead_Home DMO for the rest of this badge." 

Source (official Trailhead unit):

So go to the Data Streams tab, click on the Lead_Home data stream, and continue the badge using Lead_Home instead. This is Salesforce's own sanctioned workaround, not a hack. 

6. If none of that clears it, it's likely a playground provisioning issue on Salesforce's side. Use "Get Help" > "Report an Issue" directly on the module page so the Trailhead ops team can look at your specific playground. 

Let me know which step gets you past it.

Two things gate a Calculated Insight from showing up in a segment on Unified Individual, and you are likely hitting both: 

1. The Unified Individual primary key has to be a dimension in the CI. For a CI to surface when you segment on Unified Individual, the segment object's key (the Unified Individual ssot id) must be one of the CI dimensions. Right now you group by Rental Home Customer aliased as Individual Id, which is the source Customer field, not the Unified Individual id — so Data Cloud cannot relate the metric back to the individuals in the segment. Return the Unified Individual id (the ssot id from UnifiedssotIndividual) as the dimension instead of, or alongside, the Customer field. 

2. The CI must be run after you build or edit it. A new CI stays inactive or processing until a full run finishes, and it only lands in the segmentation attribute library once it succeeds. Open the Calculated Insights tab, check the status, and run it if it is not Active or Success — then give the segment canvas a few minutes to sync the new attribute. 

Fix the dimension first (that is the usual cause), re-run, and it should appear. 

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