Salesforce Known Issues

Certain global value set names are restricted

Metadata

Certain global value set names are restricted and will cause ant deployment errors.

In Review ·Reported By 92 ·Updated 3 days ago

Deployment which includes InstalledPackage fails if there are 2 records for the version and one of them is deprecated

API , Packaging , Metadata , Salesforce DX

Deployment which includes InstalledPackage fails if there are 2 records for the version and one of them is deprecated

Scheduled - Summer '20 ·Reported By 33 ·Updated Yesterday

Incorrect ordering of custom metadata picklist fields in SOQL

Metadata

Documentation shows that when using ORDER BY, picklist sorting is defined by the picklist sort determined during setup: https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql_select_orderby.htm However with this issue the order that is observed is different....

Scheduled - Summer '20 ·Reported By 19 ·Updated Yesterday

Global Picklist Values are not displayed on Record Types of Event object when retrieving the metadata

Metadata

Global Picklist Values are not displayed on Record Types of Event object when retrieving the metadata as consequence they can't be deployed to other Org.

In Review ·Reported By 18 ·Updated Yesterday

Metadata cannot be pulled after first authentication with Lightning for GMail

Metadata , Spring 18

Some customers have observed that after the first authentication of a user in Lightning for Email, the following error is thrown when pulling metadata using the Salesforce CLI. ERROR: Entity of type 'AuthProvider' named 'Lightning For Gmail' cannot be found.

In Review ·Reported By 13 ·Updated Yesterday

After "Translations" is installed via package, if another language is installed in the package upgrade, the language installed through the existing pa

API , Packaging , Platform , Metadata

After "Translations" is installed via a package, if another language is installed in the package upgrade, the language installed through the existing package is displayed as "beta". When this scenario happens "beta" is displayed because the package creation date is newer than the installation date....

In Review ·Reported By 1 ·Updated 2 days ago

Licensed Package Object returns "entity access is denied" for user with access to object but no license

Apex , Metadata , Lightning

When you install a licensed managed package in your organization from AppExchange, you purchase a certain number of licenses from the package developer or publisher. You can assign each license to a user within your organization If you utilize a lightning component with references to a an object from...

In Review ·Reported By 0 ·Updated 2 days ago

SFDX Pushing ContractStatus.standardValueSet to a fresh scratch org results in a error

Metadata , Lightning

When trying to push the standard value set for ContractStatus results in a error "force-app\main\default\standardValueSets\ContractStatus.standardValueSet-meta.xml Field: null is not a picklist"

In Review ·Reported By 32 ·Updated 4 days ago

Territory Management deployment fails when attempting to deploy changes with other entities

Service , Metadata

For example, Territory Management deployment fails when attempting to deploy territory changes if other entities like Account has a list view that is shared to the territory. Error: "cannot mix EntityObjects with different UddInfos within one transaction" Note: The issue occurs if the other entity...

In Review ·Reported By 8 ·Updated 4 days ago

Quick Action Deployment to namespaced org from non-namespaced org throws error.

Metadata

Deployment of a quick action from a non-namespace enabled org to a namespace enabled org throws error. The issue is specific to Quick Actions. This does not happen for any other type of deployment/objects.

In Review ·Reported By 1 ·Updated 4 days ago

1 to 10 of 259 | 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.