Running Reports as Selected Users with JWT OAuth and the Reports and Dashboards API
- David Reed
Salesforce reporting introduces some fascinating complexities to data visibility and exposure, particularly for organizations using Private Organization-Wide Defaults.
The key complicating factor is this: when a Salesforce report is run, it's run in the context of some user or another, and the records that are shown on the report are the ones that are visible to that user. This means that report distribution solutions have to be very careful to only show each user a report run in their own context - not someone else's.
Suppose your organization builds a critical report that many users will need to review. It's built to show "My Opportunities", so each user will see only their own Opportunities, and the Opportunity Organization-Wide Default is Private. You add a criterion to the report to only show Opportunities that have your internal "Needs Attention" Checkbox set. Now: how do you make sure your users are regularly updated when they have Opportunities that require their review?
A naive solution would create one subscription to this report, say for Frank Q. Exec, and add all of the users who need to receive it as recipients:
But this runs afoul of the principle mentioned above: the report's context user is Frank, and the recipients of the report will see data as if they were Frank. From Salesforce:
IMPORTANT Recipients see emailed report data as the person running the report. Consider that they may see more or less data than they normally see in Salesforce.
This is unlikely to be an acceptable outcome.
Further, we can't simply have Frank create many subscriptions to the same report, adding one user as both the recipient and the running user to each: Frank only gets five total report subscriptions, and he can only have one subscription to each report.
Of course, users can schedule reports themselves, in their own context, and they can run them manually, and we can build dynamic dashboards (which come with their own limits). But what if we really need to create these subscriptions for our users automatically, or allow our admins to manage them for thousands of users at a time? What if, in fact, we want to offer the users a bespoke user interface to let them select subscriptions to standard corporate reports, or run reports in their contexts to feed into an external reporting or business intelligence solution?
This is a question I've struggled with before, and I was excited to see Martin Borthiry propose the issue on Salesforce Stack Exchange. Here, I'd like to expand on the solution I sketched out in response to Martin's question.
There are two report subscription functionalities on Salesforce, and they work rather differently. Report subscriptions are summarized in the Salesforce documentation under Schedule and Subscribe to Reports.
On Classic, one can "Subscribe" to a report, and one can "Schedule Future Runs". The nomenclature here is confusing: a Classic "Subscribe" asks Salesforce to notify us if the report's results meet certain thresholds, but it's not for regularly receiving copies of the report. We're not going to look at this feature. "Schedule Future Runs" is equivalent to a report subscription in Lightning and is the feature corresponding to the business problem discussed above.
On Lightning, we simply have an option to Subscribe, as we saw above. There's no Lightning equivalent to the Classic "Subscribe" feature.
So what happens when we subscribe to a report?
The Classic Schedule Future Runs and the Lightning Subscribe functionality is represented under the hood as
CronJobDetail records with the
CronJobDetail.JobType field set to
'A', for Analytics Notification. You can find them in queries from the Developer Console or Workbench via queries like
SELECT CronExpression, OwnerId, CronJobDetail.Name FROM CronTrigger WHERE CronJobDetail.JobType = 'A'
Unfortunately, knowing this doesn't help us very much. Neither
CronJobDetail can be created directly in Apex or via the API, and the objects provide very little detail about existing report subscriptions. The Report Id, for example, is notable by its absence, and the
Name field is just a UUID.
A more promising avenue for our use case is the Reports and Dashboards API, because it offers an endpoint to create an Analytics Notification.
with a JSON body like this
The feature set shown here in JSON is at parity with the user interface, and has the same limitations. Adding a recipient for the subscription over the API, for example, suffers from the same visibility flaws as doing so in the UI. And the API doesn't let us do what we truly want to - create report subscriptions for other users that run as those other users - because we cannot set the owner of the subscription programmatically.
... or can we?
While the Reporting and Analytics API doesn't support setting the context user for a subscription, it always takes action as the user as whom we authenticate to the API. And that we can control.
Setup: Connected Apps and Certificates
Setting up the JWT flow involves building a Connected App in Salesforce, under which our scripts will authenticate. JWT is secured using a certificate and associated public key/private key pair - Salesforce holds the public key, our script holds the private key.
This is the same mechanism used for authentication in many Continuous Integration solutions. I'm not going to rehash all of the details here, because they're well-covered elsewhere. You can follow Salesforce's steps in using SFDX for continuous integration, or read through my own article about setting up CircleCI with Salesforce DX.
When you're finished building the Connected App, add the Profiles of each of the users who are to be subscribed to reports to the Connected App as a pre-approved Profile, or assign all of those users a Permission Set and assign that Permission Set as pre-approved on the Connected App. This ensures that we can authenticate to the API as those users without any intervention.
Building the Scripts
We're going to stick to sketching out a solution here that can be adapted to many different business problems, as we discussed earlier. For simplicity, we'll use Salesforce DX to handle the JWT authentication, even though we're not using SFDX for development here. Because it's my preferred scripting workflow, I'll be using Python with
The main job of our script is to login as a user and create a report subscription for them. We might build this towards a specific business process by adding scaffolding to, for example, query a custom object out of Salesforce to define which reports should be subscribed automatically for which users, but we'll leave that elaboration to a later date. Once we've got that core functionality achieved, we can wrap it in the logic we need for specific applications.
Let's put the key field (private key) from our JWT setup in a file called
server.key. Put the username of the user we want to subscribe (who must be pre-authorized to the Connected App) in the environment variable
$USERNAME and the Connected App's Consumer Key in
Then we can get an Access Token to make an API call into Salesforce, letting SFDX do the heavy lifting:
(If you have
jq installed, you can simplify these one-liners).
Now we've established an authenticated session as
$USERNAME, even though we do not have that user's credentials or any setup for that user besides preauthorizing their profile on the Connected App, and we have the values we need (the Access Token and Instance URL) stored in our environment.
Now we'll switch over to Python. A quick script grabs those environment variables and uses
simple_salesforce to make an API call to generate the report subscription.
= # Use an Access Token and Report Id to add a Lightning report subscription for this user # such that the report will run as that user. = = = =
Execute the script
$REPORTID is the Salesforce Id of the report you wish to subscribe the user for, and then if we log in as that user in the UI, we'll find a shiny new Lightning report subscription established for them.
Note that it's set for daily at 0300, as specified in the example JSON.
We've got a proof-of-concept in place showing that we can in fact schedule results for users run as those users. In an article to follow soon, we'll look at operationalizing this approach and building out business processes atop it.