cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
markslosberg
Resolver II
Resolver II

"Value must be between 0 and 100" error occurring occasionally on the execution of a Patch statement

I have a Patch statement has been working reliably.  It is built from the results of two separate Flows that extract info (first SoldTo and then ShipTo records) from SQL Stored Procedures into Global and Context Variables and screen controls which I then use to allow the user to edit the values and then place the edited info the CDS Sales Order Header entity.  

 

As I said, it had been working reliably with a subset of the SoldTo and ShipTo records that were being retrieved.  When I expanded my testing to include a broader array of SoldTos and ShipTos selected randomly but with a "broader brush", I have found that on some of the selected values, when I go to Patch the record (and this only happens on the creation of a new Sales Order using the Defaults function and not Edits to existing records), I get a Patch failure with the error "Value must be between 0 and 100".  I have reviewed my entity structure and that simply doesn't ring a bell and I don't have any values that fall into that range and very few overall restrictions other than a couple of required fields. I have never seen this error code before.

 

I have been "detectiving" the SoldTo/ShipTo combos that work vs. those that fail and have not seen any visible differences between the two types other than some work perfectly and others throw the error.

 

Has anyone else encountered this error message and have some understanding of it such that I can continue to troubleshoot what the difference between a Patch that works and one that doesn't.

 

Here are a couple of screen prints. The first shows the error code in the statement where I had a Patch failure.  This error message moves around so it doesn't seem to be pointing at any particular offending part of the statement.Value must be between 0 and 100 error.png.  And here is the same code after a successful Patch with no errors thrown.  I have tracked each of the data elements and don't see anything obviously different between the ones that work and the ones that don't.

 

Without Value must be between 0 and 100 error.png

Here is the entire statement under the "Save" button.  The data elements are being extracted from the galleries associated with the colSoldToCustList and colShipToList that are populate the two galleries where I am pulling data from the selected record(s).

 

 

 

 

