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

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / How to clear "web unsu...
Power Apps
Answered

How to clear "web unsupported syntax" issue in solution checker?

(0) ShareShare
ReportReport
Posted on by 15

The below mentioned is the error that I am facing for HTML Web resource which contains java script in it.

 

         ->I am trying to export my solution so ,before exporting the solution I need to run the solution by using solution checker in the power apps. So I have run my solution in that so I got this error.

 

 

"Unable to understand the syntax of this file. We currently do not support ECMA standards greater than version 5. We may have also encountered a true syntax error in the file. Please use a code editor that performs JavaScript validation, such as Visual Studio Code, to identify the script error locations. Note that other rules were unable to run on this file so the results are likely incomplete."

  • Moreover I have validated the code using visual studio and It is error free.
  • I have even removed the ES 6 version code and made it to ES 5 (for fetch).

could some please help me in clearing this issue.

 

Thanks in advance

Thanks,

Yamini

I have the same question (0)
  • MikeHuguet Profile Picture
    on at

    I think his question was focused on Power Apps/Solution Checker and how you are running it. If you are saying that you are seeing syntax errors with your HTML generation JavaScript embedded in HTML, then this is the bug that I was mentioning earlier in this thread with the parser. The new parser will be introduced in the near future. They do not have a date yet. @Yamini_surineni 

  • MikeHuguet Profile Picture
    on at

    @DianaBirkelbach I would if they are false positives.

  • Yamini_surineni Profile Picture
    15 on at
    Hi, I am not triggering any where I am placing it in form . Thanks , Yamini
  • Ben Thompson Profile Picture
    1,400 on at

    Where is the web resource being used and how are you triggering it?

  • Yamini_surineni Profile Picture
    15 on at

    Hello,

    As there was a new release in dynamics on Friday i.e on 8th of may. Due to that release there is a new issue occurring in my html web resource . The issue is it is printing html tags instead of output in the page layout.

    Can some one help me in clearing this issue.

    Thanks in advance,

     

    Thanks,

    Yamini

  • Diana Birkelbach Profile Picture
    3,072 Most Valuable Professional on at

    Hi @MikeHuguet , 

    Yes, we have a lot of problems with Solution Checker and AppSource Certification because of using bundling & 3rd Party npm Packages in our WebResources (PCFs too): like using eval, parent.Xrm, using let & const (this is not ES5 but the all Dynamics 365 supported browsers support that).

    It makes us (the developer) spend a lot of time with justifying the implementation (to our customers and out boss), even if we didn't do anything wrong. 😥
    So we should just proceed with the AppSource Certification, even if the solution checker shows High-Issues?

    Best regards,

    Diana

  • Yamini_surineni Profile Picture
    15 on at

    Hi ,

    I have cleared those errors and I passed my solution checker.

     

    Thanks,

    Yamini

  • MikeHuguet Profile Picture
    on at

    Are you using AppSource checker?

  • MikeHuguet Profile Picture
    on at

    Are you talking about AppSource certification? The certification team is aware of false positives for some rules, including with this rule. Static analysis is not perfect.

  • Diana Birkelbach Profile Picture
    3,072 Most Valuable Professional on at

    Hi  @ben-thompson 

    I wasn't aware that we have to use getContentWindow. I know about the deprecation of Xrm.Page and about the deprecation of ClientGlobalContext.js.aspx., and that the getContentWindow is a possibility (which I didn't took as reasonable, because this means that I have to include a form-script for each HTMLWebResource on the form).

     

    But in the link about the deprecation 😞https://docs.microsoft.com/en-us/power-platform/important-changes-coming#some-client-apis-are-deprecated) is stated

    - about deprecation of Xrm.Page: 

    "Although Xrm.Page is deprecated, parent.Xrm.Page will continue to work in case of HTML web resources embedded in forms as this is the only way to access the form context from the HTML web resource."

     

    - about the deprecation of parent.Xrm

    "Use one of the following:
    a) Use a custom control created using Power Apps component framework instead of HTML web resources.
    b) On forms, use the getContentWindow method of the web resource control.
    c) If the getContentWindow method doesn't work, you can use parent.Xrm to get to the Xrm object inside an HTML web resource. If the HTML web resource is opened in a new window then you should use opener.Xrm instead."

     

    So we can use parent.Xrm, but in that case we cannot pass the solution checker and the solution cannot get the certification?

    Best regards,

    Diana

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

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Apps

#1
Kalathiya Profile Picture

Kalathiya 427

#2
WarrenBelz Profile Picture

WarrenBelz 360 Most Valuable Professional

#3
MS.Ragavendar Profile Picture

MS.Ragavendar 336 Super User 2025 Season 2

Last 30 days Overall leaderboard