Forum Discussion
Composite Model access issue
Re-Reading your problem statement, it appears that you are setting xmla access on a per user basis? I am familiar with Premium access and xmla being at a capacity setting. Either case, I think what you did was to allow xmla to Specific Security Groups, not to the entire organization. I would believe that the test user accessing the composite model would need to be listed at this capacity setting.
Double check the composite model sources, worksspaces and access.
For example
Model A in Workspace A
Model B in Workspace B
Build Composite Model with Model A in Workspace A and Model B in Workspace B and publish to any of the above workspaces, or publish to a new workspace.
The user with access to the newly created composite model, will also need access to the source models and or workspaces. If the test user is listed as a viewer in either Workspace A or Workspace B, dataset permsission should be inherrited. If the test user does not have access to Model A / Workspace A or Model B /Workspace B, they will not be able to render visuals leveraging these models.
As described above, test user getting viewer access will solve this. However, there may be scenarios where you dont desire workspace access but only want specifica dataset access, this is then when you can leverage Build Permissions for this behavior.
Thanks tctrout, in this case both model A and model B are in the same workspace, the test user has access to both models. Also while we were trying to troubleshoot we even gave the test user contributor access to the workspace which also did not solve the issue.
Re-Reading your problem statement, it appears that you are setting xmla access on a per user basis? I am familiar with Premium access and xmla being at a capacity setting. Either case, I think what you did was to allow xmla to Specific Security Groups, not to the entire organization. I would believe that the test user accessing the composite model would need to be listed at this capacity setting.
