New Analysis Engine

[GregLi]

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.

[ShantanuP]

@PeterCBell_au , Have you tried the monitor tool?
https://learn.microsoft.com/en-us/power-apps/maker/monitor-overview

New analysis engine is an experimental release which we plan to preview soon. You can publish the app using new analysis engine and use it. We generally recommend not to use experimental features in production apps as those feature could break or not ship at all. In test environment, you can use it. We do plan to release new analysis engine in preview though soon.

[WiredForSound]

Please see this post.

No data in collection column after publishing? : r/PowerApps (reddit.com)

I still have the barebones app with the bug in it.   Let me know if I can do anything to assist with helping you resolve this bug.

[lesaltzm]

Hi @WiredForSound. Can you upload that barebones app here so we can take a look at it? It sounds similar to an issue that is addressed in an upcoming release, but it'd be good to take a look and make sure. 

[WiredForSound]

See attached. 

[Sergii24]

Looks like there are still some bugs to fix: once I turn a new feature on (no other changes to an existing app), Patch() function is not working anymore. I get the following error:

Had to dedicate few hours to catch this error caused by turning on "New Analysis Engine"...

[ShantanuP]

@Sergii24 , This looks to be a runtime error with Patch function. Can you please share your session id and the Patch expression that you have which is generating this error? 

[PeterCBell_au]

For what its worth;

1) Debug logging. The process of identifying bugs in apps leaves a great deal to be desired. Complex apps with their data connections shared with the support team are problematic for tech support. They have to try and understand the app and dont have access to the data. Hence, requests that the user who raised the issue replicate the issue with a barebones app. In the meantime the user hopes the dev team finds a bug and the next release sorts the issue. Please see my previous post. 

I think the ability to start a monitor (similar to sysinternals debugview) before opening the editor (edit with logging) with the editor writing out what it is doing (eg. Formula 'x' evaluated, record schema 'recname' set to ..., etc), as well as allowing the user to write out their own messages (eg. Log("recalc totals running")). At least the user and the dev team would have a better chance.

2) Record Schemas. Secondly, I think their is something fundamentally broken with the internal processes defining, updating during editing,  and assigning types for record structures .

On the one hand, it is great that you can just enter {a:1,b:"text",...} and powerapps takes care of assigning types. It must be a difficult task since the editor looks though the app and deduces what the schema is and also dynamically updates that during editing BUT this breaks unpredictably on occasion and we are left with all sorts of errors that are resolved by retyping a property name, or sometimes in components deleting a property and then recreating it exactly as was.

Since there isnt a way a define a records schema explicitly this also creates a roadblock for UDF to accept record/tables parameters.

What I suggest to explicitly define and reveal record structures is;

 For components data parameters of type record/table a function called Schema() be implemented. It could either be left blank --> determines schema from default value  (ie. {a:0,b:"text",..}  or Defaults(tablename) ), or be entered in the form {a:columntype.Integer, b:columntype.string, c:columntype.SharepointChoice, d:columntype.SharepointAttachments, e:columntype.SharepointLookup,etc)

 For other record schemas (eg. defined by a forall, patch, collect, set, etc) allow the optional use of;

    SchemaDefine(rec,{a:columntype.Integer, etc})

   And if the record 'rec' is used elsewhere in the app in a manner that conflicts with the schema (as either explicitly defined or deduced) , then an error is raised (eg. Error: Record 'rec' inconsistent with schema '{a:columntype.Integer, etc}'

 For UDF, define as.. 

    FunctionName(p1:DataType1, p2:DataType2, p3Rec:Schema({a:integer,b:string,...}) ):OutputDataType

 To reveal the record structure as internally defined by powerapps implement

    Text(rec,"Schema") --> create a string revealing the schema

3) Sharepoint Internal Column Names. I have mentioned this before- sharepoint tables and their internal column names are a PITG. Since sharepoint doesnt allow internal names to be redefined they can end up as url encoded if at some point in the column names lifetime a space, dash, etc was used. Can the use of the column displayname or the column internal name be enabled when referring to record columns?

[Zacharie_Cortes]

I turned on the feature, ... my app won't open in editor mode. 

I tried to open it with multiple internet browser and different computer too. I had to restore an old version.

[lesaltzm]

Hi @Zacharie_Cortes, thanks for the report. Can you provide a copy of the app, or if not, a session id of it not loading? That’d be very helpful in finding and fixing the issue. 

[claytsch]

You have a lot of the same concerns/recommendations that I would have.  Record Schema is so difficult in PowerApps-- especially when creating custom/nested record Structures.  I prefer to use domain structure for my apps just to make organization easier and would love for nested/recursive records and functions to be easier to define.

Being able to define structure of a Record with all of the different field types without actually setting the record/variable would be a huge help.  Inconsistent record errors are probably the thing I spend the longest time trying to resolve because I can't easily set Blank values for all field types.