Unanswered

New Enchanced Component Properties breaks app

(0) Share

Report

Posted on by JeBy

Hello,

I know there's already a topic on someone's specific use-case, but I simply wanted to alert that the new enhanced component properties feature is completely breaking my app. I had multiple functions that were using data that are now breaking (as data is not allowed in functions anymore) and the app breaking with all these errors is really impacting my business.

I know there is a way to disable the feature fully, but it is asking me to delete the components that have "Enchanced properties". The problem is, I just want to get back to still using the first wave of enhanced properties I created these "Functions" with (which was very stable - hence why I used it in production) and thus not abandon the enhanced properties fully as these "simple" functions really improve performance in my app. Is there a way to this?

If not, is there any way to use the new enhanced component properties feature (Action, Event, Function, Data) by modifying my existing functions so I can use data again? I'm really stuck here...

Thanks!

Categories:

Experimental features

I have the same question (0)

All responses (17)

Answers (0)

ShantanuP Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

@JeBy , Can you please share some examples of what your functions? What error are you getting?

Was this reply helpful? Yes No
JeBy 26 on at

Like (0)

Report
Copy link

Link copied!

Hello ShantanuP. Thank you for your reply. Basically all my functions that used to be able to access my Dataverse tables to return a record, table, etc. now have the error "_Table Name_ is not recognized" on every direct Dataverse table call inside a function. This has been happening since the new feature of disabling direct data access in Functions were pushed into the "Enchanced Component Properties" experimental feature.

Was this reply helpful? Yes No
ShantanuP Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

@JeBy , Function properties currently restrict access to dataverse tables. Is it possible for you to move that logic to Action properties?

Was this reply helpful? Yes No
JeBy 26 on at

Like (0)

Report
Copy link

Link copied!

When I try to transform my function into an "Action" I get the error "Behavior function in a non-behavior property. You can't use this property to change values elsewhere in the app.". This is in a sitation where I try to use the result in a ForAll function. No data at all is available to transform in this new "Function" feature. Not even collections...

Do you have any idea why these changes were pushed onto the year-old (or more) "Enhanced component properties" feature and not on a new experimental feature? That would have prevented breaking existing makers logic tbh.

Was this reply helpful? Yes No
ShantanuP Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Are your functions work with parameters? If not then is it possible to use named formulas instead to share the common logic that you have instead of using functions? We plan to support this in future for function properties.

https://powerapps.microsoft.com/en-us/blog/power-fx-introducing-named-formulas/

Was this reply helpful? Yes No
JeBy 26 on at

Like (0)

Report
Copy link

Link copied!

Yes, nearly all of my functions use parameters to transform data into a record or table result.

Is there no way to revert back to the old functions or even enabling using data flow in these new functions for makers that have used data in their functions in order to not break apps?

Was this reply helpful? Yes No
PeterCBell_au 109 on at

Like (1)

Report
Copy link

Link copied!

This continues to be a significant issue for me. I am not able to publish any updates and am checking daily to see if the issue has been resolved. Using named formulas (which are do not support parameters at this time) is not a substitute for components with functions that use parameters.
Please see the response from Joris (powerusers.microsoft.com/t5/Power-Apps-Experimental-Features/Components-Functions-June-Expermental-Breaks-Code-Libs-created/td-p/2200990) where he stated that he would ask the team to release the block (ie. restore previous functionality) that was put in place with the latest wave (I can only assume the block was placed assuming that UDF's and/or callbacks would have been implemented with this wave and be able to replace the component functions with parameters).

Was this reply helpful? Yes No
ShantanuP Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

As we fix to allow referencing function properties, you can currently work around it by making parameters as data properties and converting current function property to output data property.

For example, Func(Param1, Param2) need to be converted to

- Param1 data property

- Param2 data property

- Func output data property

Was this reply helpful? Yes No
HISD_JSO 31 on at

Like (0)

Report
Copy link

Link copied!

Moving my reply to a more appropriate tread. Nothing so see here.

Was this reply helpful? Yes No
PeterCBell_au 109 on at

Like (0)

Report
Copy link

Link copied!

I am sorry, but this is in no way a work around.
Simply, it wont work.
Please let us know what the roadmap is to re-enabling the previous functionality or its equivalent.

Was this reply helpful? Yes No