Salesforce Facts by Abhishek

There's a known issue while using equals to NULL filter in Data Mapper Extract. To fix this, we need to add a not equals to operator. In this example, we are fetching contacts without AccountId populated. Attached are the screenshots.

There's an issue with accessing the multi select picklist field on user object. While accessing it for the current user in flow's formula resource it doesn't work as expected. 1) It does not appear in the search result. However if we enter it manually, the formula gets saved. 2) The INCLUDES function does not work. Always returns FALSE, even when it is expected to return TRUE. The workaround is to use a Get Records on the User object and then use a decision element with Contains operator.

While referencing the external services in apex, we might encounter error like: Dependent class is invalid and needs recompilation: Class ExternalService.MyCallout : Unexpected token '2'. This is a known issue. The workaround is to replace '2XX' with '200' in the JSON of external service. Reference:  https://help.salesforce.com/s/issue?id=a028c00000uW9g4

There's a loophole with the field history tracking when the automation is executed in system context. If the user doesn't have the object access/field access and the automation executes in system context without sharing mode, then the record gets created and the audit fields are stamped correctly but the field history related list stays blank. Here's the relevant Idea link:  https://ideas.salesforce.com/s/idea/a0BHp000019OmswMAC/enable-field-history-for-system-mode-dmls-regardless-of-object-permissions Reference:  https://trailhead.salesforce.com/trailblazer-community/feed/0D5KX00000mjpO60AI

After deploying the external credential and external service registrations to the higher orgs, you might encounter the error from flow while invoking the callout: 'The external credential isn't fully configured. Try reconnecting to the external system or contact your Salesforce admin'. To fix this issue, Go to the external credential -> Under Principals section, check the authentication status -> if it is not configured, click dropdown -> edit -> populate the correct Client Id & Client Secret -> Save. This will update the authentication status to Configured.

Currently if we use group by with full name in a report, the drill down feature doesn't work for the records which have middle name populated. Reference:  https://ideas.salesforce.com/s/idea/a0B8W00000GdjzQUAR/fix-full-name-filters-in-reports