CPQ is one of the most powerful — and most feared — corners of the Salesforce platform. Between nested product rules, price rules, and bundle logic, even seasoned admins often can't say with confidence what a single change will break downstream.

With dx0, that changes. Now everyone in your org — not just your Salesforce architects — can see exactly how CPQ is configured and understand the ripple effects of any change before it hits your go-to-market engine.

No more guessing. No more "let's just test it in prod and hope."

Note: This requires "Agentic Data Access" to be enabled in your account. Reach out to help@happysoup.io for details. 

We just expanded the org index to include Profiles, Roles, and Dashboards — unlocking much richer answers about how access is really configured across your Salesforce org.

You can now ask dx0 questions like:

• Who can see or do what in this org?
• How is access structured across roles and profiles?
• Where are risky or inconsistent access patterns showing up?

One quick setup note

Dashboards are now supported, but they’re optional and need to be turned on in: Connected Orgs → Index Configuration (Include Reports and Dashboards).

Your Salesforce metadata only tells part of the story. Now dx0 understands your business context too.

With Context, you can bring the knowledge that lives in documents, spreadsheets, screenshots directly into every conversation.

You can now:

• Add Context Notes for acronyms, business rules, historical decisions, naming conventions, or reusable user story templates.
• Upload files such as user stories, requirements, CSVs, screenshots, and other supporting documents.
• Combine Salesforce metadata + business context + uploaded files in a single prompt for dramatically better answers.

Need to know whether a new set of requirements impacts a field? dx0 can analyze the requirements document against your Salesforce metadata. Want user stories generated in your company's standard format? Just add your template as Context and dx0 will follow it automatically.

And yes, attachments are finally here. Simply drag and drop your files into the conversation.

Watch the video below to see Context in action.

Your Salesforce reports have always been a bit of a blind spot. Not anymore.

You can now include Reports in your org index, which unlocks a whole new layer of visibility:

• Field usage, finally complete. See where a field is actually used in reports, not just in code and automation. No more "safe to delete?" guesswork.
• Ask the AI agent the real questions. "Which reports are duplicates?", "Can we consolidate these sales reports?", "What reports still reference this legacy field?" — the agent can now dig into your report definitions and answer.

A quick heads-up

Reports can number in the thousands and are heavy to retrieve, so we've kept this off by default to keep everyone's indexing fast and lean. When you're ready for the deeper view, flip it on:

Connected org → Details → Index Configuration → Include Reports

It'll be picked up on the next index refresh. Turn it off any time.

You can now choose whether dx0 can see CRM data

Metadata got us far. Dependency maps, impact analysis, org intelligence — all built on metadata alone. But there's a whole category of Salesforce problems that metadata can't solve, and we've been hearing about them.

Why isn't this lead assignment rule firing? Why is the duplicate rule letting records through? What's actually happening in production?

Now the agent can go find out.

How to get it

Data access is off by default — reach out to us and we'll enable it on our end. From there, you switch it on in your account settings and you're live. The agent decides when a data query is actually needed; you don't have to prompt it.

On privacy

Before anything reaches the LLM, it goes through the dx0 trust layer. PII gets stripped on our servers — emails, dates of birth, ID numbers, gone before the model ever sees them. The agent knows this and won't even attempt to surface that data if you ask. It's not a setting you configure. It's just how it works.

If you want it enabled, get in touch.

dx0 now index more metadata types which power the AI agent's capabilities to understand your org. This new update includes:

- Permission Sets / Groups

- Global Picklists / Value Sets

- Workflows and their subtypes (email alert, field update, etc.)

- Approval processes

Additionally, we've enhanced the index UI so that it's always clear which metadata types are available and when they were last indexed.

You can now access your bills, payment methods and invoices from your settings page. Just click your avatar > Billing.

The dx0 search functionality, available both on the agent and the user interface, has been significantly enhanced. Users can now conduct searches within specific folders, utilize regular expressions, and perform negative searches. The screenshot below illustrates how to identify all flows that do not include the term "CustomerPriority." This capability can assist in locating various elements within your organization, such as specific Apex patterns, flows containing particular formulas, and hardcoded user IDs within flows. Enjoy!

We've shipped prompt templates to make it easier to understand the art of possible. You can do a whole audit of the org in seconds, find dependencies, create UML diagrams from processes, and much more.

You can now search your entire org at your own pace using the "Search" functionality on the sidebar. Search for hardcoded email addresses, User Ids, picklist values or anything else.