Salesforce Known Issues
Trailblazer Community

Known Issues · Custom Objects

External Lookup field is shown as ID instead of the name

Apex , API , VisualForce , Custom Objects , Sandbox , Winter 18

When performing an External look up on editing the record , the field displays an ID (aXXXXXXXXX) rather than the name of the record.

In Review ·Reported By 23 ·Updated 2020-11-19

In Summer 17' Special symbols like the registered trademark symbol ® appears extremely tiny for the text fields in Lightning UI

Custom Objects , Summer 17

Registered trademark symbol ® appears extremely tiny for the text fields in LEX for an org on Summer 17, Works fine in Classic.

In Review ·Reported By 10 ·Updated 2020-11-17

Create new record from 'New' Standard button threw an error during value provisioning on custom object [LEX]

API , Custom Objects , Lightning , Winter 21

Create new record from 'New' Standard button threw an error during value provisioning on custom object. Error: [LWC component's @wire target property or method threw an error during value provisioning. Original error: [Cannot assign to read only property 'value' of object '#<Object>']]

Fixed - Winter '21 Patch 9.6 ·Reported By 41 ·Updated 2020-10-27

Date/Datetime field on custom object record does not shows Japanese Imperial Calendar in Winter'21

Custom Objects , Lightning , Winter 21

Date/Datetime field on custom object record does not shows Japanese Imperial Calendar in Winter'21.

In Review ·Reported By 5 ·Updated 2020-10-27

When creating a base platform object record and a custom object record in the same transaction, sharing rule does not fire for the second object

Sharing , Custom Objects , Financial Services Cloud , Health Cloud

When creating a base platform object record and a custom object record in the same transaction (when both have criteria-based sharing rules), only the sharing rule of the first record is executed.

Fixed - Winter '21 Patch 1.0 ·Reported By 4 ·Updated 2020-10-19

SOQL query on Custom Metadata Type records ignores where clause with Database.getQueryLocator

Apex , Custom Objects , Metadata

SOQL query used with Database.getQueryLocator on Custom Metadata Type records returns results without considering the where clause.

Fixed - Winter '21 Patch 2.0 ·Reported By 0 ·Updated 2020-10-19

Label value appears in DeveloperName field of Custom Metadata Types query when run as Community User but not with Admin

Custom Objects , Developer Console , Communities

DeveloperName field is returning label instead of API name (Developer Name) for the community user when it is in relationship query. Note: The issue is not reproducible to System admin, as mentioned it is only to community users.

In Review ·Reported By 11 ·Updated 2020-10-08

Unexpected validation rule executes while installing managed package with custom metadata

API , Platform , Custom Objects , Metadata

Unexpected validation rule executes while installing managed package with customer metadata due to customer package created with parent-child relationships between the custom metadata types. Package also contain validation rules for all child objects and validating on parent object attributes (parent...

In Review ·Reported By 29 ·Updated 2020-09-24

Database.emptyRecycleBin() throws INVALID_ID_FIELD when attempting to empty deleted records of CaseComment type from recycle bin

Apex , Custom Objects

Database.emptyRecycleBin() throws INVALID_ID_FIELD when attempting to empty deleted records of CaseComment type from recycle bin Expected result: records deleted Actual result: INVALID_ID_FIELD exception

In Review ·Reported By 11 ·Updated 2020-09-24

Metadata API returning incorrect audit fields information about Custom Metadata Type records

API , Custom Objects , Metadata

Values for audit fields (Createdby, LastModifiedby, CreatedDate and LastModifiedDate) are returned incorrect when retrieved using List Metadata feature in Metadata API

In Review ·Reported By 6 ·Updated 2020-09-22

Prev | 11 to 20 of 121 | 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.