Known Issues · Packaging
When installing a managed package or a package extension that includes a Permission Set which contains CRUD information for objects that have a Master/Detail relationship you may receive an internal server error.
In Review ·Reported By 158 ·Updated Yesterday
Deployment of VF component fails with "Unsupported attribute" error
A deployment of visualforce components fails with an error: "Unsupported attribute myAttribute in <c:myComponent> in myVfPage at line 369 column 50"
Fixed - Winter '19 ·Reported By 68 ·Updated 2 days ago
In orgs on the Summer '20 major Salesforce release, we are seeing similar errors to the below when uninstalling a package with a field included on a dataset Error: 1802406352-20360380 (894020651)
In Review ·Reported By 44 ·Updated 2 days ago
Packaging , Change Sets , Summer 19
Users could encounter an error when deploying Sharing Rules that use a Country Code picklist field as sharing criteria via Change Sets or packaging.
In Review ·Reported By 23 ·Updated Today
Packaging , Change Sets , Winter 23
On Winter'23 org, invalid Data error occurs when adding a component which having a dependency to a 2GP managed package to a change set. ----- Error: Invalid Data. Review all error messages below to correct your data. Can’t add component xxxxxx because it’s associated with metadata from a managed...
Scheduled - Spring '23 ·Reported By 20 ·Updated 2 days ago
Unlocked Package upgrade fails if lookup field with filter is removed from the subscriber org
Package upgrade fails if unlocked package has lookup field with named filter and user removes the lookup field from the package in subscriber org
Scheduled - Spring '23 ·Reported By 11 ·Updated Yesterday
A new Button "Assign to Volunteer Project" is showing up on the Contacts page for all orgs. This should show up only for Production Orgs having ERM (Emergency Response Management). If clicked, an error will be generated and no action will happen.
Fixed - Summer '20 Patch 13.5 ·Reported By 17 ·Updated 2 days ago
There are instances where a connected app is installed in the org and conflicting with a package being installed. When installing the package it will fail with the error "A newer version of this package is currently installed." Otherwise, an error ID will appear in which the background error is showing...
In Review ·Reported By 17 ·Updated 2 days ago
sfdx force:source:push to US Scratch orgs with "DE" packaged ancestor id fails
Packaging , Platform , Salesforce DX
Deploying the contents of the local sfdx project into the "US" scratch org fails while using, "ancestorId": "04t......" of the (German) 2GP package version built with a non-US country code *Note :* This is not just specific to (DE - German). It is applicable to other non-US country codes
In Review ·Reported By 8 ·Updated Yesterday
Change set validation may delete an object's sharing rules
When a change set contains a relationship field where the source environment's field type is Master-Detail and the target environment's field type is lookup with differing org-wide defaults (OWD) for the field's object in each environment, validating a change set causes sharing rules built on said object...
Fixed - Spring '18 ·Reported By 7 ·Updated 2 days ago
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.
