Helpdeskmodule - Endpoint does not exist on the backend

[mru-ipg]

Endpoint does not exist on the Backend

[mru-ipg]

On the Component of the HDS-Project this.entitySchema = this.hdsApiService.typedClient.PortalCalls.GetSchema(); The hdsApiService is serving an Error because of 404 it seems like the Endpoint does not exist on the backend.

[Mathnstein]

Hi @mru-ipg - I'm not sure how you wound up in a state where you have the frontend built but without the api endpoints but I would re build the HDS project.

Build ./HDS/build.proj --> Produces the imx-api-hds.tgz that then will go into the assemblies folder and expose endpoints to the server

Then rebuild and serve the frontend

npm run build:watch:dynamic hds --> This part I think you already had correct but its an additional verification step, this should fail if the imx-api or endpoints don't exist.

[mru-ipg]

/HDS/build.proj and where to find this file, coul you provide more information, the Angular part is working fine but the Endpoint does not exist like a dll ore something

[Mathnstein]

Apologies - Ignore my comment on building the imx-api-hds, that is already available on the repo here.

Grab this file from the repo here under imxweb/imx-modules/imx-api-hds.tgz, and stick that in your assemblies folder under Assemblies/imx-modules.

Then restart your server (locally or remote), this should give you the endpoints in the admin portal/swagger api documentation.

My suspicion is that the package was missing or had built incorrectly such that your final assemblies didn't have it loaded.

[mru-ipg]

I mean the tgz file provides just TypeScript Classes and Interfaces for the Frontend, either is here the problem that a .dll file does not exist which is responsible for the hds module.

PS: The .dll file ist responsible to show up an endpoint in the swagger, like we do it when we create a custom endpoint. I mean there is no dll for the Hds module

[Mathnstein]

I see - yes the issue is further back and not related to the github code, it may be that the HDS module is not installed in your database or that the API plugin is not loaded.

For handling of installations / setup I'd refer you to the setup guide.

If this is not helpful then I would suggest opening a support ticket.

Apologies for the red herring ;)