Resolving Cross-Company Filter Errors: How to Grant Resource Access via Security Roles

Error:

Authz: cross company filter has no companies. User roles: User: {6773ED9F-DE1B-4EDD-94A3-561265423BD0} Company: Id: 7 Name: SYSTEMUSER Id: 260 Context: AuthzContext rlsEnabled: false rlsExplicit: false includeDerived: true autoAuthzMode: None autoAuthzSCsc: false, Resource: Resource type: table tableName: TaxDocumentExtension_IN tableID: 109321 The resource was not found in the cache.

Scenario: When trying to access a resource in Dynamics 365, you encounter the error above. It indicates that the system is not able to find the resource in the cache, and this is most likely because the required resource is not included in the security role for the user. This can happen due to missing resource assignments or misconfigured security roles that restrict access.

High level resolution steps

Ensure that the resource (in this case, TaxDocumentExtension_IN) is added to the appropriate security role.

Grant access to the missing resource for the role associated with the user.

Reattempt accessing the resource after making the required changes.

Detailed resolution steps

Step 1: Identify the Role and Resource

Go to System Administration > Security Configuration > Roles.

Look for the security role assigned to the user who is encountering the error (as indicated in the error message).

Check if the role includes the necessary resources[tables].

Step 2: Add the Missing Resource to the Role

Open the security role and navigate to the Tables sections.

If the resource, such as TaxDocumentExtension_IN, is missing, it must be added to the role under the Tables section, depending on how the resource is configured.

If you are dealing with custom resources, ensure they are also added correctly to the role.

Step 3: Save and Assign the Updated Role

After adding the missing resource, publish the role.

Step 5: Test the Changes

Once the roles and permissions are updated, test accessing the resource again to confirm the issue is resolved. The user should now be able to access the table/resource without encountering the error.

Output:

Once the missing resource (TaxDocumentExtension_IN) is added to the user’s security role, the user will be able to access the resource without encountering the authorization error.