If(
    SOHdrEditMode,
    UpdateContext(
        {
            selectedOrderCTX: Patch(
                'Sales Order Headers',
                LookUp(
                    'Sales Order Headers',
                    cr66a_salesordernumber = selectedOrderCTX.cr66a_salesordernumber
                ),
                {
                    cr66a_soldtoname: selectedOrderCTX.'SoldTo Name',
                    cr66a_soldtocontactname: txtSOHdrContactName.Text,
                    cr66a_soldtocontactmobilephone: txtSOHdrContactMobile.Text,
                    cr66a_soldtocontactemail: txtSOHdrContactEmail.Text,
                    cr66a_soldtoaddressid: selectedOrderCTX.SoldToAddressID,
                    cr66a_shiptoname: selectedOrderCTX.'ShipTo Name',
                    cr66a_shiptocontactname: txtSOHdrShipToContactName.Text,
                    cr66a_shiptocontactmobilephone: txtSOHdrShipToMobile.Text,
                    cr66a_shiptocontactemail: txtSOHdrShipToEmail.Text,
                    cr66a_shiptoaddressid: selectedOrderCTX.'ShipTo AddressID',
                    cr66a_seedorderpreference: drpSeedOrderPreference.Selected.Value,
                    cr66a_salespersoncommissioncode: selectedOrderCTX.cr66a_salespersoncommissioncode,
                    cr66a_salesorderdate: dteSalesOrderDate.SelectedDate,
                    cr66a_requiredarrivaldatetime: dteRequiredByDate.SelectedDate + Time(
                        Value(drpHeaderRequiredHour.Selected.Value),
                        Value(drpHeaderRequiredMinute.Selected.Value),
                        0
                    ),
                    cr66a_ordertype: drpOrderType.Selected.JDECode,
                    cr66a_generalshipmentrequirements: txtSOHdrShippingPreferences.Text,
                    cr66a_customerpo: txtSOHdrCustomerPO.Text,
                    cr66a_soldtonumber: Value(lblSoldToCustomerNumber.Text),
                    cr66a_shiptonumber: Value(lblShipToCustomerNumber.Text),
                    cr66a_shiptolongaddressid: selectedOrderCTX.'ShipTo LongAddressID',
                    cr66a_pendingorderstatus: drpPendingOrderStatus.Selected.Value
                }
            )
        }
    );
    Set(
        changedOrderLineData,
        false
    ),
    UpdateContext(
        {
            selectedOrderCTX: Patch(
                'Sales Order Headers',
                Defaults('Sales Order Headers'),
                {
                    cr66a_soldtoname: selectedOrderCTX.'SoldTo Name',
                    cr66a_soldtocontactname: txtSOHdrContactName.Text,
                    cr66a_soldtocontactmobilephone: txtSOHdrContactMobile.Text,
                    cr66a_soldtocontactemail: txtSOHdrContactEmail.Text,
                    cr66a_soldtoaddressid: Text(selectedOrderCTX.SoldToAddressID),
                    cr66a_shiptoname: selectedOrderCTX.'ShipTo Name',
                    cr66a_shiptocontactname: txtSOHdrShipToContactName.Text,
                    cr66a_shiptocontactmobilephone: txtSOHdrShipToMobile.Text,
                    cr66a_shiptocontactemail: txtSOHdrShipToEmail.Text,
                    cr66a_shiptoaddressid: selectedOrderCTX.'ShipTo AddressID',
                    cr66a_seedorderpreference: drpSeedOrderPreference.Selected.Value,
                    cr66a_salespersoncommissioncode: selectedOrderCTX.cr66a_salespersoncommissioncode,
                    cr66a_salesorderdate: dteSalesOrderDate.SelectedDate,
                    cr66a_requiredarrivaldatetime: dteRequiredByDate.SelectedDate + Time(
                        Value(drpHeaderRequiredHour.Selected.Value),
                        Value(drpHeaderRequiredMinute.Selected.Value),
                        0
                    ),
                    cr66a_ordertype: drpOrderType.Selected.JDECode,
                    cr66a_generalshipmentrequirements: txtSOHdrShippingPreferences.Text,
                    cr66a_customerpo: txtSOHdrCustomerPO.Text,
                    cr66a_soldtonumber: Value(lblSoldToCustomerNumber.Text),
                    cr66a_shiptonumber: Value(lblShipToCustomerNumber.Text),
                    cr66a_shiptolongaddressid: selectedOrderCTX.cr66a_shiptolongaddressid,
                    cr66a_pendingorderstatus: drpPendingOrderStatus.Selected.Value
                }
            )
        }
    );
    Set(
        changedOrderLineData,
        false
    )
);
Set(
    showCustList,
    false
);
Set(
    showShipToList,
    false
);
Set(
    changedOrderHdrData,
    false
);
Set(
    showSavedHeader,
    true
);
Set(
    _SOHeaderDisplayMode,
    true
);
Clear(colSoldToCustList);
Clear(colShipToList)

 

 

 

Thanks,

Mark

1 ACCEPTED SOLUTION

Accepted Solutions

That wasn't exactly the solution but it got me pointed in the right direction.  It wasn't the DropDownBox that was too long but one of the other text strings that came in from the SQL Stored Procedure call.  As it turned out the source data was not well structured and consistent (which is what the core symptom was (some records were just fine, others not).

 

I never figured out exactly which string was too long (I have a hunch) but I just went through and did a Left truncate at 100 characters on every field and that solved it.  And my app is that much more error-protected now.

 

It might be nice if the error message was just a bit more descriptive and told me which of the 21 fields was causing the error instead of the generic "Value must be between 0 and 100" which could have been any of them.  Then it does suggest that it was indeed a value that was causing the problem rather than a string length violation.

 

Thanks for the tip. I needed it;-).

 

Mark

View solution in original post

