Known Issues · Salesforce DX
Picklist values not getting deployed during unlocked package upgrades
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 458 ·Updated Today
Unable to diff a RecordType meta file
When you try to use SFDX: Diff File Against Org for the Record Type files, it shows you that Selected Components are not available in the org.
In Review ·Reported By 33 ·Updated Today
Show warning message if standard object settings are included into unlocked package
Whenever include Standard Object in metadata for creating Unlocked Package version there should be a Warning Message.
In Review ·Reported By 19 ·Updated Today
When creating records for custom metadata types via SFDX using command force:cmdt:record:insert, it is creating undefined value and field for any NULL values provided in the CSV file.
In Review ·Reported By 6 ·Updated Yesterday
The ShapeRepresentation object exists in scratch orgs created using Org Shape. If a user creates a 'View All Data' permission set it will include read permissions on the ShapeRepresentation object. The permission set cannot be deployed to a sandbox as the ShapeRepresentation object does not exist in...
In Review ·Reported By 5 ·Updated Today
Github issue link: https://github.com/forcedotcom/cli/issues/1837 If you try to create or update a record using a key=value pair that has a quoted string in it, like this key="this is a 'quote'", then sfdx:force:data:record:create and sfdx:force:data:record:update just error out.
In Review ·Reported By 0 ·Updated Today
When creating/updating a record using sfdx force:data:record:create/force:data:record:update, values in field-value pairs that contain single quotes are stripped. Expected result The value should be uploaded with single quotes present as the value is a contraction. Actual result The value has...
In Review ·Reported By 1 ·Updated Yesterday
When an existing field is set to required, related Permission Sets FieldPermissions updated are not pulled to update the existing metadata payload. This causes discrepancy with future push happening to other orgs.
In Review ·Reported By 4 ·Updated 3 days ago
"TimelineObjectDefinition" metadata is exposed in Version 55.0 and later. Error shown during package retrieval/deploy using CLI.
In Review ·Reported By 3 ·Updated 3 days ago
Redeployment attempts of an LWC component containing the markup "<target>analytics__Dashboard</target>" in the meta.xml file results in an unknown exception despite the first instance of the same component deployment succeeding
In Review ·Reported By 1 ·Updated 3 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.
