When you create or edit a DQE One Unify process, you can scope it to a specific set of records by choosing a Selected List View instead of processing the whole object. The Use List View Sort option additionally applies the list view's sort order to the process.
Why a specific user's access to the list view matters
At every run — scheduled, chained to another process, or launched manually from the console — DQE One re-reads the selected list view's filters (and sort order, if enabled) directly from Salesforce. This read is not done as the user who created the process or clicked "Run": it is always done as the user who installed DQE One, whose credentials are reused for every subsequent call.
What "installed DQE One" means here
In this article, "the user who installed DQE One" specifically means the person who completed the DQE One Installer app's setup wizard — the step where you grant DQE One access to your Salesforce org (the OAuth consent screen). This is not the same as clicking Install on the AppExchange listing itself: that step only requires the "Download AppExchange Packages" user permission and does not, on its own, connect DQE One to anything. If a different person carried out each of these two steps in your org, it is the person who completed the setup wizard that matters for list view sharing.
There is no single user who fills this role the same way in every org — it depends entirely on who ran the setup wizard. Depending on how your organization set things up, this can be:
- A dedicated integration/service user created specifically for this purpose — some organizations do this deliberately, and may already refer to it internally by their own name (for example, a "technical user").
- Or simply the personal account of whoever happened to run the setup wizard — in many organizations, there is no dedicated user at all.
If you're not sure which one applies to you, go to Setup > Connected Apps OAuth Usage, find DQE One Installer, and check which user currently holds an active authorization for it.
How to share a list view correctly
On the list view, open its visibility settings ("Restrict Visibility" / who can see this list view) and make sure that user is covered by one of these:
- The list view is shared directly with that user, or
- The list view is shared with a public group that includes that user — recommended, since it keeps working if the exact sharing rule changes later, or if the setup wizard is ever re-run by a different user.
Do this for every list view used by a DQE One process — each process has its own Selected List View, so sharing one does not cover the others.
What happens if sharing is missing
If that user cannot see the list view, DQE One does not raise a visible error. The process silently falls back to an empty filter (and no sort order) and runs against the entire object population instead of the list view's scope. If a process that should only touch a subset of records processes far more records than expected, this is the first thing to check.
Good to know
This applies identically to filters and to sort order: both are read from the same list view in the same call, and both are lost together if that user doesn't have access. Running the setup wizard with a dedicated integration user, rather than a personal admin account, makes this easier to maintain over time, since it won't change if the person who set up DQE One leaves the company.
Related articles
Related to