Cubes are not visibles on Apliqo UX

Hi all,
We are having an issue with Apliqo UX on the server. When we create applications, cubes (even those from the content store) are not visible as you can see below.

Do you have any idea about how to resolve this problem ?
Thanks in advance.

Check in the Settings.json file of this new Webapp, if the “allowedRestPaths” is blank, it might be in case of new installations or new webapps, then you need to update it with all the Rest paths.
it will be located on …\WEB-INF\Config

This is for the latest version:
https://downloads.cubewise.com/Apliqo+UX/2024.02/2024.02+-+allowedRestPaths.txt

Hello @rmazziero
The “allowedRestPaths” is already filled.

Thanks for your help.

Hi @cngampessi it’s not whether the allowedRestPaths was empty (it would never be empty) but whether it contains all the values that it needs to. There are sometimes feature updates which require this parameter in default.constant.js to be updated with new path(s). If paths are missing which are needed in rest calls by some features, then those features won’t work. All the needed rest paths are listed in the release notes.

Not that I think this is relevant in your case but this is what Rodrigo meant.

the main API path that needs to be in the settings.json is following

{
    "path": "/ExecuteMDXSetExpression(.*)",
    "method": "POST"
  },
  {
    "path": "/ExecuteMDXSetExpression(.*)",
    "method": "GET"
  },

, please investigate the network call via developer tools to find why the call fails, preview tab should have the message response.
Please check

Hi @cw-ch-scott

Thanks for additional the additional information.

Hi @ishapiro
This is what’s in the setting.json

  "allowedRestPaths": [
    {
      "path": "/ExecuteProcessWithReturn",
      "method": "POST"
    },
    {
      "path": "/Users.*",
      "method": "Get"
    },
    {
      "path": "/Groups.*",
      "method": "Get"
    },
    {
      "path": "/Users.*",
      "method": "PATCH"
    },
    {
      "path": "/Cubes(.*)",
      "method": "GET"
    },
    {
      "path": "/Cubes(.*)",
      "method": "POST"
    },
    {
      "path": "/Cubes(.*)",
      "method": "PATCH"
    },
    {
      "path": "/Cubes(.*)",
      "method": "DELETE"
    } ,
    {
      "path": "/Dimensions(.*)",
      "method": "GET"
    },
    {
      "path": "/Dimensions(.*)",
      "method": "PUT"
    },
    {
      "path": "/Dimensions(.*)",
      "method": "POST"
    },
    {
      "path": "/Dimensions.*",
      "method": "PATCH"
    },
    {
      "path": "/Dimensions(.*)",
      "method": "DELETE"
    },
    {
      "path": "/Cellsets(.*)",
      "method": "POST"
    },
    {
      "path": "/Cellsets(.*)",
      "method": "DELETE"
    },
    {
      "path": "/\\$metadata.*",
      "method": "GET"
    },
    {
      "path": "/Threads.*",
      "method": "GET"
    },
    {
      "path": "/Threads.*",
      "method": "PATCH"
    },
    {
      "path": "/Threads(.*)",
      "method": "POST"
    },
    {
      "path": "/ExecuteMDX(.*)",
      "method": "POST"
    },
    {
      "path": "/ExecuteMDXSetExpression(.*)",
      "method": "POST"
    },
    {
      "path": "/ExecuteMDXSetExpression(.*)",
      "method": "GET"
    },
    {
      "path": "/Annotations.*",
      "method": "GET"
    },
    {
      "path": "/Annotations(.*)",
      "method": "DELETE"
    },
    {
      "path": "/ErrorLogFiles(.*)",
      "method": "GET"
    },
    {
      "path": "/BeginChangeSet",
      "method": "POST"
    },
    {
      "path": "/EndChangeSet",
      "method": "POST"
    }
  ]

When I connect the application to an older instance, I can only see the control cubes in both instances.



But when I connect it to a recent instance, I can’t see anything in both instances.

When I click on cube settings, I can see the contentstore control cubes.

It sounds like it could be a permissions issue. Does your user have rights to the }Cubes dimension and read access to elements in the }Cubes dimension?

Yes i am admin user.

Hi all,
I did a test by changing the values of the variables PortNumber, HTTPPortNumber, ClientMessagePortNumber in the file tm1s.cfg for the model tm1 and it seems to work now.
image

We can say it was due to the port.

Thanks a lot for your help.