https://domainname.lightning.force.com/lightning/o/objectname__c/new
https://domainname.lightning.force.com/lightning/o/objectname__c/list?filterName=Recent
Every computer language has its own syntax, the same with query language or formula. Here are the samples of SAQL that are used in Dataflow.
Since CRM Analytics is moving with Recipe, here are samples of the formula syntax in the Recipe:
String - use '', e.g., 'Singapore'
Field name - use "", e.g., "Account.Id", optional if the field name does not contain dot(s)
Field with blank value - "Opportunity.Id" IS NULL
CASE, e.g., case when Have_Activity = 'Yes' or Have_Opportunity = 'Yes' then 'No' else 'Yes' end
Logical Function
use or, and, e.g., case when Have_Activity = 'Yes' or Have_Opportunity = 'Yes' then 'No' else 'Yes' end
Compare Operator
use != (not <>) as compare operator, also use = (not ==), e.g., Have_Activity != 'Yes'
Here is the step:
1. Create Salesforce Action -- navigate to Salesforce's object manager, look for the object, click on Buttons, Links, and Actions menu, then click New Action.
2. Add the newly created Action to a Salesforce page layout (this is a must).
3. Configure the Action from the CRM Analytics dataset.
Once configured, if you have a table widget in the dashboard, you can also set up one-click actions, so by clicking the value, the action selected will be performed, e.g., click the value in Account Name to call the action to edit Industry.
Reference:
For example, if Tom is the owner of Trident Inc.'s record, all users can view and edit it. However, only Tom can change the owner or delete (if he has Delete permission given via Profile or Permission Set) the Trident Inc. record.
Scenario:
1. User Profile (and Permission Set) does not have access to the object
2. User Profile (or Permission Set) has Read access to the object
3. User Profile (or Permission Set) has Edit access to the object
4. User Profile (or Permission Set) has Create access to the object
5. User Profile (or Permission Set) has Delete access to the object
So, in other words, View All permission is replaced with Read permission, while Edit All permission is replaced by Edit permission.
Note: Profile permission access does not roll up to user by Role Hierarchy
Reference:
As a Salesforce admin, seeing the parent objects of an object is easy; just go to the Object Manager, look in Fields & Relationships, and look for fields with type = Lookup or Master-Detail.
However, the other way around, looking for child objects from an object is not straightforward; developers can use getChildSObject().
Here is a way to find child objects, which is using Workbench.
Navigate to Standard & Custom Objects, choose the object, and see items under "Child Relationships"