Known Issues · Salesforce DX
SFDX pull command not retrieving imported Translation records/data from Scratch orgs
In Review ·Reported By 53 ·Updated Yesterday
Unable to open the Process Builder when installed from Unlocked Package, getting Internal Server Error : 1173818564-103493 (1201824199)
In Review ·Reported By 53 ·Updated 2 days ago
Picklist values not getting deployed during package upgrades, the newly added picklist value is not showing up in upgraded version of unlocked package
In Review ·Reported By 21 ·Updated Yesterday
When using sfdx force:source:pull command to pull down the Joined reports which are saved multiple times are causing errors.
Scheduled - Winter '20 Patch 2.0 ·Reported By 18 ·Updated 2 days ago
Record Type Associated values in Permission Sets are not set during package install. After unlocked package installation the Record Type Association is not set as per settings in permissionset-meta.xml metadata file.
Scheduled - Spring '20 ·Reported By 1 ·Updated 2 days ago
Unable to create Unlocked Package if its metadata contain a class referencing to the PendingServiceRouting object, it throws an error : "ERROR: OmniChannelService: Invalid type: PendingServiceRouting,OmniChannelService: Variable does not exist: queueItem,OmniChannelService: Invalid type
In Review ·Reported By 0 ·Updated 2 days ago
For Unlocked Packaging these features "Account.Sharing" & "Account.RecordType" not yet supported feature in definition . So while creating a package version if there are any dependencies with these properties then that would fail.
In Review ·Reported By 47 ·Updated 5 days ago
Getting Internal Server Error when creating an unlocked package version 2133552946-23258 (862547712)
Scheduled - Winter '20 ·Reported By 10 ·Updated 5 days ago
Not able to convert the Report metadata to SFDX format when the report is in sub folder , for eg : unzipped folder >>> package.xml file + reports folders >>> parent folder >>> sub folder + metadata file >>> metadata file.
In Review ·Reported By 53 ·Updated 7 days ago
sfdx force:source:pull does not report any changes if a custom field is deleted on a Standard Object or on a Managed Custom Object in a scratch org
In Review ·Reported By 11 ·Updated 7 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.