8 REPLIES 8
EricRegnier
Most Valuable Professional
Most Valuable Professional

Hi @markslosberg,

Have you tried increasing the max length of your field? In make.powerapps.com, expand Data then select Entities. Search for your entity and open it. Under the Fields tab, select your field and a right pane will open. Under Advanced Options, you can increase the Max Length. Don't forget to save and publish!

Here's more info about editing a field: https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/create-edit-field-portal#edit-a... 

Hope this helps!

Thanks, I will try to look at that but I don’t think that is my issue. I don’t have anything that is currently constrained to between 0 and 100 and the challenge is the error message doesn’t give me any guidance as to which field or value is responsible for the message. As I said, most of the SoldTo/ShipTo combos work just fine and from what I can see, the info being fed to the Patch command is of identical type and length for both the ones that work and the ones that don’t. Obviously they aren’t actually identical but diagnosing the difference/issue has been a challenge. 

This seems to be something a bit more arcane. A little more info in the error message would be useful.

I'd look at drpSeedOrderPreference.Selected.Value and drpPendingOrderStatus.Selected.Value.... anything that's a .Value field rather than a .Text and then check out the max/min in the CDS entity

That wasn't exactly the solution but it got me pointed in the right direction.  It wasn't the DropDownBox that was too long but one of the other text strings that came in from the SQL Stored Procedure call.  As it turned out the source data was not well structured and consistent (which is what the core symptom was (some records were just fine, others not).

 

I never figured out exactly which string was too long (I have a hunch) but I just went through and did a Left truncate at 100 characters on every field and that solved it.  And my app is that much more error-protected now.

 

It might be nice if the error message was just a bit more descriptive and told me which of the 21 fields was causing the error instead of the generic "Value must be between 0 and 100" which could have been any of them.  Then it does suggest that it was indeed a value that was causing the problem rather than a string length violation.

 

Thanks for the tip. I needed it;-).

 

Mark

Agreed, the error messaging could be more informative, especially on long functions - glad you got it worked out!

Thank you.  You were right on but it didn't click with me until later.  The problem was the error message.  Based on that, I was hunting for a "value" in the numeric sense rather than a string length.  A clearer error message would have made this a lot quicker.

 

I also had to really inspect the data that was coming in from my data source which was not consistent.  All in all, while this was a bit of a 6-8 hour detour, my app is much more hardened now (across all of the different fields, numeric and string) and I have a design pattern to reuse for the future ensuring that my Patch statements closely match my CDS schema constraints.

Anonymous
Not applicable

Had to say that left Truncate is 'not' the best way to solve this. This will irritate your users who will wonder why half their text is missing and it will drive them crazy and they will complain to you that you build faulty apps.

 

The issue is with the field receiving the data, it is set to a max length of 100.

  1. Find that field and change it to a suitable length like 500 or 1000 or something.
  2. Next get rid of the left truncate.
  3. Once you have found the field, set the text box for that field to only allow the set max characters you have set for that field.
  4. Next put a label under the text box that checks the Length of that text box 'Text' attribute so it gives a character count to the user
    1. Or be smart and do some calculations to show the remaining character count allowed for that text box so the user can see how many characters they have left as they are typing.

This is the best way to do it ... not deleting half of the users text.

Kind of old news. Long since solved.  Nice ideas. All workable. 

I was mostly commenting on the bad diagnostics I was getting at the time. The error messages provided by PowerApps should have been clearer.  

On the other hand, ensuring that string length maximums (and data types) are consistent between on-screen controls and back-end data stores is hygiene that I, as a developer, need to pay attention. 

Helpful resources

Announcements

