Salesforce Facts by Abhishek

With the new mutation feature with GraphQL, the field values of the created record can be accessed right after the create record operation. In this example, there is an automation to set some value on the Description field and a formula field is also present on the Contact object. Both are accessible right after a record creation. Attached are the screenshots.

In the upcoming Spring'26 release, we will be able to mutate data with the GraphQL api i.e. it will now be possible to perform create, update or delete operations. Also, using this api we will be able to create multiple related records in the single call, similar to composite api. In this example, we are creating an account and a related contact record. Reference:  https://developer.salesforce.com/docs/platform/graphql/guide/mutations-use.html https://developer.salesforce.com/docs/platform/lwc/guide/reference-graphql-mutation.html Attached are the screenshots.

There is an object TwoFactorMethodsInfo which keeps track of the identity verification methods which the user has registered. 1) In order to access the object, user requires the 'Manage MFA in API' user permission. 2) If a DML and a query on this object is performed on the same call, it throws an error. Reference:  https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_twofactormethodsinfo.htm

With the Winter'26 release, we can now access sobject fields from the Create records element without an additional Get records. This also works fine for local formula fields(not for cross object formula fields). This is similar to the Formulas.recalculateFormulas() function but doesn't consume any SOQL query. In this example, we have a formula field on case which calculates a date 10 days plus the Createddate. In the flow, we are creating a case record and referring the same field from the Create Record reference, it shows the value correctly. Reference:  https://admin.salesforce.com/blog/2025/improve-automation-with-winter-26-flow-features-be-release-ready Attached are the screenshots.

We need to be careful while using the IN operator in Get Records element along with sorting of the result by a field. If the text collection is null which is used in the Id filter, the underlying SOQL throws a syntax error. As a best practice, it is always preferred to check if the collection var is null or not. This also avoids one SOQL query. Attached are the screenshots. Reference:  https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000JfvwISAR

We can implement a validation in screen flow using the formula resource to select a date other than the first monday and last friday of the month. Attached are the screenshots.