#Trailblazer Community Questions3 327 personnes en discutent

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.

Yes, the password on an Outlook PST can be removed or reset without changing the emails and folders stored inside the file. If you have forgotten the PST password, an expert PST password recovery tool can help you remove the Outlook file password effortlessly. 

is a helpful solution for this. It can remove an existing PST password or set a new one, supports both ANSI and Unicode PST files, and works without requiring Microsoft Outlook to be installed. It also provides a folder mode when you need to process multiple PST files. 

Before making any changes, keep a backup of the original .pst file. Also, password removal is different from PST corruption repair, so a damaged PST may require a separate recovery method.

Hi @JEET Patel

This looks more like a  Data Governance access issue than a problem with your Data Stream or Data Model. 

Salesforce has a known scenario where Data Explorer shows: 

table "xxxx__dll" does not exist 

when the user doesn’t have the required Data Governance policy access to that Data Lake Object. 

I would check these first:

1. Go to Data Cloud / Data 360 → Data Governance → Policies.
2. Check whether the All Data Access Ruleset policy is available.
3. Make sure your user is assigned a policy that gives access to the affected DLO, such as Employee_Salary_Data__dll.
4. After updating the policy, refresh the Data Stream and try Data Explorer again.

Also check the Data Stream Refresh History and confirm that records are actually being ingested into the DLO without failures. 

I wouldn’t keep deleting and recreating Data Streams at this point, because if the issue is Data Governance access, recreating the DLO will not fix the underlying permission/policy problem. 

Regarding disabling Data Cloud, I would avoid doing that just for this issue. First check the governance policy. If the correct policy is already assigned and the error still continues, then I would raise a Salesforce Support case with the TraceId and Query ID from the error. 

Based on the error you shared, Data Governance policy access would be my first check.

Thank you,

Venkat Yadav.

Hi @Abhay Ram Solanki

This looks like Trailhead is unable to create or update its test Account and Opportunity records in your org. 

You can try these checks:

1. Create one Account and one Opportunity manually and confirm they save without any error.
2. Check if any Validation Rules are blocking the records.
3. Check for required custom fields on Account or Opportunity.
4. Check if any Flow, Trigger, or other automation is failing during record creation/update.
5. Once manual create/update is working fine, tryCheck Challenge again.
6. If the issue still continues, try the challenge in a fresh Trailhead Playground.

If the same error happens even in a clean playground, then it may be a Trailhead verification issue and raising a Trailhead Support case would be the better option. 

Thank you, 

Venkat Yadav.

Hi @Rodrigo Sanchez

I think your overall approach is correct, but the issue may be with streamKnowledgeSearch itself.

1. before_reasoning can run actions deterministically, so using run there is a valid pattern.
2. In your case, AnswerQuestionsWithKnowledge uses:

standardInvocableAction://streamKnowledgeSearch 

Because this is a streaming action, it looks like it may not work properly when called directly from before_reasoning. The fact that it saves successfully but fails only at runtime also points in that direction. 

1. I could not find clear Salesforce documentation saying that streamKnowledgeSearch is supported inside before_reasoning, so I would avoid assuming it is supported there.
2. For the user message, the current documented variable is:

@system_variables.user_input

If your org says this variable does not exist, it could be related to the AgentScript version or feature rollout in that org. 

For now, I would keep the Knowledge action under reasoning.actions and make the instructions as strict as possible. 

If you really need the Knowledge search to run every time before reasoning, I would raise a Salesforce Support case and specifically ask whether streamKnowledgeSearch supports deterministic execution inside before_reasoning. 

The interesting part here is that the script passes validation but fails only at runtime, so it may be a current platform limitation rather than an issue with your syntax. 

Thank you, 

Venkat Yadav.

@Nagaraju Vadlamudi

Sendlog DE will only show or add records when a send has occurred. 

It is not recommended to update Sendlog DE in any other way. (i.e. using SQL, import etc) 

As you already have the ControlGroup "true" in the source DE, you can apply a filter and run it via automation to review the Control Group audience.  

Additionally, as you have highlighted that you are using "Random Split" in Journey for 10% control group exclusion, I assume that the number of records being processed is >1000, otherwise Random Split may work unexpectedly. See this article for better understanding -