web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Refused to get unsafe ...
Power Apps
Answered

Refused to get unsafe headers (in D365 form).. PCF that binds to a key

(0) ShareShare
ReportReport
Posted on by Microsoft Employee

Hi guys,

 

I'm just working on a keybinding example PCF.

https://github.com/365lyf/PCFControls/tree/master/KeybindingExample  (solution file and code within)

 

It works within the Test Harness.  See uploaded video of it working:

https://youtu.be/5KIuafXf39s

 

However when it is deployed to a D365 form,

keybind_error.PNG

i'm getting the following error.

 

F12 debug console output on Chrome.

app.js?v=1.3.1714-190430-204026:2335 Refused to get unsafe header "REQ_ID"
(anonymous)	@	app.js?v=1.3.1714-190430-204026:2335
(anonymous)	@	app.js?v=1.3.1714-190430-204026:2335
load (async)		
(anonymous)	@	app.js?v=1.3.1714-190430-204026:2335
e.send	@	app.js?v=1.3.1714-190430-204026:2335
sendPOST	@	app.js?v=1.3.1714-190430-204026:1024
e._sendRequest	@	app.js?v=1.3.1714-190430-204026:1024
e.sendQueuedRequests	@	app.js?v=1.3.1714-190430-204026:1024
e.sendEventsForPriorityAndAbove	@	app.js?v=1.3.1714-190430-204026:277
e._batchAndSendEvents	@	app.js?v=1.3.1714-190430-204026:1123
(anonymous)	@	app.js?v=1.3.1714-190430-204026:1123
setTimeout (async)		
e.scheduleTimer	@	app.js?v=1.3.1714-190430-204026:1123
e._batchAndSendEvents	@	app.js?v=1.3.1714-190430-204026:1123
(anonymous)	@	app.js?v=1.3.1714-190430-204026:1123
setTimeout (async)		
e.scheduleTimer	@	app.js?v=1.3.1714-190430-204026:1123
e.sendEvent	@	app.js?v=1.3.1714-190430-204026:1123
e._sendEvent	@	app.js?v=1.3.1714-190430-204026:1458
e._logEvent	@	app.js?v=1.3.1714-190430-204026:1458
e.logEvent	@	app.js?v=1.3.1714-190430-204026:1458
e.logEvent	@	app.js?v=1.3.1714-190430-204026:726
e.handleEvent	@	app.js?v=1.3.1714-190430-204026:726
(anonymous)	@	app.js?v=1.3.1714-190430-204026:726
e._dispatch	@	app.js?v=1.3.1714-190430-204026:726
e.ReportComponentPerformance	@	app.js?v=1.3.1714-190430-204026:726
e._reportEvent	@	app.js?v=1.3.1714-190430-204026:2039
e._sendToTelemetry	@	app.js?v=1.3.1714-190430-204026:2039
e.writeRetroactiveTimespan	@	app.js?v=1.3.1714-190430-204026:2039
e.createRetroactiveStopwatch	@	app.js?v=1.3.1714-190430-204026:1831
e._sendSlowFrameInfo	@	app.js?v=1.3.1714-190430-204026:754
e._trackFrames	@	app.js?v=1.3.1714-190430-204026:754
(anonymous)	@	app.js?v=1.3.1714-190430-204026:754
requestAnimationFrame (async)		
(anonymous)	@	app.js?v=1.3.1714-190430-204026:754
setTimeout (async)		
e._trackFrames	@	app.js?v=1.3.1714-190430-204026:754
(anonymous)	@	app.js?v=1.3.1714-190430-204026:754
e._safelyCallCallback	@	app.js?v=1.3.1714-190430-204026:2331
(anonymous)	@	app.js?v=1.3.1714-190430-204026:2331
e._onNewWork	@	app.js?v=1.3.1714-190430-204026:2331
e.trackWork	@	app.js?v=1.3.1714-190430-204026:2331
t.dispatch	@	app.js?v=1.3.1714-190430-204026:435
(anonymous)	@	app.js?v=1.3.1714-190430-204026:996
registerOngoingWork	@	1.js?v=1.3.1714-190430-204026:69
CustomControlHostRoot._onOutputChanged	@	1.js?v=1.3.1714-190430-204026:187
KeybindingExample.refreshData	@	index.ts:76

 Any ideas? thanks.

I have the same question (0)
  • Verified answer
    Greg Hurlman (MSFT) Profile Picture
    Microsoft Employee on at
    Andrew, the REQ_ID error is a known issue in Dynamics 365, and can be safely ignored—it’s not coming from your code nor the framework.
  • Community Power Platform Member Profile Picture
    Microsoft Employee on at
    Thanks Greg, so I should just wait for it to be patched out in future revision of D365 to test the control?
  • Greg Hurlman (MSFT) Profile Picture
    Microsoft Employee on at

    That error shouldn't blocking you from testing the control; I was able to build and deploy your control and have it run successfully in a production tenant of Dynamics 365. I did deploy it on its own in a solution though, so try that and see if you get a better result. If that works, and the solution with multiple controls consistently fails, please post a link to your solution file so that we can take a look.

  • Hemant Gaur Profile Picture
    Microsoft Employee on at

    We have this issue tracked and prioritized (via internal bug - 1339680 for reference) and we will address this via weekly release.  Thanks for reporting Andrew, as Greg mentioed this does not affect control developement or functionality and is incorrect error being logged by infra in browser console.

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

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 248 Most Valuable Professional

#2
Kalathiya Profile Picture

Kalathiya 209 Super User 2026 Season 1

#3
VASANTH KUMAR BALMADI Profile Picture

VASANTH KUMAR BALMADI 195

Last 30 days Overall leaderboard