Notification Component -Error loading component

(0) Share

Report

Posted on by vani2000

Hello,

I am creating PCF signal R notification component. I am following the documentation from the below URL

https://powerapps.microsoft.com/en-us/blog/notification-control-using-powerapps-component-framework-and-azure-signalr/?ranMID=24542&ranEAID=je6NUbpObpQ&ranSiteID=je6NUbpObpQ-rG1oZYpRjPOWcFs3dd2a0g&epi=je6NUbpObpQ-rG1oZYpRjPOWcFs3dd2a0g&irgwc=1&OCID=AID2000142_aff_7593_1243925&tduid=(ir__0wd9xapuawkftmaokk0sohz3x32xlc6hxlhwrj3300)(7593)(1243925)(je6NUbpObpQ-rG1oZYpRjPOWcFs3dd2a0g)()&irclickid=_0wd9xapuawkftmaokk0sohz3x32xlc6hxlhwrj3300

There were 3 parts(powerapps framework-typescript, Creating function in Azure, powerapps ) in the documentation, which i have done .

But i see Error Loading Control when i use the component. Has anyone faced similar kind of problems particularly for this component or do you have any fix or advice to me.

Please let me know if i need to share any other information.

Regards

Vani

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (4)

Answers (0)

Sort by

vani2000 67 on at

Like (0)

Report
Copy link

Link copied!

Error message i get. Thanks in advance.

Was this reply helpful? Yes No
Ben Thompson 1,400 on at

Like (1)

Report
Copy link

Link copied!
The issue relates to CORS or Cross Origin Resource Sharing see https://auth0.com/blog/cors-tutorial-a-guide-to-cross-origin-resource-sharing/

Your function in Azure needs to return a Access-Control-Allow-Origin header in the response but I suspect adding just

req.HttpContext.Response.Headers.Add("Access-Control-Allow-Origin", "*");
will be enough.

Was this reply helpful? Yes No
vani2000 67 on at

Like (0)

Report
Copy link

Link copied!

Hi, Thanks for the response. Please could you let me know where should i paste the code exactly. Is it in the function which i created in Azure. if yes, that function is not editable for me.
how can i edit that ? Please could you let me know?
Thanks

Was this reply helpful? Yes No
BenediktB 50 on at

Like (2)

Report
Copy link

Link copied!

Hej,
I do agree with Ben. I would also say it is because of CORS.
As I know you can configure this in your Azure portal. When you open the Function, go to the tab "Platform features" and open "CORS" under API a flyout configuration will come in from the right. There you can add your source. I would not recommend adding a "*" there because this will allow requests from everywhere.

//Benedikt

Was this reply helpful? Yes No