Metadata deployments (change sets or package) show successful without error message but the expected components are not deployed

Apex , AppExchange , Packaging , Metadata , User Interface , Eclipse IDE , Change Sets

Metadata deployments via change sets or packages may show that the deployment was successful without any error messages. However, upon checking - the expected components are not actually deployed or present in the target org. This may occur if your change set contains Apex and requires the deploy...

In Review ·Reported By 22 ·Updated 8 days ago

Deployment error when deploying sharing rules together with queues on the same package

Packaging , Metadata , Eclipse IDE

When deploying sharing rules and queues together the following error can occurr error: "sharedFrom not allowed:queue - [QueueName]", when using ANT or the IDE.

No Fix ·Reported By 44 ·Updated 11 days ago

Translation Labels are saved to incorrect page layout sections if there are duplicate section names

API , Metadata , Eclipse IDE

Deploying translated labels for page layout section is saved to incorrect section in presence of layout sections with duplicate names.

In Review ·Reported By 11 ·Updated 11 days ago

Converting the package into DX format via the force:mdapi:convert command results in "Invalid or unsupported zip format. no EDS header found"

Packaging , Metadata , Salesforce DX

Converting the package into DX format via the force:mdapi:convert command results in "Invalid or unsupported zip format. no EDS header found"

In Review ·Reported By 7 ·Updated 11 days ago

Not able to deploy Opportunity Product Layout to another org after removing "Sales Price" from the layout

Metadata

Remove the "Sales price" from OpportunityLineItem-Opportunity Product Layout after enabling 'Supply Default Opportunity Line Item Values' perm in both source and target sandbox orgs. Users are getting error "Layout must contain an item for required layout field: UnitPrice" while deploying the layout...

Scheduled - Spring '20 ·Reported By 1 ·Updated 11 days ago

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....

In Review ·Reported By 18 ·Updated 13 days ago

Namespaced aggregate FieldInfos are cached incorrectly on EntityInfoImpl if subscriber org has non namespaced field with similar child relationship n

Apex , Packaging , Metadata

Namespaced aggregate FieldInfos are cached incorrectly on EntityInfoImpl if subscriber org have non namespaced field with similar child relationship name. In the Spring '20 release there will be a Critical Update available that will address this issue: https://releasenotes.docs.salesforce.com/en...

In Review ·Reported By 1 ·Updated 13 days ago

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 83 ·Updated 17 days ago

EnableActivities and EnableReports settings are disabled on updating a custom object via MetaData API

Custom Objects , Metadata , Spring 16

EnableActivities and EnableReports settings are disabled on updating a custom object via the Metadata API if the settings are excluded from the Metadata XML

In Review ·Reported By 10 ·Updated 17 days ago

Patch org creation fails due to duplicate picklist labels resulting in ISE with Id: -1875811753

AppExchange , Packaging , Metadata

When creating a patch org, the org is created successfully however, the package deploy process fails with an ISE with an Error Id ending in: -1875811753. Picklist values which have the same labels but different API names cannot be deployed and result in an error. This error may be the result of...

In Review ·Reported By 1 ·Updated 18 days ago

Prev | 11 to 20 of 244 | 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.