Loading

Salesforce OmniStudio: FlexCards and OmniScript Components not Visible to Multiple Users After Go-Live

Data pubblicazione: Jul 16, 2026
Descrizione

This article addresses the intent to restore visibility of Salesforce OmniStudio FlexCards and OmniScript-based Lightning components for multiple end users who share a profile or permission set. Affected users see the component area blank or non-functional with no visible error, while a System Administrator sees the component correctly.

Some users also encounter "ApiQueryException" referencing "OmniInteractionAccessConfig.DeveloperName" in the browser JavaScript console. Trigger conditions include: enabling OmniStudio Metadata (Managed Package vs. Standard Runtime), enabling Enhanced Runtime Performance, deploying new component versions, or going live in a production org where sandbox permission sets were not migrated.

Affects non-administrator profiles and users assigned custom permission sets that lack OmniStudio object access; System Administrators are typically unaffected because their profile grants access to all OmniStudio objects. 

Risoluzione

Work through the causes in order. Both causes commonly co-occur when new component versions are deployed or you go live.

Cause 1: Affected users are missing OmniStudio object permissions.

  •  Go to Setup > Users > Permission Sets > Omnistudio User [OmniStudioUser]
  • Click Manage Assignments > Add Assignment, select every affected user (all users sharing the reference user's profile), and click Assign.
  • This will provide Users with the below Omni-object permissions:
    • OmniProcesses [OmniProcess]
    • OmniProcess Elements [OmniProcessElement]
    • OmniData Transformations [OmniDataTransform] 
    • OmniUiCards [OmniUiCard] 

Cause 2: Enhanced Runtime Performance is enabled and enforces in-platform access checks that unentitled users fail.

  • Go to Setup and enter "OmniStudio Settings" in Quick Find; click OmniStudio Settings.
  • Confirm Enhanced Runtime Performance is set to On. When On, OmniStudio components communicate through in-platform capabilities instead of Apex, so the object permissions in Cause 1 are mandatory for every user.
  • Assign the permission set from Cause 1 to all affected users before relying on this setting.

Cause 3: A newly activated component version is not the version users are entitled to see.

  • Open OmniStudio (App Launcher > OmniStudio).
  • Open the affected FlexCard or OmniScript (for example, the Patient Card FlexCard or Assessment OmniScript).
  • Confirm the intended version shows Status of Active. If a new version was deployed, click the current version and click Activate Version so exactly one version is Active.
  • Clear the browser cache and reload the Lightning record page that hosts the component.

Confirm the issue is resolved by logging in as (or having) an affected non-admin user open the Lightning record page (for example the Person Account or patient record) and verifying the Patient Card FlexCard and Assessment component render and function, with no blank area and no "ApiQueryException" in the browser JavaScript console.

Numero articolo Knowledge

005389120

 
Caricamento
Salesforce Help | Article