Salesforce: Sharing Detail

More than 5 years ago, we wrote about Sharing Button URL, where you can check Sharing Detail and Access, which is useful to troubleshoot why a user is able to view or edit a record.

On the Sharing Detail page, it will show you all User, Public Group, Role, Role and Internal Subordinates and the access level. In this blog I am using Opportunity as a sample, Opportunity visibility in my org is Private.

https://johantest.my.salesforce.com/p/share/OppSharingDetail?parentId=0062H0000123456QAN

We can get the same result from SOQL: SELECT Id, OpportunityAccessLevel, RowCause, UserOrGroupId FROM OpportunityShare WHERE OpportunityId = '0062H0000123456QAN' ORDER BY UserOrGroupId 

Let us compare from Sharing Detail page:

1. Sharing Detail #1 = SOQL row #7, reason = Account Sharing which = Implicit Child [in Account Sharing Rules, to Role]
2. Sharing Detail #2 = SOQL row #6, reason = Opportunity Sharing Rule which = Rule [in Opportunity Sharing Rules, to Role and Internal Subordinates]
3. Sharing Detail #3 = SOQL row #5, reason = Account Sharing which = Implicit Child [in Account Sharing Rules, to Role and Internal Subordinates]
4. Sharing Detail #4 = SOQL row #4, reason = Opportunity Sharing Rule which = Rule [in Opportunity Sharing Rules, to Public Group] 
5. Sharing Detail #5 = SOQL row #1, reason = Account Sharing which = Implicit Child [User is Account Owner] 
6. Sharing Detail #6 = SOQL row #2, reason = Owner which = Owner [User is Opportunity Owner]
7. Sharing Detail #7 = SOQL row #3, reason = Opportunity Team with Split which = Team [User in Opportunity Split]
8. Sharing Detail #8 = SOQL row #8, reason = Account Sharing which = Implicit Child [in Account Sharing Rules, to Public Group]

Access level comparison:

- In Sharing Detail, Full Access = All in SOQL

- In Sharing Detail, Read/Write = Edit in SOQL

- In Sharing Detail, Read Only = Read in SOQL

Copy from Sharing Detail

• Full Access - User can view, edit, delete, and transfer the record. User can also extend sharing access to other users.
• Read/Write - User can view and edit the record, and add associated records, notes, and attachments to it.
• Read Only - User can view the record, and add associated records to it. They cannot edit the record or add notes or attachments.
• Private - User cannot access the record in any way.

Summary:

• Sharing Detail page will only show User, Public Group, Role, Role and Internal Subordinates, but does not show: users in the higher role hierarchy of another user, users in the higher role hierarchy of a role hierarchy, users in the higher role hierarchy of user in Public Group. Click the Expand List button to see each user, access level, and the why.
• Query to OpportunityShare will show the same thing as on Sharing Detail page, so you can't just depend on OpportunityShare to determine all users that have access to a record.

Reference:

• OpportunityShare

Tableau CRM : using Source Field in computeRelative node

The computeRelative node is useful to traverse across rows to identify something or calculate something.

Three important items in a computeRelative node:

1. Partition By
2. Order By
3. Sort Direction (for 2 - Order By)

From the above screenshot:

- It is Opportunity 

- Partition By Account Id

- Order by CreatedDate and sort by Descending

The result in the calculated fields: 

- the first record in the partition would be the Last Opportunity created for an Account

- the last record in the partition would be the First Opportunity created for an Account

This is because we order by Descending.

There is two Expression Type in the calculated field for computeRelative: 

1. SAQL

2. Source Field

Use Case: to identify the First or Last or Previous record

using SAQL

SAQL Expression = case when previous(Id) is null then "Yes" else "No" end

* Id in above SAQL can be any field (always with value), as it is just used to check if any previous record exists.

using Source Field

In this method, the new calculated field will contain "Yes" if that's the first row, the rest will be the Id from the previous record, which is not important.

Comparison

Based on my testing, using Source Field is faster than SAQL in the dataflow. In the below example, the dataflow processing close to 1.6 million rows

Happy Sweet 17teen

Oh, this is not a blog about teen turn adult, but a celebration of the 17th anniversary of my 1st Salesforce org., which is still active till now.

If this org is a human, today it is officially an adult (in many parts of countries). While the org has been evolved a lot, at least from the shape which is the user interface. I did not screenshot every year, but here are a few milestones:

super old user interface — image credit to salesforceben.com

Theme 2 — The Salesforce Classic 2005 user interface — Its Summer 21

Theme 3 — The current Salesforce Classic user interface (a.k.a. Aloha)

The current Salesforce Lightning user interface 

Reference:

• User Interface Themes
• getUserInfoResult

Tableau CRM: Nodes with no data in Dataflow

 

First, it sounds weird when you said that your dataflow processed no data, but that could happen when you put a filter that clears off all data. What happened with the further nodes that create fields in the dataflow:

Augment with Right node has no data

• Warning: The dataflow was completed, but the NodeName node didn't augment any columns. Either the node didn't find any matches, or a join key contains only null values.
• Augment fields are created

Augment with Left node has no data

• Warning: The dataflow was completed, but the NodeName node didn't augment any columns. Either the node didn't find any matches, or a join key contains only null values.
• Augment fields are created

ComputeExpression

• No error and no warning
• ComputeExpression field is created

ComputeRelative with Expression Type = Source Field

• No error and no warning
• ComputeRelative field is created

ComputeRelative with Expression Type = SAQL

• No error and no warning
• ComputeRelative field is NOT created, because the field is not created, if you have any further transformation node that includes the new field, such as in slice, augment, etc., the dataflow will error. As per Salesforce, this is a defect, but no KI is created yet, the KI has been created, so feel free to "subscribe".

Salesforce Dashboard: Dynamic Gauge Charts

In Winter 22 release, Salesforce releases Dynamic Gauge Charts in Dashboard, even still beta. Before this, all segments (low, medium, high) values must be entered manually by editing the component. With Dynamic Gauge Charts, you just need to update a field and the segment target changed.

To use Dynamic Gauge Chart, you need to enable the feature from Reports and Dashboards Settings in the setup menu. 

The concept

You need to have a target value, this is the max value of the gauge chart. The value should be defined in an object, within a record, and in a field. Let say you use the Opportunity report for the component, it does not make sense to put the target in the Opportunity object. 

So, here is my idea:

- Create a custom object

- Create a number field: this to store the value or target

- Create a text field: this field used to store description

Notes: thanks to Nicholas Sullivan from the Trailblazers community for the idea to use a custom field in the User object to store each user target.

The component

Once "Enable Dashboard Dynamic Gauge Charts (Lightning Experience only)" is enabled, you will see Mode: Standard and Dynamic when editing a Gauge component. Standard = existing mode where you need to enter values for each segment, while Dynamic is the new one, where the segment is divided by % of target.

Object = which object to refer to chart target

Record = which record that holds the value for this component

Field = which field from the above record holds the value

Instead of value as per normal, we need to enter % for each segment to divide segments of the low, medium, high.

Footer: once you select "dynamic" mode, you cannot make use of the footer by entering any text, it will be locked and will show the description, for example, Sum of Amount (USD) compared to Target (Dynamic: Rec-1)

• Sum of Amount (USD) = the needle of gauge chart, which is the current value in the database
• Target = field name
• Dynamic = object name
• Rec-1 = record name

Reference:

• Automatically Tune Your Dashboards to Your Business Goals with Dynamic Gauge Charts (Beta)