Understanding the Issue

We have seen teams running into this issue when trying to set up Data Cloud on Agentforce, and it’s mainly due to the namespace restrictions in Scratch orgs.

When clients hit this roadblock, they usually try various methods to resolve the issue, including checking cases, questions, known issues, and even trying workarounds, but to no avail.

Technical Explanation

The root cause of this issue lies in the fact that Agentforce features are not fully compatible with unnamespaced Scratch orgs, which are required for Data Cloud to work.

Data Cloud requires an unnamespaced Scratch org to function, but many Agentforce features are not compatible with this setup, leading to a deadlock situation.

This incompatibility leads to a situation where developers cannot use Data Cloud on Agentforce, resulting in frustration and wasted time.

Possible Solutions

To overcome this issue, developers can try using a different approach, such as using a namespaced Scratch org for development and testing, and then deploying the solution to a production org.

Another possible solution is to use Apex code to deploy Data Cloud solutions, which can provide more flexibility and control over the deployment process.

DataCloudDeployment.cls

public class DataCloudDeployment {    public static void deployDataCloud() {        // Apex code to deploy Data Cloud solution    }}

Best Practices

To avoid running into this issue, it’s essential to plan carefully and consider the namespace restrictions when setting up Data Cloud on Agentforce.

Heads up: Make sure to test your Data Cloud solution thoroughly in a development environment before deploying it to production.

Checklist for Enabling Data Cloud on Agentforce

• Use a namespaced Scratch org for development and testing
• Deploy Data Cloud solutions using Apex code
• Test your solution thoroughly in a development environment
• Consider using a different approach, such as using a production org for deployment
• Plan carefully and consider namespace restrictions when setting up Data Cloud on Agentforce

What is the main cause of the issue with Data Cloud on Agentforce?

The main cause is the incompatibility between Agentforce features and unnamespaced Scratch orgs required for Data Cloud.

Can I use Apex code to deploy Data Cloud solutions?

Yes, using Apex code can provide more flexibility and control over the deployment process.

What are the best practices for enabling Data Cloud on Agentforce?

Plan carefully, consider namespace restrictions, and test your solution thoroughly in a development environment.

What are the consequences of not using a namespaced Scratch org for development and testing?

Not using a namespaced Scratch org can lead to compatibility issues and wasted time.