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

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / PCF control solution c...
Power Apps
Unanswered

PCF control solution checker error

(1) ShareShare
ReportReport
Posted on by 8

Hello All,

I have build all PCF controls using msbuild /p:configuration=Release mode but when i run solution checker on my complete solution which includes few PCF controls and customization changes then i got below bundle.js error. How can we make our solution rid of this error in development environment.

Issue
a.top*n references 'window.top' or 'window.parent.parent'. This will likely result in cross-origin security errors when hosted outside of the primary web client. Develop an alternate approach.
Issue
For most comparisons the strict equality comparison algorithm is the appropriate choice as it will return the expected results. The strict operators, === and !==, handle null and undefined values as expected.

BhuvitaSisodiya_1-1606392329682.png

 

  • ScottDurow Profile Picture
    1,039 on at

    Hi - these kind of messages are often false positive. If you are not referencing window.top then you can safely ignore them. Strict equality operators are often best practice so you might consider looking at the occurrences. Many times however, the issues are coming from third party libraries that you have no control over and so you would ignore the issues in this situation. 

  • BhuvitaSisodiya Profile Picture
    8 on at

    Yes i am not referencing them in my control they are coming from third party library. Few months back this work fine solution checker does not give any error if we build control using msbuild /p:configuration=Release and deploy the unmanaged solution into the environment. But now it started giving error.

  • CU22071954-0 Profile Picture
    2 on at
    I had the same problem here in the project, PCF was using FluentUi and React, it reported a similar error, in fact, I realized that it was not a coding error, but rather the use of a third-party library, I found this information on this forum, It was of great help, thank you all for the information.

     

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

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Leaderboard > Power Apps

#1
11manish Profile Picture

11manish 342 Super User 2026 Season 2

#2
M Bilal Khan Profile Picture

M Bilal Khan 271

#3
Mohsin Ali Profile Picture

Mohsin Ali 239

Last 30 days Overall leaderboard