Posts

Salesforce Fact #897 | Opportunity Amount is read only

When the Opportunity is associated with one or more Opportunity Products, the amount field is read only. Reference:  https://help.salesforce.com/s/articleView?id=000387134&type=1

Salesforce Fact #896 | Conditional field formatting in action

Image
With the latest release, we have the Conditional Field Formatting as GA. With this option, we can add visual indicator to a particular field based on the value of that particular field or other fields. Reference:  https://admin.salesforce.com/blog/2024/conditional-field-formatting-winter-25-be-release-ready In this example, we are showing a warning symbol when the Opportunity Probability is less than 10%. Attached are the screenshots.

Salesforce Fact #895 | Dependent record picker in LWC

Image
We can create a dependent lightning record picker in LWC. Suppose, we have two record pickers and once the account record is selected, the second record picker should filter out the related contacts. Reference:  https://salesforce.stackexchange.com/questions/428066/lightning-record-picker-dynamic-record-filter-not-working Attached are the code snippets.

Salesforce Fact #894 | Adding user to multiple public groups/queues at once

Image
There are times when we need to add a particular user to multiple public groups and queues. Now, based on the OOTB option, we can do that by going to each and every public group or queue. We can create a screen flow as well to assign a particular user to multiple public group or queue at once to ease the work for users. Attached are the screenshots.

Salesforce Fact #893 | OLI insert/update triggers Opp triggers and flows

When an Opportunity Product record is created or during update if certain fields like Sales price/Quantity is updated, it executes the before and after update triggers and flows on related opportunity. So, we need to be careful while creating any automation on Opportunity Product. Reference:  https://salesforce.stackexchange.com/questions/184659/opportunitylineitem-fires-opportunity-trigger

Salesforce Fact #892 | Parent record access missing in LWC getRecord

Image
While using getRecord in LWC, if the user does not have access to the parent record the parent field values are shown as null but there is no error encountered. In this example, we have an Account lookup on Lead record and fetching the Rating and Account Owner name using getRecord. Attached are the screenshots.