Loading

CRM Analytics Component Parameter Not Populated After Deployment Using package.xml

Veröffentlichungsdatum: Jul 7, 2026
Beschreibung

Problem: CRM Analytics Component Parameter Displays Name Instead of Value After Deployment

When a CRM Analytics (CRMA) dashboard component is deployed to a target environment using a package.xml manifest, the component parameter displays the parameter name instead of the resolved query value the first time the dashboard is opened.
Editing the dashboard runs the query and temporarily populates the parameter correctly, but saving the dashboard does not retain the value. Opening and saving the individual component is a short-term workaround, but does not permanently resolve the issue.
This behavior occurs because the WaveXMD metadata type — which stores the extended metadata (XMD) for CRM Analytics components, including parameter value bindings — is missing from the deployment package by default.

Lösung

Resolution: Include WaveComponent and WaveXMD in the Deployment Package

This issue occurs because the WaveXMD metadata type, which stores the extended metadata (XMD) for CRM Analytics components including parameter bindings, is not included in the deployment package by default. Including both WaveComponent and WaveXMD in the package.xml manifest resolves the parameter population issue permanently.

Step 1: Update the package.xml Manifest File

Open the package.xml manifest file used for deployment. Add two separate type entries for the component — one for WaveComponent and one for WaveXMD — each specifying the CRM Analytics component name as the member. The WaveComponent entry covers the component definition, and the WaveXMD entry covers the extended metadata that controls parameter value bindings.

Step 2: Deploy Using the Updated Manifest

Deploy the components using the updated manifest file that now includes both the WaveComponent and WaveXMD metadata types. After deployment, open the dashboard in the target environment and verify that the component parameter displays the correct query value without requiring any editing.

Alternative: Deploy Using a Change Set

As an alternative to a manifest-based deployment, deploy the component using a change set. When building the change set, ensure that all component dependencies are included — specifically, confirm that both the WaveComponent and WaveXMD entries for the component appear in the change set before deploying.

Nummer des Knowledge-Artikels

005299576

 
Laden
Salesforce Help | Article