Publishing extension failure

[will-jai]

Hi,
We got a question regarding iTwin viewer, our application allows users to provide clientid, imodelid, and contextid at the run time of our application and we display the corresponding iModel at runtime, for this approach we are trying to make the configuration as generic as possible. This means we cannot pre-write the code which would interact with the model or display data on it, as we don't even know what model user will try to embed.

We are hoping there would be a way where we can just pass the data either to the viewer or the iTwin server and the model would already know how to render or display it. Please advise if there is a way which can allow us to achieve this?

Thanks,
Will

[aruniverse]

Sorry, not sure if I understood the question correctly, but the Viewer component exposes a prop for the context and iModel ids, so couldnt you pass them like you want? It should just open the default view of that model. And if you wanted to override it, you theoretically could because there is a prop we expose for that, but i'm guessing that won't be generic enough.

[will-jai]

Hi,

I was trying to publish an extension via extension-cli, however, i got the below error messages. Could you please advise how I can resolve this? thanks

Without Context Id:
Unknown error: Could not find a team for the current user,
With Context Id
o Error: Unknown error from backend: Server returned status: 403, message: User is not allowed to modify using Asset/Project context

Upload to public context
o Error: Unknown error from backend: Server returned status: 403, message: User is not allowed to modify public context

[aruniverse]

@paulius-valiunas ?

@will-jai have you looked at this discussion post? #1613 (reply in thread)

[paulius-valiunas]

@calebmshafer any idea why a user wouldn't have a team id assigned?

[will-jai]

@aruniverse, I've looked at the discussion post, unfortunately, I got the above errors when I tried to publish an extension.

[calebmshafer]

The first error of not finding a Team is interesting and would need some more information to track down. @will-jai lets follow up on this part in our call next week.

The rest of the error I believe is a permissions issue. In order to publish an Extension for your Organization you must have the "Manage Extension" Enterprise-level role assigned to you. That role will need to be set by an administrator of your CONNECT Org and is under the "Extension Service" heading. We can follow up on this as well when we cover the first issue.