Entity not found when trying to add a route on a Thing Template

[JD_8606834]

Hi all,

we are facing an issue when adding a service on a Thing Template.

We created a Thing Template which is based on the ODataConnector Thing. A new Thing should use the template by calling its services. So the inherited chain looks like this:
Thing Test-TestTemplate-ODataConnector

But when trying to add a new service to the TestTemplate and by adding a route, the following errors pops up:

We did a lot of research and found some similiar issues, which were all related to missing access rights.

So we assigned all groups that were suggested but still no luck:

TestTemplate uses ODataConnector

TestTemplate Permissions Visibility

TestTemplate Permissions Visibility Instance

TestTemplate Permissions Runtime

TestTemplate Permissions Runtime Instance

TestTemplate Permissions Designtime

TestTemplate Permissions Designtime Instance

Does anyone have an idea, how to fix that error?

Thanks,

Jürgen

[PaiChung]

What does the service look like you are trying to execute?

Usually if you are trying to execute a runtime service, you would do it either on the Thing Thing[ThingName].Service or me context me.Service

I'm curious why you are trying to execute something on the ThingTemplate

[JD_8606834]

We want to add a service on the template, so that it can be used from different things which all dervive from the template.

The service itself will then of course be executed on the thing, not on the template

[nmutter]

You may want to describe it simpler (basically you stated it with a lot of additional infos which may be confusing):

1. Create a new ThingTemplate with baseTemplate ODataConnector

2. Save the ThingTemplate

3. Now -in edit mode- add a new service and select "Route" 

4. Error is shown

I assume the error may be because no endpoints are defined:

But I did not look into it deeper - just tried to reproduce. Maybe someone can help from here who knows the ODataConnector

[JD_8606834]

Thanks for your investigations and the clarification. But in our situation, there are endpoints on the related thing available.

[nmutter]

as a side note: when you think you have a permission issue just try it with Administrator user. If the issue persists you do not have a permission issue.

[JD_8606834]

We are already using a Administrator user. I was just trying to point out that usally permission issues were the cause for others who had similiar issues.