For Choice fields the Value string is replaced with 'Material Cost' string

(1) Share

Report

Posted on by TudorS

Suddenly the code in the app is changed by an unseen force for choice fields: instead of FieldName.Value it appears FieldName.'Material Cost'. What the hack is this? I'm working in a cloned instance of an app that works in production even if it has the same code changed as described below. The entire app contains this kind of Find and Replace of ".Value" with ".'Material Cost'". The production instance that is at the release 3.25021.9 doesn't throw errors, but the dev instance throws errors. My dev instance has changed from release 3.25021.9 to 3.25022.8 at this time: 2/25/2025, 2:00:35 AM

Backend is SharePoint Lists. The varFormData variable store one the entire item/record from a SharePoint list.

Is this a hacking done by some smart bad guys or a bad release from MS?

Production doesn't throw erros:

But Dev instance throws errors:

Something or someone has changed the code while I was coding the app. I'm the only one working with this app, no collaborators, co other colleagues involved. "Value"

was replaced by "'Material Cost'" while I was working in another screen for a new request to deploy these days.

Categories:

Building Power Apps

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

WarrenBelz 153,084 Most Valuable Professional on at

Like (0)

Report

Disregard - wrong thread

Was this reply helpful? Yes No
Michael E. Gernaey 53,433 Super User 2025 Season 2 on at

Like (0)

Report

Hi @TudorS,

Hmmm.. So apologies I dont know if this is SharePoint or Dataverse. I am going to guess SharePoint, because you didn't specifically leverage the Choice context for comparisons which would be required in Dataverse.

The thing is. I would need to see the varFormData collection.object to have a bit more details to help you with because its possible that due to that it could force you to use what you have, but I would still expect you to add a .Value at the end end of the new stuff.

My guess is production hasn't been updated yet.

But can you please share a view of the varFormData and also can you please share what the error says. I realiaze where it is, but is it saying material cost isn't a string or not valid as a "thing" at all or what?

Was this reply helpful? Yes No
TudorS 14 on at

Like (0)

Report

@WarrenBelz: I'm afraid you didn't read correctly my issue description. The problem is from the Microsoft backend cloud code storage. Something has replaced the Value string with another word in my whole app's code. There are a lot of Choice type fields and instead of FieldName .Value = "something" it appears now as FieldName .'Material Cost'= "something" and it worked a few hours ago and now suddenly it doesn't work due to this replacement. And of course it doesn't recognize this kind of data type. Please check the print screens and see the differences.

Was this reply helpful? Yes No
WarrenBelz 153,084 Most Valuable Professional on at

Like (0)

Report

@TudorS

Actually posted on wrong thread - should have been this one - I have deleted content

Was this reply helpful? Yes No
TudorS 14 on at

Like (0)

Report

Hi @Michael E. Gernaey,

As you can check, I have added extra details. The code was working perfectly for more than one year. It is not about the syntax; it is more about what the hack is Microsoft team doing in the backend / backstage with their releases? They broke the code for my entire app. The production instance is still working, but my dev instance is broken due to this code change in the backstage 30 minutes ago. Is it here any Microsoft representative to read this thread and give an answer after they are immediately fixing this bug?????

Thank you!

Was this reply helpful? Yes No