Skip to main content

Notifications

Announcements

Welcome to the Power Platform Communities - Lets Get Started!
Announcing new navigation menus and the Engage with the Community forum!
News and Announcements icon
Community site session details

Community site session details

Session Id : ZdEr1S1EY0DMk+C6gYRk4M
Power Platform Community / Forums / Power Apps - Building Power Apps / Issues with integratin...
Power Apps - Building Power Apps
Unanswered

Issues with integrating PowerApps with Custom Connector in Studio Mode

Like (0) ShareShare
ReportReport
Posted on 23 May 2022 13:56:24 by sthota 139
Hello Team,
 
We are trying to connect to the Azure APIM instance through PowerApps. We were facing CORS issues in testing the custom connector response as well as hitting the same API through the APP URL in published mode.

 

We were able to resolve the above issues by referring to a couple of articles (https://powerusers.microsoft.com/t5/Connector-Development/Property-quot-quot-type-mismatch-Expected-...
) by adding https://flow.microsoft.com and https://apps.powerapps.com. URIs to the CORS policy.

 

However, we are still having issues with loading the data in PowerApps Studio mode. We tried adding the below URLs to the CORS policy after debugging in the network tab without any luck.

The error that we are seeing in the studio mode has been attached. 

It would be great if you could share your insights into this issue.

Thanks,
Srinivas
Categories:
Connecting to Data
Connectors
CORS.png
Custom connector ...
  • Community Power Platform Member Profile Picture
    Community Power Pla... on 21 Mar 2023 at 12:41:41
    Re: Issues with integrating PowerApps with Custom Connector in Studio Mode

    Hello Srinivas,

     

    I was facing the same issue and was able to work around the issue by allowing all origins in the CORS policy. Like so:

     <cors>
 <allowed-origins>
 <origin>*</origin>
 </allowed-origins>
 <allowed-methods preflight-result-max-age="300">
 <method>*</method>
 </allowed-methods>
 <allowed-headers>
 <header>*</header>
 </allowed-headers>
 <expose-headers>
 <header>*</header>
 </expose-headers>
 </cors>

     

    The call works with this configuration, but is obviously not secure and cannot be used in production. 

    Were you able to find the correct URLs to be allowed for the connection to work?

     

    Thanks,

    Shridhar

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Welcome to the Power Platform Communities - Lets Get Started!
Announcing new navigation menus and the Engage with the Community forum!

Quick Links

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

🌸 Community Spring Festival 2025 Challenge Winners! 🌸

Congratulations to all our community participants!

Warren Belz – Community Spotlight

We are honored to recognize Warren Belz as our May 2025 Community…

Leaderboard > Power Apps - Building Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 254 Most Valuable Professional

#2
MS.Ragavendar Profile Picture

MS.Ragavendar 132

#3
stampcoin Profile Picture

stampcoin 117

Overall leaderboard

Featured topics

Gallery Tabs - Show or Hide Tabs based on Field Value
How to patch multiple records at once
Enable Copilot for end users in model-driven apps

Product updates

Microsoft Power Platform Community release plans