Exclusive LIVE Community Event: Power Apps Copilot Coffee Chat with Copilot Studio Product Team

  It's time for the SECOND Power Apps Copilot Coffee Chat featuring the Copilot Studio product team, which will be held LIVE on April 3, 2024 at 9:30 AM Pacific Daylight Time (PDT).     This is an incredible opportunity to connect with members of the Copilot Studio product team and ask them anything about Copilot Studio. We'll share our special guests with you shortly--but we want to encourage to mark your calendars now because you will not want to miss the conversation.   This live event will give you the unique opportunity to learn more about Copilot Studio plans, where we’ll focus, and get insight into upcoming features. We’re looking forward to hearing from the community, so bring your questions!   TO GET ACCESS TO THIS EXCLUSIVE AMA: Kudo this post to reserve your spot! Reserve your spot now by kudoing this post.  Reservations will be prioritized on when your kudo for the post comes through, so don't wait! Click that "kudo button" today.   Invitations will be sent on April 2nd.Users posting Kudos after April 2nd. at 9AM PDT may not receive an invitation but will be able to view the session online after conclusion of the event. Give your "kudo" today and mark your calendars for April 3rd, 2024 at 9:30 AM PDT and join us for an engaging and informative session!

Tuesday Tip: Unlocking Community Achievements and Earning Badges

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!     THIS WEEK'S TIP: Unlocking Achievements and Earning BadgesAcross the Communities, you'll see badges on users profile that recognize and reward their engagement and contributions. These badges each signify a different achievement--and all of those achievements are available to any Community member! If you're a seasoned pro or just getting started, you too can earn badges for the great work you do. Check out some details on Community badges below--and find out more in the detailed link at the end of the article!       A Diverse Range of Badges to Collect The badges you can earn in the Community cover a wide array of activities, including: Kudos Received: Acknowledges the number of times a user’s post has been appreciated with a “Kudo.”Kudos Given: Highlights the user’s generosity in recognizing others’ contributions.Topics Created: Tracks the number of discussions initiated by a user.Solutions Provided: Celebrates the instances where a user’s response is marked as the correct solution.Reply: Counts the number of times a user has engaged with community discussions.Blog Contributor: Honors those who contribute valuable content and are invited to write for the community blog.       A Community Evolving Together Badges are not only a great way to recognize outstanding contributions of our amazing Community members--they are also a way to continue fostering a collaborative and supportive environment. As you continue to share your knowledge and assist each other these badges serve as a visual representation of your valuable contributions.   Find out more about badges in these Community Support pages in each Community: All About Community Badges - Power Apps CommunityAll About Community Badges - Power Automate CommunityAll About Community Badges - Copilot Studio CommunityAll About Community Badges - Power Pages Community

Tuesday Tips: Powering Up Your Community Profile

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!   This Week's Tip: Power Up Your Profile!  🚀 It's where every Community member gets their start, and it's essential that you keep it updated! Your Community User Profile is how you're able to get messages, post solutions, ask questions--and as you rank up, it's where your badges will appear and how you'll be known when you start blogging in the Community Blog. Your Community User Profile is how the Community knows you--so it's essential that it works the way you need it to! From changing your username to updating contact information, this Knowledge Base Article is your best resource for powering up your profile.     Password Puzzles? No Problem! Find out how to sync your Azure AD password with your community account, ensuring a seamless sign-in. No separate passwords to remember! Job Jumps & Email Swaps Changed jobs? Got a new email? Fear not! You'll find out how to link your shiny new email to your existing community account, keeping your contributions and connections intact. Username Uncertainties Unraveled Picking the perfect username is crucial--and sometimes the original choice you signed up with doesn't fit as well as you may have thought. There's a quick way to request an update here--but remember, your username is your community identity, so choose wisely. "Need Admin Approval" Warning Window? If you see this error message while using the community, don't worry. A simple process will help you get where you need to go. If you still need assistance, find out how to contact your Community Support team. Whatever you're looking for, when it comes to your profile, the Community Account Support Knowledge Base article is your treasure trove of tips as you navigate the nuances of your Community Profile. It’s the ultimate resource for keeping your digital identity in tip-top shape while engaging with the Power Platform Community. So, dive in and power up your profile today!  💪🚀   Community Account Support | Power Apps Community Account Support | Power AutomateCommunity Account Support | Copilot Studio  Community Account Support | Power Pages

