App Engine STudio Workspace Not Loading Home Page

[Felipe Albino]

I created a custom app using AES and configured a Workspace. The Workspace is pretty standard, has a Home and a Lists tab.

When I deployed it to my Test environment, everything on the Scoped App got moved up... but there is only one issue: the Home page of the Workspace does not load. The Lists view works fine, but the Home page with the reports is stuck.

I thought that something must of gone wrong when I initially create the Workspace, so I created a new Workspace and delete the old one. Promoted the application to my Test environment, and again the Home page does not load.

I am unable to manage or view any details of the Workspace in my Test environment because the Workspace record itself does not show up in the Workspace Experience module.

Has anyone run into this issue or know a way around this? I can't edit or do any changes to the Workspace in the Test environment because it was developed in Dev. When I open AES in my Test environment, the Application is not available.

[Felipe Albino · Accepted solution]

Updating this thread with the issue and fix we found:

When our application got moved to the test environment via the Pipeline deployment, the PAR Dashboard did not bring the PAR Dashboard Permissions or User Metadatas with it.

So we had to manually export and import those permissions and matadatas in our upstream environments to make the Workspace work again.

I hope this helps anyone that runs into this issue.

[Matt Hernandez]

Hello, I have this issue too, with a custom workspace just made with AES. Deployed to Test instance and the home page won't load.

But where is this permission/metadata is stored, which you speak of?

Thanks, for any help.

[Felipe Albino]

Hey Matt,

Check the PAR Dashboard Permissions (par_dashboard_permission) table. That was the issue I had, the dashboard/roles needed didn't move upstream.

I hope this helps!

[Matt Hernandez]

THHANK YOU!!! I checked and the user permissions had moved upstream, but then I looked for a similar table to match your "metadata" statement, and found [par_dashboard_user_metadata].

And _that_ was where I found a row missing. Awesome, this made my day!