Salesforce Known Issues

New!Some package install fails if it contains inactive record type

AppExchange , Packaging , Partner

Some customers may get package failure issue if the package contains inactive record types. The error is displayed on UI: 1. (ObjectName__c.RecordtypeName) This record type cannot be deactivated because it is the last active record type for RecordtypeLabel ObjectName__c.RecordtypeName: This record...

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

Solution Collection object records are not being properly mapped

Packaging , Partner , Lightning

If Solution Collection object records are referenced in a lightning page, they are not properly mapped from Id to name if a trial is created from this org and an error occurs on the Lightning Page.

In Review ·Reported By 4 ·Updated 2 days ago

Fields end up in an invalid state when signed up from trialforce. Push upgrades will fail.

Packaging , Custom Objects , LMO , Partner

FieldDefinition relationships to Standard Fields on custom objects are stored in the database in the form: "<CustomObjectId>.<FieldApiName>" e.g. 01Ixx0000005ahE.Name. These fields are not remapped by the signup engine, since the field isn't totally and exclusively an ID. There's logic to partially remap...

Release In Progress - Spring '19 Patch 14.0 ·Reported By 3 ·Updated 3 days ago

Global constructor visibility issue in apex class after upgrading the package

Apex , Packaging , Partner

Create a managed package released version with 1.0, and it contains a global class with no constructor defined.You install the managed package into a subscriber org and create a custom class that instantiates an instance of the global class from the package.Then back in the managed package packaging...

In Review ·Reported By 7 ·Updated 7 days ago

Package install fails if it has post install script and there is a non-namespace indexed formula field in the org

Packaging , Partner

Package install fails with internal server error if it has post install script and there is a non-namespace indexed formula field in the subscriber org.

Scheduled - Summer '19 ·Reported By 3 ·Updated 9 days ago

Spring 19: Master field label changed when subscriber overrides field label

Packaging , Partner

In spring 19 release orgs, when subscriber overrides field label using translation workbench, the master field label changes to same.

Fixed - Spring '19 Patch 12.0 ·Reported By 3 ·Updated 12 days ago

Action override not updated by package upgrade

Packaging , Partner

When a managed object standard button is overridden by lightning component for "Lightning Experience Override" by developer in the packaging org, and the package is installed in a subscriber org, the override for "Lightning Experience Override" cannot be updated by package versions remove the lightning...

In Review ·Reported By 28 ·Updated 13 days ago

Error: "Not in package.xml" when attempting to validate or deploy a Change Set.

Packaging , Partner , Change Sets

Users may notice an error message "Not in package.xml" when attempting to validate or deploy an inbound Change Set. --- When a Developer deletes a component from their package, the component continues to exist in the subscriber org even after the package is upgraded. When the component is...

In Review ·Reported By 8 ·Updated 13 days ago

Fails to create trial orgs using private template on an instance different from TSO

Partner

When creating an org using private trialforce template on an instance which is different from the TSO, it fails and no error email is sent.

In Review ·Reported By 4 ·Updated 21 days ago

"Packages" tab in Partner Community can't load if there are large number of package versions

AppExchange , Partner

The issue arises when a package has a large number of package versions that our "Packages" tab in Partner Community can't load. If the partner can't see the package versions, they can't submit for Security Review and can't get the package version listed.

In Review ·Reported By 3 ·Updated 22 days ago

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