Known Issues · Salesforce DX
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 15 ·Updated 4 days ago
Changing a 'Managed' Platform Cache Partition (which is included in an installed Managed package) in a Scratch Org causes the following error on: sfdx force:source:pull ERROR: Entity of type 'PlatformCachePartition' named '<Partition Name>' cannot be found. This is happening on managed partitions...
In Review ·Reported By 3 ·Updated 6 days ago
Large number of Apex Tests cause a socket connection reset when executing a status report via Salesforce DX using below command : sfdx force:apex:test:report --testrunid <testId>
In Review ·Reported By 6 ·Updated 7 days ago
CLI Command which is getting error out : sfdx force:apex:test:run --targetusername <username> --resultformat tap --codecoverage when using Jenkins The error happens only when --codecoverage parameter is used.
In Review ·Reported By 2 ·Updated 7 days ago
SFDX pull command not retrieving imported Translation records/data from Scratch orgs
In Review ·Reported By 11 ·Updated 10 days ago
If "sfdx force:source:pull" command is run to fetch the profile details after changing the assigned record types, we see that the changes do not get pulled.
Fixed - Winter '19 Patch 10.0 ·Reported By 12 ·Updated 17 days ago
If "sfdx force:source:pull" command is run to fetch the profile details after changing the assigned record types. In metadata source of that profile, It does not show any recordTypeVisibilities elements at all.
No Fix ·Reported By 11 ·Updated 20 days ago
Action Override when added to Custom Object, the sfdx force:src:pull does not detect it.
In Review ·Reported By 0 ·Updated 2018-10-15
Salesforce DX : picklist values on recordType when changes are not being detected by force:source:status and are not pulled by force:source:pull
Fixed - Winter '19 ·Reported By 16 ·Updated 2018-10-13
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.