Known Issues · Custom Objects
Metadata Deployment fails if there is history tracking in custom lookup field with look up filters, when the filter refers to a field with tracking to custom object in the same deployment transaction.
In Review ·Reported By 400 ·Updated 3 days ago
Related list Contact FirstName/LastName not showing as links on custom object with Master-Detail relationship in Lightning Experience
In Review ·Reported By 8 ·Updated 2 days ago
Sorting order not being used in SOQL with Custom Metadata Type when sort field is not in column queried. This result in the order not being returned properly with Flows, API, Apex, and any functionality which would use a SOQL query for Custom Metadata Type. Consider a Custom metadata type called MD_NUMBER__mdt...
In Review ·Reported By 27 ·Updated 4 days ago
In Lightning, some columns on related lists are displayed as blank despite fields containing value
In Review ·Reported By 4 ·Updated 9 days ago
The package upgrade removes dependent picklist values that are selected in a managed picklist field. Upgrading the same package version or a new version deselects the picklist values. This causes the customer to lose their original selected values and would have to add it back to the field.
Fixed - Spring '18 Patch 6.0 ·Reported By 15 ·Updated 12 days ago
Users cannot create any new records from related lists on person accounts. They get the following error: "Custom Contact: id value of incorrect type: 001100000000000Ooo" This problem occurs when the related custom object has a master-detail/lookup relationship to the Contact object.
Scheduled - Summer '18 ·Reported By 11 ·Updated 12 days ago
In Lightning App Builder, the Related Record component will throw an internal server error when used with a custom object that has a namespace (for example, objects included in managed packages).
Fixed - Spring '18 ·Reported By 7 ·Updated 12 days ago
When viewing a related list for an external object in Lightning you may not see any records.
In Review ·Reported By 28 ·Updated 2018-01-22
Salesforce Internal Server Error like : UNKNOWN ERROR: UNKNOWN_EXCEPTION: An unexpected error occurred. Please include this ErrorId if you contact support: 1132050911-112 (-1681035069) is thrown while insert if there is a null value to custom lookup field in an external object.
In Review ·Reported By 0 ·Updated 2018-01-19
When a change set contains a relationship field where the source environment's field type is Master-Detail and the target environment's field type is lookup with differing org-wide defaults (OWD) for the field's object in each environment, validating a change set causes sharing rules built on said object...
Fixed - Spring '18 ·Reported By 7 ·Updated 2018-01-15
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.