Loading

Missing Query References on Text Widgets in CRM Analytics Dashboards Deployed via Metadata API

Publiseringsdato: Jun 2, 2026
Beskrivelse

When a CRM Analytics Dashboard is deployed from a source org to a target org using Metadata API version 48 or lower, text widgets may not deploy correctly. Specifically, query references (values and step bindings) defined in the text widget in the source org are not transferred to the target org. This means dynamic values — such as aggregate totals displayed in a text widget — will appear as plain static text in the target org, showing the placeholder label (e.g., "Total Figures - [Confirmed]") but without the data binding.
This issue does not occur when deploying via Change Sets or Packaging, as both methods use the latest API version by default.


Example: A text widget configured in the source org to display a dynamic query reference like Total Figures - [Confirmed] will deploy to the target org without the values and step reference bindings, rendering the widget non-functional.

"parameters": {
"content": {
"displayTemplate": "Total Figures - [Confirmed]",

"values": {

"Confirmed": {

"field": "Confirmed",

"sourceType": "result",

"step": "lens_1"

}

}

},

"fontSize": 16,

"showActionMenu": true,

"textAlignment": "left",

"textColor": "#091A3E"

},

"type": "text"

}

>> Text Widget deployed in Target Org.

{

"parameters": {

"content": {

"displayTemplate": "Total Figures - [Confirmed]"

},

"fontSize": 16,

"showActionMenu": true,

"textAlignment": "left",

"textColor": "#091A3E"

},

"type": "text"

}

 

Løsning

This issue occurs because Metadata API version 48 and lower do not fully support the deployment of text widget query reference bindings in CRM Analytics Dashboards. When the API version is too old, the values block containing field and step references is silently dropped during deployment.
To resolve this issue, use the latest Metadata API version when deploying CRM Analytics Dashboards.
In your deployment configuration (e.g., package.xml or Salesforce CLI deploy command), specify the latest available API version. For example, if using Salesforce CLI:
In your .forceignore or sfdx-project.json, set sourceApiVersion to the latest supported API version (e.g., 59.0 or higher).
After updating the API version, redeploy the dashboard. The text widget query references, including the values and step bindings, will be preserved in the target org.
If you cannot immediately update the API version, use Change Sets or Packaging as an interim deployment method, as both use the latest API version automatically.

Knowledge-artikkelnummer

000389080

 
Laster
Salesforce Help | Article