cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Submit button is erroring that a value must be provided for item

Hi there,

 

Nearly there with my app - the last hurdle is that it won't patch my data to the receiving table.

So I have two SQL tables -

The first is called Powerapps.CRM_ACCOUNT and holds with a distinct list of ACCOUNT_NUMBER and ACCOUNT_NAME. I pulled this into my app and it's used in a vertical gallery for users to search by account number or account name. 

 

 

Filter('Powerapps.CRM_Account',ACCOUNT_SEARCH.Text in CRM_ACCOUNT_NAME || ACCOUNT_SEARCH.Text in CRM_ACCOUNT_NUMBER)

 

 

The second SQL table is called Powerapps.SCHEDULE_OF_SERVICES and holds CRM_ACCOUNT_NUMBER as well as 8 other fields, all of which can be populated in my app. There's a mix of drop downs, text input, radio button and checkbox. 

 

The key between the two SQL tables is called ACCOUNT_ID which is just an index I guess, and is not anywhere in the app itself.

 

My submit button should look for changes to any of the fields and then push the data into Powerapps.SCHEDULE_OF_SERVICES by matching the selected ACCOUNT_NUMBER to the SQL CRM_ACCOUNT_NUMBER. 

 

Here is the OnStart code for my app:

 

 

ClearCollect(
    CollectUpdate,
    ShowColumns(
        Table(Defaults('Powerapps.CRM_SCHEDULE_OF_SERVICES')),
        "ACCOUNT_ID",
        "CRM_ACCOUNT_NUMBER",
        "ANNUAL_FEE",
        "SCHEDULE_YEAR",
        "SCHEDULE_INCLUDED",
        "SERVICE_WEIGHTING",
        "FREQUENCY_AGREED",
        "VOLUME_AGREED",
        "SCHEDULE_ACHIEVED",
        "LOADDATE",
        "USER"
    );
    Clear(CollectUpdate)
);

 

 

I'm not sure if I should be including ACCOUNT_ID or CRM_ACCOUNT_NUMBER in this code because they are already populated in the SQL table, and will not be updated.

 

Here is the OnSelect code for my Submit button:

 

 

ForAll(
    CollectUpdate,
    Patch(
        'Powerapps.CRM_SCHEDULE_OF_SERVICES',
        LookUp('Powerapps.CRM_SCHEDULE_OF_SERVICES', (Text(CRM_ACCOUNT_NUMBER) = BROWSE_ACCOUNT.Selected.BROWSE_ACCOUNTNUMBER.Text)),
        {
            CRM_ACCOUNT_NUMBER: BROWSE_ACCOUNTNUMBER,
            ANNUAL_FEE: ANNUAL_FEE,
            SCHEDULE_YEAR: SCHEDULE_YEAR,
            SCHEDULE_INCLUDED: IS_INCLUDED,
            SERVICE_WEIGHTING: NEW_SERVICEWEIGHTING,
            FREQUENCY_AGREED: NEW_FREQUENCYAGREED,
            VOLUME_AGREED: NEW_VOLUMEAGREED,
            SCHEDULE_ACHIEVED: NEW_SCHEDULEACHIEVED,
            LOADDATE: Now(),
            USER: User().Email
             } ) );
             Notify("Submission successful", NotificationType.Success)

 

 

As you can see i'm asking it to check ACCOUNT_NUMBER selected from my search gallery equals CRM_ACCOUNT_NUMBER in SQL as the lookup.

ACCOUNT_NUMBER in the gallery and is just a label which says ThisItem.ACCOUNT_NUMBER.

 

Can anyone help me get this working? I know i've done something wrong but I don't know what!

6 REPLIES 6
gcmfaizan
Solution Sage
Solution Sage

@JemmaD ,

 

can you update your for all with this:

ForAll(
    CollectUpdate As ThisRec,
    Patch(
        'Powerapps.CRM_SCHEDULE_OF_SERVICES',
        LookUp('Powerapps.CRM_SCHEDULE_OF_SERVICES', CRM_ACCOUNT_NUMBER = BROWSE_ACCOUNTNUMBER.Text),
        {
            CRM_ACCOUNT_NUMBER: ThisRec.BROWSE_ACCOUNTNUMBER.Text,
            ANNUAL_FEE: ThisRec.ANNUAL_FEE,
            SCHEDULE_YEAR: ThisRec.SCHEDULE_YEAR,
            SCHEDULE_INCLUDED: ThisRec.IS_INCLUDED,
            SERVICE_WEIGHTING: ThisRec.NEW_SERVICEWEIGHTING,
            FREQUENCY_AGREED: ThisRec.NEW_FREQUENCYAGREED,
            VOLUME_AGREED: ThisRec.NEW_VOLUMEAGREED,
            SCHEDULE_ACHIEVED: ThisRec.NEW_SCHEDULEACHIEVED,
            LOADDATE: Now(),
            USER: User().Email
        }
    )
);
Notify("Submission successful", NotificationType.Success)

 

 

If this is the answer for your question, please mark the post as Solved.
If this answer helps you in any way, please give it a like.

 

Thanks!

@gcmfaizan thanks for this, it's now erroring that ANNUAL_FEE does not match the expected type 'Number' (this is a number type field)

And it says ThisRec isn't recognised. This is my revised code:

 

 

