Answered

Unexpected error-- isFeatureEnabled: Method not implemented

(3) Share

Report

Posted on by JenniferK

167

I'm building a Page for my model-driven app. Up until yesterday it was working fine. Today I opened it to edit and received this message: isFeatureEnabled: Method not implemented. And now my Page is ignoring the recordId I pass it in a param. I did some testing and it appears that my App.OnStart() event is no longer firing.

I know that App.OnStart() is being deprecated for navigation. But surely it can still be used for parameter processing, no? Could this be a symptom of preview nature of Pages? Did MS push an update that broke App.OnStart() for Pages?

In any case, if I can't use App.OnStart() to initialize variables, where should I do it?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (13)

Answers (1)

Sort by

Drew Poggemann 9,287 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Hi @JenniferK ,

I have not dug into this a lot, sorry, but thought I would pass this article along if you have not been through these details, hopefully something is helpful: https://powerapps.microsoft.com/en-us/blog/app-startscreen-a-new-declarative-alternative-to-navigate-in-app-onstart/

Was this reply helpful? Yes No
Hyperlance 14 on at

Like (1)

Report
Copy link

Link copied!

@JenniferK we experienced this morning as well, and like you use the app.onstart method to initialize variables. This only appears to be Dataverse related apps i.e. dataverse for teams

Also @dpoggemann we have apps that were created the only in the past 2months are this is occuring.

Was this reply helpful? Yes No
JenniferK 167 on at

Like (0)

Report
Copy link

Link copied!
This is a new Page so it had no legacy settings. Navigate() was not being used. This is my App.OnStart:
Set(oppID, Mid(Param("recordId"),2,36)); Set(entityName,Param("entityName"));
The article you linked to states:
Declarative road ahead: Named formulas
App.StartScreen is just our first step. There are two other important new declarative features in the works.
How many of you use Set in App.OnStart to setup global variables? Ok, everyone raised their hand. What if instead of writing:
App.Onstart = Set( ThisUser, LookUp( Users, Email = User().Email ) )
You instead wrote:
ThisUser = LookUp( Users, Email = User().Email )
I know, yet another very nuanced difference. In the second case, we are defining a named formula rather than using the Set function. This is equivalent to defining a name in Excel by using the formula bar or the Name Manager.

My further experimentation seems to indicate that Set() is no longer functioning at all, anywhere in my app. It looks like I may have to use these new Named Formulae. So where do I put them?

Was this reply helpful? Yes No
AR_LT 5 on at

Like (0)

Report
Copy link

Link copied!

Experiencing this too since this last night. Set() in App.OnStart still works for me. I use StartScreen all the apps where I have this error (they are all fairly recent). There is no clue as to what is causing this and it would be nice to get insight as to what is causing and the ramifications.

Was this reply helpful? Yes No
Antti99 4 on at

Like (0)

Report
Copy link

Link copied!

I have the same issue as of this morning. Due to the discussion above I temporarily removed Set() functions from onStart, in vain. Looking forward to getting insight into this.

Was this reply helpful? Yes No
westerdaled 672 on at

Like (0)

Report
Copy link

Link copied!

I am getting the same issue testing out Rezza's recent Dataverse Expenses sample. Note, I don't have anything in my App.OnStart other than Collect() function .

Was this reply helpful? Yes No
Spamrancher 345 on at

Like (0)

Report
Copy link

Link copied!

I am seeing this same error in a Custom Page I started developing a few weeks ago. Just started seeing the message within the last week. As far as I can tell, it's not impacting my app in any way: my variables and collections that I have in App.OnStart are still running. Passing a parameter between screens is still working.

Has anyone put in a support ticket with Microsoft about this?

Was this reply helpful? Yes No
RTB_10 89 on at

Like (0)

Report
Copy link

Link copied!

Working within Teams and using Dataverse and receiving the same message as described.

Was this reply helpful? Yes No
FLOWPA 85 on at

Like (0)

Report
Copy link

Link copied!

Same error here today.

@JenniferK wrote:
I'm building a Page for my model-driven app. Up until yesterday it was working fine. Today I opened it to edit and received this message: isFeatureEnabled: Method not implemented. And now my Page is ignoring the recordId I pass it in a param. I did some testing and it appears that my App.OnStart() event is no longer firing.

I know that App.OnStart() is being deprecated for navigation. But surely it can still be used for parameter processing, no? Could this be a symptom of preview nature of Pages? Did MS push an update that broke App.OnStart() for Pages?

In any case, if I can't use App.OnStart() to initialize variables, where should I do it?

Make sure StartScreen propery is visible:

StartScreen property will not appear in the list of properties when the retired option Enhanced formula bar is turned on. To turn Enhanced formula bar off, go to Settings > Upcoming features > Retired > turn off the Enhanced formula bar switch when you want to use StartScreen property. (reference)

For now you can initialize global variables in any behavioral formulas ( OnSelect, OnVisible, OnHidden, and other On... properties)
I have changed most of my variable initialization inside Screen OnVisible.

Declaring global variables: Set function and global variables

OnStart retired doc: https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/functions/object-app#onstart-property
StartScreen doc: https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/functions/object-app#startscreen-property

Was this reply helpful? Yes No
Verified answer

Spamrancher 345 on at

Like (2)

Report
Copy link

Link copied!

I was on with Microsoft Support today and brought up this error. I noticed that I haven't been seeing it the last couple of days and there is a new Authoring version. He indicated that the new version fixed this problem.

Was this reply helpful? Yes No