Contents
Why are some actions not showing up in lightning experience?
When viewing the Activity composer related list, you may notice that some activity actions within the lightning experience do not appear on records even though those actions have been added to the Salesforce1 and Lightning Experience Actions section.
Where do open activities go in Salesforce Lightning?
For those of you who have been migrated from Classic to Lightning, you notice that “Open Activities” and “Activity History” are no longer appeared in the related list, instead, they appear as a Lightning component called Activity.
All you need is to add related list single component to Lightning page layout using Lightning App Builder and select Open Activities in related list names available on the right-hand side panel. Once done, Save the page and activate it for the users you want.
Why does Salesforce Lightning log a call button not appear?
Salesforce Lightning: Log a Call button does not appear in Activity component. For those of you have been migrated from Classic to Lightning, you notice that “Open Activities” and “Activity History” are no longer appeared in the related list, instead, they appear as a Ligthning component called Activity.
Can you select custom record types in Lightning?
–Master– will not work. Note: If you have no custom record types for these objects (Tasks, Events) then you won’t be able to select any Record Type. If you do have custom record types, it needs to be associated with the global action to work in the lightning experience under the Activity composer.
How does adderror work in visualforce.com?
Otherwise, all records that passed the final pass without causing an error are all committed, while those that were “set aside” are flagged as errors and will be reported. AddError will also work on any field or record bound to a Visualforce page; you can show an error message without any DML operation at all.
What happens if allornone is false in adderror?
If allOrNone is false, then addError has a different effect. First, all records are attempted. If any return with an error on an object or field, those records are “set aside”, the governor limits are reset, and a second pass occurs.