We're having trouble sharing a component library. The Microsoft documentation here:
says that it's just like sharing an app. But when a colleague shares his component library with me, I can see the library, but when I click on it, no components are listed. And if I try to Add more components in an app, his library and components are not shown. Then he shared his library with me as a co-owner, and then I could see his components and use them in my apps.
So this behavior is not matching the documentation. It is rather disturbing to have to share a component library with others as a co-owner. Is there an admin setting we need to change? Is there anything we can do? Thank you!
Are the components in the library using any connectors? If so, does the user have access to those connections? I just tried to reproduce your issue by sharing a menuing component library I built with another user. I shared the library with them as a user only. When they import the library they see the component and can add it to the page. This is what the other user see's when they click on Get more components at the bottom of the page.
Hi, @Pstork1 - No, there are no connectors. They are basic building-block components, originating from the blog post with 10 Reusable Components:
I can't show a screenshot of what I saw now, because the colleague has shared it with me as a co-owner, but I will ask him to change it to user-only on one, and I will post it in a follow-up.
In your app did you click on 'Get more components' to import the components into your application? They don't show up just because they were shared with you. You have to add the library to the app.
Yes, I did that. When I click on Get more components, the one that was only shared as a user (not as a co-owner) does not show up. The other ones, shared with me as a co-owner, do show up.
I'll have to try with some of the components from the article. As I said it works fine for me with a component that doesn't have any external requirements. I'm assuming you are both in the same tenant and not trying to share between tenants or environments.
I'll try pulling some of those components from Github and importing them into a library to see if I can replicate your problem.