Salesforce Known Issues
Trailblazer Community

Known Issues · Salesforce DX

Error:Must specify a non-empty label for the CustomObject

Salesforce DX

"Must specify a non-empty label for the CustomObject" when deploying a custom field to the target org using Org development model.

In Review ·Reported By 152 ·Updated 3 days ago

Not Able to Convert Report Metadata to SFDX Format

Salesforce DX

Not able to convert the Report metadata to SFDX format when the report is in sub folder , for eg : unzipped folder >>> package.xml file + reports folders >>> parent folder >>> sub folder + metadata file >>> metadata file.

In Review ·Reported By 85 ·Updated Yesterday

Getting ERROR running force:source:push: Push failed when pushing appMenu of a community

Salesforce DX

After creating a community and pull the source you cannot push the community to a new scratch org because the push will fail the <appmenu> item.

In Review ·Reported By 86 ·Updated 2 days ago

Some commands seem to check the existence of the jwt keyfile when the access token is still valid

Salesforce DX

Some commands seem to check the existence of the jwtkeyfile when the access token is still valid

In Review ·Reported By 34 ·Updated 2 days ago

Entitlements Sample data being created in Spring '21 orgs

Service , Salesforce DX , Spring 21

Scratch Orgs created with Spring '21 release with "hasSampleData": false, will have the following sample data: an Entitlement record called "Sample Entitlement", which is associated with an Account called "Sample Account for Entitlements". It gets added as part of the Spring '21 feature

In Review ·Reported By 18 ·Updated Yesterday

SFDX - While using source:deploy command may come across an error "INVALID_SESSION_ID"

Salesforce DX

You may come across an error "INVALID_SESSION_ID" while using source:deploy command which is due to the token not getting refresh.

In Review ·Reported By 22 ·Updated 2 days ago

In Scratch org, custom field deletes on Standard Objects and Managed Custom objects are not being captured by sfdx force:source:pull

Metadata , Salesforce DX

sfdx force:source:pull does not report any changes if a custom field is deleted on a Standard Object or on a Managed Custom Object in a scratch org

In Review ·Reported By 19 ·Updated 2 days ago

Temporary folder "shape" not cleared out before `force:org:create` command executes

Salesforce DX

If you have multiple DX projects with varying configurations within each project's project-scratch-def.json files, the system temporary folder that the Salesforce CLI uses to define the shape of the scratch org can include definition files from previous force:org:create executions. This can lead to errors...

In Review ·Reported By 7 ·Updated 2 days ago

Unable to retrieve case feed filter using sfdx force:source:pull

Salesforce DX

sfdx force:source:pull is failing with the below error whenever case feed filter is present in the scratch org. "ERROR running force:source:pull: Invalid full name, Current Name: Test, Required Delimiter: . Invalid full name, Current Name: TEST1, Required Delimiter: ."

In Review ·Reported By 1 ·Updated 2 days ago

SFDX force:source:convert omits child metadata types containing a repeated API name

Salesforce DX

sfdx force:source:convert ignores child metadata types belonging to the same parent object which have the same API name. E.g. converting Opportunity BusinessProcess and Opportunity RecordType with the same API name will only include whichever is listed first in package.xml.

In Review ·Reported By 0 ·Updated 2 days ago

1 to 10 of 197 | Next

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.