Forum Discussion

Marc_B's avatar
Marc_B
Icon for Helper I rankHelper I
5 months ago
Solved

Cross‑workspace shared dataset: users must open App A before accessing App B — How to Fix?

Hello, I have created a report, which I will call “A”, in a workspace and granted Build permission to a colleague through the app audience settings. He then created his own report, which I will c...
Need Help
  • Marc_B's avatar
    Marc_B
    5 months ago

    Hi v-aatheeque ,

    I've just unpublished the app A. So, automatically, the read+build permissions given through the app were translated into grants for the dataset.

    Thanks for your support

v-aatheeque's avatar
v-aatheeque
Icon for Community Support rankCommunity Support
5 months ago

Hi Marc_B 

Thanks for the clarification, your understanding is correct.

Even though the dataset is shared org-wide via App A, that access doesn’t fully apply to cross workspace reports until users access the app at least once. That’s why opening App A makes Report B work.
Deleting App A won’t break the dataset, but users may lose access to Report B unless another permission path is provided.

For an org-wide scenario, keeping App A published is currently the most reliable approach.

Marc_B's avatar
Marc_B
Icon for Helper I rankHelper I
5 months ago

Hi v-aatheeque ,

thanks.

I gave read & build permission to dataset A through the app to the developer of report B. He shared the app B with the entire organization. Now, if I share directly with him the report (with read & build grants) and remove the app A:

  • the model B won't be broken
  • the app B ordinary users won't lose access 

Is this correct?

Can you clarify on why you believe that keeping app A is the most reliable approach?

 

Sorry if I come across as nitpicky, but some doubts aren't simple to resolve. Thanks