Skip to main content

Faq

FAQ​

List of all NPM @asol-platform packages:

https://dev.azure.com/avaspace/feed/_artifacts/feed/feed

Errors during build/start application​

May be caused because of older @asol-platform libraries you're using. Check latest versions of all @asol-platform packages which are available, and those you are using in your application. Keep an eye of changelog for each library. There may be some breaking changes.

Licensing not working​

If you try to open Licensing page on localhost during local development, it won't work, and you get an error message. You need to try it on dev.avaplace.com or demo.avaplace.com.

In case you have errors in console or error dialog appear, in most cases there is problem with @asol-platform npm libraries. Check latest version of npm packages and update them in your project.

NPM package missing​

If you have problem start you application locally due to missing npm packages which are peer dependencies to @asol-platform libraries. This may be caused that you have older version of npm on your computer lower than v7.x.x. To check run command npm -v.

List of possible solutions:

  • Install missing npm libraries manually to your application. In Avaspace feed on Azure Devops you can see all peer dependencies to each @asol-platform packages with required version.
  • Update npm version in your computer to above v7.x.x to and retry install specific @asol-platform library.

After installing missing packages, you can check, if they are located in node_modules.

Missing licence​

You don't have access to specific application. Check if you're in the right tenant, where you have given access. Try logout and login back to application eventually refresh your access rights. When you still don't have access, try contact your project manager and ask for rights into project.

Problem with side-menu pages​

Sometimes may happen that user with specific role see (or don't see) pages in left side-menu. This may be caused with problem, when you have defined page in side-menu.authorization.json, which not exist - is not last part of url.

Another problem with menu item visibility may be caused, that you have authorization for last item in menu, but don't have authorized parent item.
Showed in example - you have page Licensing and Licensing overview in menu - Licensing is root parent item in side-menu and has Licensing overview inside as child item. Then you have need authorized page URL routes licensing-overview and licensing together to have access on Licensing overview page for specific role.

Another problem may be with missing <app-name>.Owner role in backend. By default, backend doesn't have this role defined even when frontend includes some page authorization. This can be typically problem in new application.