Known Issues · Salesforce DX

Translations imported in Scratch Orgs are not retrieved by SFDX pull command

Salesforce DX

SFDX pull command not retrieving imported Translation records/data from Scratch orgs

In Review ·Reported By 43 ·Updated Yesterday

Unable to open Process Builder when installed from Unlocked Package

Salesforce DX

Unable to open the Process Builder when installed from Unlocked Package, getting Internal Server Error : 1173818564-103493 (1201824199)

In Review ·Reported By 38 ·Updated 2 days ago

Scratch org creation fails with Error ID (1203833999) without providing any details on troublesome components/features.

Sandbox , Salesforce DX

Scratch org creation fails with below error without providing details on troublesome components/features. === Component Failures [1] TYPE FILE NAME PROBLEM ───── ───────────────────────────────────── ───────────── ────────────────────────────────────────────────────────────────────────────────────────────────────────────── Error...

In Review ·Reported By 27 ·Updated Yesterday

Unlocked Package - Package creation fails due to feature "Account.sharing" & "Account.RecordType"

Salesforce DX

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

Not Able to Convert Report Metadata to SFDX Format

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 43 ·Updated 3 days ago

SFDX: Second and subsequent saves of joined reports cause sfdx pulls to fail

Salesforce DX

When using sfdx force:source:pull command to pull down the Joined reports which are saved multiple times are causing errors.

In Review ·Reported By 15 ·Updated 2 days ago

force:source:status returns "no results found" when deleting a custom label in scratch org. - force:source:pull worked

Salesforce DX

Some customers may have observed when building a DX project, push some fields, force:source:push fails to recognize that the fields are an addition.

In Review ·Reported By 3 ·Updated Yesterday

New!sfdx force:source:pull gives error for EntitlementProcess which contain uppercase letters

API , Salesforce DX

"ERROR running force:source:pull: Entity of type 'EntitlementProcess' named 'myDefaultProcess' cannot be found" when doing a sfdx force:source:pull in the scratch org. This is seen if you create an EntitlementProcess with an Uppercase name such as "myDefaultProcess" It works if the Entitlement Process...

In Review ·Reported By 1 ·Updated Yesterday

SFDX force:package1:version:create command has incomplete PostInstall Instructions

Packaging , Platform , Salesforce DX

For 1st generation packages, developers can signify that they want either a URL or a Visualforce page as a PostInstall instruction page that will be displayed to users upon install. We need to improve this command such that developers can set a visualforce page as the URL.

In Review ·Reported By 5 ·Updated 3 days ago

Regression: : Error when syncing External Objects from odata or apex connect when org language default is not English Error: XYZ_x:Cannot specify a st

Salesforce DX , Spring 19 , Summer 19

Syncing external objects from Odata or Apex data source fails because of the following error starting in Summer'19 when organization default language is set to Portuguese (or any languages that don't need to care about sound to start nouns with). -- <ObjectName>__x:Cannot specify a startsWith attribute...

Scheduled - Summer '19 Patch 12.0 ·Reported By 6 ·Updated 5 days ago

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