Create flows that use sObjects not found in the Object Manager with these simple instructions. https://www.linkedin.com/in/dirk-keaton-785a1531/

1. Weird sObjects
PRESENTATION BY DIRK KEATON
FOR MORE SALESFORCE TRAINING, FOLLOW ON LINKEDIN

2. Our Goals
Name new sObjects
Explore and Discuss Object Reference
Create flow accessing these objects

3. SObjects are Everywhere
“NORMAL” SOBJECTS
Task
Contact
Account
In the object manager
“WEIRD” SOBJECTS
Task Relation-Connects Accounts to Tasks
Contact Share-Created when a Contact is
Manually Shared with a User
Account History-Records changes to the
account object
Accessed through flow, apex, reports

4. It can get
silly:

5. What will our flow do?
Our flow is designed for an org with private sharing for accounts. When accounts are private a
person may be assigned a task related to an account that they can’t see.
Our flow addresses this problem. When a task is created, it will share all accounts related to the
task to the person who the task is assigned to.

6. Setting up
Under activity settings, allow users to relate multiple contacts to tasks and events
Under sharing settings,
make account sharing private:

7. Build a record triggered flow

8. Begin by choosing an object
Click choose object
Then choose task
Set the flow to “trigger”
when a record is created or
updated

9. Add a decision element
If you try to share an account
with yourself, you’ll trigger an
error that will stop the flow. To
avoid this, add a decision
element.
{!$Record.OwnerId} Does not
Equal {!$Record.CreatedById}

10. Getting the People from the Task
A standard whoid won’t work if there’s more
than one person on the task.
We need a weird subject—we need to go to
the object reference.
Immediately there are two candidates:
TaskRelation and TaskWhoRelation

11. The Refence includes
A list of fields
A code block (usually Apex) and links to
related sObjects

12. GetTaskrelations
Make the TaskId equal to
$Record.activityid
We select activity because all
tasks are activities.
Select all records (so we can
capture everyone added)

13. Create a loop
Loop through the collection variable you
created.

14. Connect your get records element
Make sure to connect your get records
element to the “not equal to creator” path.
You do not need to connect anything to
default outcome

15. Create a New Variable
Name it AccountShareExample
Make sure the record it targets is
AccountShare

16. Select the following options
Contactshare.contactid equals
Loop_Through_Relations.RelationId
ContactShare.UserOrGroupId
equals $Record.AssignedToId
We have to give the account and
opportunity read access

17. Create another variable
Call it ShareCollector
Allow multiple values so it can be a
a collection variable for
AccountShares

18. Adding to the collection
Choose share collector as the variable
Select the “add” operator. Then, select
ContactShareExample
You may get an error or the system may try to
add a field name after {!ContactShare} Ignore
it and do not include a period. Click “outside”
the box to ignore it.

19. Add a create records element
Choose multiple
Select ShareCollector as your values

20. Activate your flow and test it!
Take this contact, for example.
Our test user has no access.

21. Create the task
Make sure to include a person who the test
user doesn’t have access to
Assign it to them.

22. They now have full access!