ForAll(
    CollectUpdate as ThisRec,
    Patch(
        'Powerapps.CRM_SCHEDULE_OF_SERVICES',
        LookUp('Powerapps.CRM_SCHEDULE_OF_SERVICES', (Text(CRM_ACCOUNT_NUMBER) = BROWSE_ACCOUNT.Selected.BROWSE_ACCOUNTNUMBER.Text)),
        {
            CRM_ACCOUNT_NUMBER: ThisRec.BROWSE_ACCOUNTNUMBER.Text,
            ANNUAL_FEE: ThisRec.ANNUAL_FEE,
            SCHEDULE_YEAR: ThisRec.SCHEDULE_YEAR,
            SCHEDULE_INCLUDED: ThisRec.IS_INCLUDED,
            SERVICE_WEIGHTING: ThisRec.NEW_SERVICEWEIGHTING,
            FREQUENCY_AGREED: ThisRec.NEW_FREQUENCYAGREED,
            VOLUME_AGREED: ThisRec.NEW_VOLUMEAGREED,
            SCHEDULE_ACHIEVED: ThisRec.NEW_SCHEDULEACHIEVED,
            LOADDATE: Now(),
            USER: User().Email
             } ) );
             Notify("Submission successful", NotificationType.Success)

 

@JemmaD,

can you rape ANNUAL_FEE in the value function:
like:

Value(ThisRec.ANNUAL_FEE)

 

If this is the answer for your question, please mark the post as Solved.
If this answer helps you in any way, please give it a like.

 

Thanks!

@gcmfaizan it's still upset, it started saying it didn't recognise any of the values of the other fields so I updated them all with a Value() and it still doesn't like it, it says:

JemmaD_0-1699535866589.png

 

Here is my latest syntax:

 

ForAll(
    CollectUpdate as ThisRec,
    Patch(
        'Powerapps.CRM_SCHEDULE_OF_SERVICES',
        LookUp('Powerapps.CRM_SCHEDULE_OF_SERVICES', CRM_ACCOUNT_NUMBER = BROWSE_ACCOUNT.Selected.BROWSE_ACCOUNTNUMBER.Text),
        {
            CRM_ACCOUNT_NUMBER: Value(ThisRec.BROWSE_ACCOUNTNUMBER.Text),
            ANNUAL_FEE: Value(ThisRec.ANNUAL_FEE.Value),
            SCHEDULE_YEAR: Value(ThisRec.SCHEDULE_YEAR.Selected.Value),
            SCHEDULE_INCLUDED: Value(ThisRec.IS_INCLUDED.Value),
            SERVICE_WEIGHTING: Value(ThisRec.NEW_SERVICEWEIGHTING.Selected.Value),
            FREQUENCY_AGREED: Value(ThisRec.NEW_FREQUENCYAGREED.Selected.Value),
            VOLUME_AGREED: Value(ThisRec.NEW_VOLUMEAGREED.Value),
            SCHEDULE_ACHIEVED: Value(ThisRec.NEW_SCHEDULEACHIEVED.Value),
            LOADDATE: Now(),
            USER: User().Email
             } ) );
             Notify("Submission successful", NotificationType.Success)

I'm not sure how to reference each of the fields - I only know that drop downs like Selected.Value

Here is what each field type is:

 

BROWSE_ACCOUNT_NUMBER - type Label (text)

ANNUAL_FEE - type Text input (number)

SCHEDULE_YEAR - type Drown down (number)

IS_INCLUDED - type Checkbox

NEW_SERVICEWEIGHTING - type Drop down (number)

NEW_FREQUENCYAGREED - type Drop down (text)

NEW_VOLUMEAGREED - type Text input (number)

NEW_SCHEDULEACHIEVED - type Radio

@JemmaD ,

 

just use value function there where column type is Number, 
can you try this formula,

ForAll(
    CollectUpdate as ThisRec,
    Patch(
        'Powerapps.CRM_SCHEDULE_OF_SERVICES',
        LookUp('Powerapps.CRM_SCHEDULE_OF_SERVICES', CRM_ACCOUNT_NUMBER = BROWSE_ACCOUNT.Selected.BROWSE_ACCOUNTNUMBER.Text),
        {
            CRM_ACCOUNT_NUMBER: Text(ThisRec.BROWSE_ACCOUNTNUMBER.Text),
            ANNUAL_FEE: Value(ThisRec.ANNUAL_FEE.Text),
            SCHEDULE_YEAR: Value(ThisRec.SCHEDULE_YEAR.Selected.Value),
            SCHEDULE_INCLUDED: Value(ThisRec.IS_INCLUDED.Value),
            SERVICE_WEIGHTING: Value(ThisRec.NEW_SERVICEWEIGHTING.Selected.Value),
            FREQUENCY_AGREED: Value(ThisRec.NEW_FREQUENCYAGREED.Selected.Value),
            VOLUME_AGREED: Value(ThisRec.NEW_VOLUMEAGREED.Text),
            SCHEDULE_ACHIEVED: Value(ThisRec.NEW_SCHEDULEACHIEVED.Value),
            LOADDATE: Now(),
            USER: User().Email
        }
    )
);
Notify("Submission successful", NotificationType.Success)

 

 

 

If this is the answer for your question, please mark the post as Solved.
If this answer helps you in any way, please give it a like.

 

Thanks!

@gcmfaizan changing that entry to .Text did not fix the code:

The errors are :

Invalid use of '.' against the rows from CRM_ACCOUNT_NUMBER down to SCHEDULE_ACHIEVED

Expected operator such as +, * or & (but doesn't tell me where)

Name isn't valid. 'ThisRec' isn't recognised

The function 'ForAll' has some invalid arguments

The function 'Text' has some invalid arguments

The function 'Value' has some invalid arguments

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (402)