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 24 ·Updated 2 days ago

Deployments containing dependent fields fail with Unexpected Error

Packaging , Metadata , Change Sets

When there is a delete operation, or an operation on a soft-deleted field (Field1), in a deployment package with another field (Field2) being updated and dependent on Field1, the deployment will fail with errors observed against Field2 similar to the following: Error: An unexpected error occurred. Please...

In Review ·Reported By 13 ·Updated Yesterday

MD-API deploy error when lookup filter and searchLayout is changed

Packaging , Metadata

When you are deploying a package where lookup filters or searchLayouts are being changed, errors will be thrown in deployment. Note: This will also occur when the lookup filter deployment and the the lookup field is being created in the same deployment package. UnsupportedOperationException

In Review ·Reported By 10 ·Updated 2 days ago

Patch org creation fails with error number (1008011683)

AppExchange , Packaging , Partner

When attempting to create a patch org, it will fail and email containing the error number (1008011683) is produced. You may also receive an error message similar to: VALIDATION_FAILED Missing Organization Feature: NetworksEnabledOnce: null

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

Patch org creation failure due to permission or feature discrepancy between dev org and patch org

AppExchange , Packaging , Partner

Some partners are finding that when they create a patch org, that the patch org will be created but does not successfully work as a patch org. This is due to the package not being deployed to the org due to a discrepancy in enabled features or permissions between the patch org and the packaging developer...

In Review ·Reported By 20 ·Updated 3 days ago

Package install fails if it contains CRT based on external objects using custom adapter data source

Packaging , Partner

Package install or upgrade fails with "Insufficient Privileges" error if it contains CRT(custom report type) based on external object, which uses custom adapter data source.

Fixed - Winter '20 Patch 14.0 ·Reported By 1 ·Updated 7 days ago

Packages containing "Lightning Community Template" component may fail to install in some orgs.

AppExchange , Packaging , Winter 20

Packages containing "Lightning Community Template" component may fail to install in some orgs, NavigationLinkSet is spidered in by Lightning community template.

Scheduled - Spring '20 Patch 1.0 ·Reported By 6 ·Updated 9 days ago

Managed components can only be deleted in Salesforce classic.

Packaging , Lightning

When attempting to delete managed components in the Lightning (LEX) interface an error is thrown: "Cannot delete managed component".

In Review ·Reported By 1 ·Updated 9 days ago

[2GP] Package upgrades fail with gack when package has post-install script and version number is 0.x.x.x

Packaging , Salesforce DX

During upgrade of a second-generation managed package, a gack occurs during initialization of the post-install script when the version of the package being upgraded is 0.x.x.x. Note that 0 is a valid major version number for 2nd-gen packages, unlike 1st-gen. Expected: ~~~~~~~~ Package upgrade to...

In Review ·Reported By 2 ·Updated 12 days ago

Intermittent sfdx force:org:create not creating scratch org with all permissions specified in scratch definition file

API , Packaging

In some customers orgs we are seeing some org setting not being set consistently for scratch org creation

No Fix ·Reported By 1 ·Updated 12 days ago

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