Who is this article for?

  Users who are experiencing issues with WebUI modules.

  No elevated access or permissions are required.

You may find that in the WebUI, opening dashboards works as expected but attempting to open one of the other pages results in infinite loading. This article walks you through how to identify and resolve the issue.

1. Issue
2. Solution

1. Issue

When opening a page, the spinner appears on the page but the content never loads.

Pressing F12 and switching to the "Console" tab shows the following error:

Uncaught TypeError: Cannot read properties of null (reading 'Guid')
    at Object.<anonymous> (app.js:1:2771473)
    at Object.each (app.js:1:40899)
    at ae.getChildNodes (app.js:1:2771419)
    at ae.buildStore (app.js:1:2771091)
    at ae.constructor (app.js:1:2769801)
    at new ae (app.js:1:12360)
    at eval (eval at getInstantiator (app.js:1:114190), <anonymous>:3:8)
    at Object.create (app.js:1:115893)
    at Object.<anonymous> (app.js:1:2453671)
    at Object.each (app.js:1:40899)

This issue is usually caused by an Excel import where a parent has not been specified in the imported data.  You should always ensure that when importing Org Units a Parent Org Unit is specified.

In the desktop application, you would expect to see a single ‘root node’ Org Unit (called ‘All Org Units’ by default.

Additionally, if your user has an Org Unit specified in its properties, you will see that section of the tree displayed alongside the root node.

In the below example, the user is in the Corporate Org Unit, meaning that you should be able to see the "Corporate Org Unit" alongside the "All Org Units" root node.

However, if an additional Org Unit has no Parent, it will also appear in this tree.

This causes the WebUI to fail to display properly.

2. Solution

To resolve the issue:

1. Go to Org Structure.
2. Select the Org Unit you are having issues with.
3. Specify a Parent.

WebUI should now behave as expected.