Open srivigneshj opened 2 weeks ago
@srivigneshj if I'm understanding correctly, you are not having an issue using the Creator Kit people picker component, and you're just trying to create a 'people picker' experience using a combo box, is that correct?
Are you able to list or validate whether guest user data is able to be accessed in production tenant, either from the API or in a simple vanilla repro?
@denise-msft Yes your understanding is correct. We are not using any creator kit and used Combo box in Canvas App to have people picker experience. As I mentioned in steps to reproduce, #5 The same guest users are resolving if we try from Out of the Box SharePoint List's New/Edit form.
Thanks for confirming @srivigneshj. Unfortunately, since this is an issue with the underlying Platform, we cannot assist you with this issue here. You'll have to follow up with the official Microsoft support channel you initialized. I have internally reached out to the respective product team owners to request they reengage the support ticket number you shared. If you do not get a response from them in the next week, please let me know so we can figure out a resolution accordingly.
Describe the bug Guest user accounts are not resolving in PowerApps Combo box field (people picker). This is working in LAB tenant and not in Production tenant. When we raise this issue with Microsoft (TrackingID#2407250040003792) Microsoft Canvas team suggested us to raise a support ticket at https://aka.ms/creator-kit-issues though we have not used any creator kit in the Power Apps Canvas App.
To Reproduce Steps to reproduce the behavior:
Expected behavior Any guest users should be resolved in Canvas PowerApps. This is working in LAB tenant but not in PROD tenant.
Additional context This issue was raised with Microsoft and after investigating for more than 45+ days their PG team mentioned us to create ticket in https://aka.ms/creator-kit-issues link though we are not using any creator kit in the canvas PowerApps. So surprised with Microsoft's support and still raising this ticket as recommended by Microsoft. We also requested Microsoft not to close TrackingID#2407250040003792 issues until this issue got resolved with the help of GitHub channel or some other source.