web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps - Error Handling / Edit Screen error
Power Apps - Error Handling
Unanswered

Edit Screen error

(0) ShareShare
ReportReport
Posted on by Ann_DAS 110
Good afternoon,
 
I am working on a Power App for an audit and am encountering an issue or two with the Choices input when I try to convert a drop down menu to radio buttons. Specifically, I am getting a variety of error messages with the entry:
 
- Expected operator. We expect an operator such as +, *, or & at this point in the formula.
- Name isn't valid. '{0}' isn't recognized.
 
1. The first issue is that when I select the original Choices entry it displays as 
Choices([@'Audit 5S de production / Production 5S Audit'].'Les_x0020_postes_x0020_de_x0020_') instead of the whole entry. 
 
I have been able to fix this by copying the data card value and replacing the Les_x0020_postes_x0020_de_x0020 with the whole entry and everything seems to work fine.... except for two entries that give me these messages above.
 
Frankly, I'm baffled. Copying the data card doesn't seem to work, copying the actual entry from the SharePoint list doesn't work either and I've looked at the difference between an accepted entry and the error one to see if I am missing something that I just can't see. Is is the French? The length?
 
Accepted entry - Choices([@'Audit 5S de production / Production 5S Audit'].'Le sol, les étagères et les armoires, sont-ils propres et exempts de déversements et de débris ? / Are floor, racks and cabinets kept clean and free of spills and debris?')

Error entry - Choices([@'Audit 5S de production / Production 5S Audit'].'Y a-t-il un espace dédié pour les outils et l'équipement ? Sont-ils conservés dans leur espace dédié suite à leur utilisation ? / Is there a home location for tools and equipment ? Are they kept in their home location after their use?')
 
Any thoughts or suggestions would be greatly appreciated as I am relatively new to Power Apps.
 
Thank you,
Ann
 
I have the same question (0)
  • WarrenBelz Profile Picture
    WarrenBelz 150,771 Most Valuable Professional on at
    Edit Screen error
    One of the issues with giving SharePoint fields very long names with non-alpha characters is this - Power Apps at times struggles to resolve them. Yours also has commas, question marks, a forward slash and a single quote in the middle (the last two in particular could make the whole name invalid in Power Apps)
     
    Open up your SharePoint List Settings, select the field and copy the last bit in the URL at the top after &field= and see what the actual field name is. Even though the field name you used is this 
    Y a-t-il un espace dédié pour les outils et l'équipement ? Sont-ils conservés dans leur espace dédié suite à leur utilisation ? / Is there a home location for tools and equipment ? Are they kept in their home location after their use?
    SharePoint substitutes the Hex values of any special characters, with %HexNo, so your name would turn into this
    Y%20a%2Dt%2Dil%20un%20espace%20dédié%20pour%20les%20outils%20et%20l%27équipement%20%3F%20Sont%2Dils%20conservés%20dans%20leur%20espace%20dédié%20suite%20à%20leur%20utilisation%20%3F%20%2F%20Is%20there%20a%20home%20location%20for%20tools%20and%20equipment%20%3F%20Are%20they%20kept%20in%20their%20home%20location%20after%20their%20use%3F
    which is 336 characters (the maximum for a field is 256). I suspect this causes the "Internal name", to be truncated to 32 characters, which would be 
    Y%20a%2Dt%2Dil%20un%20espace%20d
    or plainly 
    'Y a-t-il un espace d'
    You should be able to get the name as I have noted above from the List Settings.
     
    Whatever the case, you need to shorten your field names (this may require new fields) and use only alpha or number characters and try to keep them under 32 characters (mine are maximum half of that).
     
    I have a blog on app construction - the Field Naming Protocol section may be useful for you.
     
    Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful?
    Visit my blog     Practical Power Apps    LinkedIn  

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

News and Announcements

Welcome to the Power Platform Communities
Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Tom Macfarlan – Community Spotlight

We are honored to recognize Tom Macfarlan as our Community Spotlight for October…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 1,019 Most Valuable Professional

#2
developerAJ Profile Picture

developerAJ 436

#3
MS.Ragavendar Profile Picture

MS.Ragavendar 281 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Microsoft Power Platform Community release plans