Super User of the Month | Chris Piasecki

In our 2nd installment of this new ongoing feature in the Community, we're thrilled to announce that Chris Piasecki is our Super User of the Month for March 2024. If you've been in the Community for a while, we're sure you've seen a comment or marked one of Chris' helpful tips as a solution--he's been a Super User for SEVEN consecutive seasons!       Since authoring his first reply in April 2020 to his most recent achievement organizing the Canadian Power Platform Summit this month, Chris has helped countless Community members with his insights and expertise. In addition to being a Super User, Chris is also a User Group leader, Microsoft MVP, and a featured speaker at the Microsoft Power Platform Conference. His contributions to the new SUIT program, along with his joyous personality and willingness to jump in and help so many members has made Chris a fixture in the Power Platform Community.   When Chris isn't authoring solutions or organizing events, he's actively leading Piasecki Consulting, specializing in solution architecture, integration, DevOps, and more--helping clients discover how to strategize and implement Microsoft's technology platforms. We are grateful for Chris' insightful help in the Community and look forward to even more amazing milestones as he continues to assist so many with his great tips, solutions--always with a smile and a great sense of humor.You can find Chris in the Community and on LinkedIn. Thanks for being such a SUPER user, Chris! 💪🌠

Find Out What Makes Super Users So Super

We know many of you visit the Power Platform Communities to ask questions and receive answers. But do you know that many of our best answers and solutions come from Community members who are super active, helping anyone who needs a little help getting unstuck with Business Applications products? We call these dedicated Community members Super Users because they are the real heroes in the Community, willing to jump in whenever they can to help! Maybe you've encountered them yourself and they've solved some of your biggest questions. Have you ever wondered, "Why?"We interviewed several of our Super Users to understand what drives them to help in the Community--and discover the difference it has made in their lives as well! Take a look in our gallery today: What Motivates a Super User? - Power Platform Community (microsoft.com)

March User Group Update: New Groups and Upcoming Events!

  Welcome to this month’s celebration of our Community User Groups and exciting User Group events. We’re thrilled to introduce some brand-new user groups that have recently joined our vibrant community. Plus, we’ve got a lineup of engaging events you won’t want to miss. Let’s jump right in: New User Groups   Sacramento Power Platform GroupANZ Power Platform COE User GroupPower Platform MongoliaPower Platform User Group OmanPower Platform User Group Delta StateMid Michigan Power Platform Upcoming Events  DUG4MFG - Quarterly Meetup - Microsoft Demand PlanningDate: 19 Mar 2024 | 10:30 AM to 12:30 PM Central America Standard TimeDescription: Dive into the world of manufacturing with a focus on Demand Planning. Learn from industry experts and share your insights. Dynamics User Group HoustonDate: 07 Mar 2024 | 11:00 AM to 01:00 PM Central America Standard TimeDescription: Houston, get ready for an immersive session on Dynamics 365 and the Power Platform. Connect with fellow professionals and expand your knowledge. Reading Dynamics 365 & Power Platform User Group (Q1)Date: 05 Mar 2024 | 06:00 PM to 09:00 PM GMT Standard TimeDescription: Join our virtual meetup for insightful discussions, demos, and community updates. Let’s kick off Q1 with a bang! Leaders, Create Your Events!    Leaders of existing User Groups, don’t forget to create your events within the Community platform. By doing so, you’ll enable us to share them in future posts and newsletters. Let’s spread the word and make these gatherings even more impactful! Stay tuned for more updates, inspiring stories, and collaborative opportunities from and for our Community User Groups.   P.S. Have an event or success story to share? Reach out to us – we’d love to feature you!

Users online (6,130)