Skip to main content

Notifications

Power Apps - Power Apps Experimental Features
Answered

New Analysis Engine

(5) ShareShare
ReportReport
Posted on by

Similar to the dependencies between cells in a spreadsheet that drives recalc, Canvas apps depend on understanding all the dependencies between properties of controls so that data can flow between them properly and efficiently.  We call this process "dependency analysis" and it is something that Studio is doing all the time in the background while you are editing an app.

 

For more than a year, we have been rewriting the analysis engine to both perform better and to optimize the results.  The result is that complex Canvas apps that can take minutes to load should load significantly faster.  It is a major change, at the very heart of Canvas apps, that we have been working on for over a year.

 

We are very excited to announce that this feature is now available as an experimental feature for your testing and feedback.  Please make a copy of complex apps, turn on this setting, see if you run into any problems in Studio and at runtime, and provide feedback here in the forum.   

 

Do not use this feature in production!  There could be subtle behavior differences that will take time to discover, just because the app loads and saves doesn't necessarily mean all is well, some testing is needed too.

 

Thank you!  And with your help we hope to turn this feature on for everyone soon.

 

GregLi_1-1701804999605.png

Categories:
  • CU04020414-0 Profile Picture
    CU04020414-0 2 on at
    New Analysis Engine
    I could see some issues.
     
    Code writtein OnStart property not runnuing completely. Same code works if we turn off the feature.
  • ShantanuP Profile Picture
    ShantanuP on at
    New Analysis Engine
    @alexsolexToo, Thanks for reporting the issue. Sorry that you run into this issue. Can you please provide more details about your issue? The data columns which were not fetched from dataverse, used anywhere in expressions in your app. If possible could you please provide a monitor trace for your app and send it to shpakh@microsoft.com? This would help us to investigate the issue.
  • DeeTronSEAM Profile Picture
    DeeTronSEAM 396 on at
    New Analysis Engine
    I tested out the NAE on a large app and had some errors where it couldn't determine the datatype of a field in a collection and threw an error, even though there was only two refences to the narrow collection.  Got rid of the error using a well-worn "trick" of having an "object definition" ClearCollect that fills a single record in the collection with a value of the datatype we want the field to be.  Then clearing that collection before going onward in the app where the original uses of the collection remined and which then didn't throw the NAE.
     
    But even though the app would run after that, we eventually discovered that screens with a large assortment of controls (e.g. two galleries with 10 to 50 controls on each card in them) which worked fine on the old analysis engine (OAE ?) now crashed the app when run on our gen 8,9, or 10 iPads.  This is the infamous "ios closed your app due to CPU or memory pressure" fun.  I.e. it isn't that the app's code crashes, it's that whatever the NAE does during runtime is pegging the memory or CPU on the iPad in a way that never was a problem with the OAE.
     
    Obviously, there's a well-established "best practices" to limit the number of controls on a screen. But, rules are meant to be broken and best practices to be ignored at times, no?
     
    Regardless, this app has been working for over a year but is now is facing a death sentence if the NAE is forced on us at any point.  We have disabled the NAE and for now the app is working.
     
    Please address the resource hogging the NAE seems to be causing as compared to the OAE, or allow us to stick with the OAE until we have plenty of time to migrate out of PowerApps for this app (and maybe others because of the uncertainty, cost, and frustration this backwards step is causing us and the client).
  • alexsolexToo Profile Picture
    alexsolexToo 37 on at
    New Analysis Engine
    I test the new engine every powerapps version but there is nothing new : my app does not have any code error, but some data columns are not fetched from dataverse. So, even without any noticeable error, the app does not work properly as intended. 
  • IAmIntractable Profile Picture
    IAmIntractable 225 on at
    New Analysis Engine
    I also agree with the poster below that fixing the Intellisense bar is important. I feel it is more important than the New Analysis Engine. If anything, dealing with the new engine's inevitable errors makes the issues with Intellisense standout. Seven months have passed since people started complaining about the Intellisense changes.
  • IAmIntractable Profile Picture
    IAmIntractable 225 on at
    New Analysis Engine
     
    Can provide more detail on what these issues are as I cannot find a description of them. Especially the first one:
     
    - Component properties with parameters returns null value [Fix rolling out now]
     
    - Reset function error when used across screens [Fix rolling out now]

    - Pre-loading not needed screens [Fix rolling out now]

    Collections cycle type resolution issue
  • BaptisteW Profile Picture
    BaptisteW 99 on at
    New Analysis Engine
     
    You said "@BaptisteW, Thanks for the report. This issue appears to be one we're aware of, with the GroupBy statement. Under the hood, it's the same issue as the ShowColumns one that other posters have mentioned, and should be fixed in in version 3.25013.".

    However, I just tried switching to the version 3.25014.13 and I still get the same error.
  • Verified answer
    CU31012106-0 Profile Picture
    CU31012106-0 10 on at
    New Analysis Engine
     
    This feature should not have been enabled by default, as it has caused numerous issues and sends a negative message, especially to clients who are still exploring or adapting to the platform. Several times, I had to inform my clients that the platform is experiencing problems due to this feature.
     
    And on top of it it got enabled even after I disabled it manually for each custom page. Please have a loot at my post here.
     
  • BP-19081954-0 Profile Picture
    BP-19081954-0 30 on at
    New Analysis Engine
    Similar to @AndersonLimabr referencing a combobox within a form and calling a related column does not work with the NAE turned on.
     
    Datasource is Dataverse, form is connected to the "Projects" table. One column in that table is a lookup column from the related table "Opportunity Status". As such, the form displays the primary name column of "Opportunity Status" in a combobox "DataCardValue92"
     
    I am using the following code to call a related column in "Opportunity Status" called "Projects Request Number"
    DataCardValue92.Selected.'Projects Request Number'
    The data in the field is a text string "yes" (without the quotes). But it returns the value "blank."
     
    It works correctly with the NAE turned off, but fails with the NAE turned on.
  • Wired4Sound Profile Picture
    Wired4Sound 19 on at
    New Analysis Engine
    Sort of related since NAE seems to make these behaviors worse.

    This impacts pretty much everyone.  Could you PLEASE fix these annoyances that suck up more time than they save, regarding behavior of the formula bar.

    Here is a nicely compiled thread.   

    This is in regards to tab not working as intended, enter not working as intended, hint box covering half the screen, hit box giving every option under the sun instead of just options that are relevant and usable.  etc.  It's a mess.

    PowerFX Formula Bar Issues Megathread : r/PowerApps

    I find myself CONSTANTLY backspacing to fix automated, even when a suggestion is correct, it still leaves whateveryou started typing and adds it suggestion in addition to it.  Example.  Typing Full, you see 'Full Name' come up, you select it and you end up with Full'Full Name' instead of just 'Full Name'  So you situate your mouse to full the first Full.  The intelligent suggestions list EVERYTHING across all suggestions instead of suggestions that make sense.  Etc Navigate(sc should just bring up your screens  and not every single property of every single component.  It used to do this until NAE came out.  Not sure if related.  I know turning off NAE makes it more tolerable.

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

Microsoft Kickstarter Events…

Register for Microsoft Kickstarter Events…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Announcing Forum Attachment Improvements!

We're excited to announce that attachments for replies in forums and improved…

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 145,304

#2
RandyHayes Profile Picture

RandyHayes 76,287

#3
Pstork1 Profile Picture

Pstork1 64,703

Leaderboard

Featured topics