cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Erec
Frequent Visitor

Powerapps saving combo box default value (no user selection made)

Hi

 

In my Powerapp I am setting the default value of a combo box to a global variable within the app. This is working ok, however, when I save the record it does not save and no error message is returned. The form continues as if the record saved correctly.

 

My question is. How to correctly set the value of the combo box so that when not changed by the user and saved. It saves?

 

To set the default value, I am setting the DataCard default to:

{'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.lsTSDetails",
  id:0,
  Value:Text(varMainID)}

The update of the datacard is set to:

DataCardValue5.Selected

 

I have set the combobox defaultSelectedItems to:

{'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.lsTSDetails",
  id:0,
  Value:Text(varMainID)}

 

I have looked around the forums and cannot find a solution that works relating to the Saving of the default value.

 

Any help appreciated.

 

Thanks

8 REPLIES 8
v-micsh-msft
Community Support
Community Support

Would you please share more details about the field that the Combo Box control bound with, is it a Lookup, Choice or Person or group type?

 

The '@odata.type' would vary based on the data field you are working with.

And I have never experienced with a value for 

"'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.lsTSDetails"

 

It would be much appreciated if you could share more details for this field type, I will then test it and share the results back.

 

Regards,

Michael

Community Support Team _ Michael Shao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hi Micahel

 

Yes the field defined in the SharePoint list is a Lookup field.

 

A little background.

I have an app where I am capturing main details for the data (varying fields) and also detail items/transactions that are linked to the main details. I save the main details first via the standard SubmitForm and then store the Last id into a variable. On the details form I have a combo field of type lookup that lists all the id values. I never want the user to enter this value. I want to default it and then save it with no user interaction. Despite the value being shown in the combo box it does not save unless if you click on it and select it.

 

Thanks

 

EREC

Hi Michael

 

Did you have the opportunity to see if you were able to replicate my issue and resolve?

 

Do you need any additional information?

 

Thanks

Eickhel
Most Valuable Professional
Most Valuable Professional

Hey,

 

as @v-micsh-msft said, I've neved seen that odata.type, for LookUps I use this:

 

For defaultSelectedItems should be:

Text(varMainID)

 

And for the update of the datacard you should use:

{
  '@odata.type': "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
  Id: 0,
  Value: DataCardValue5.Selected
}

 

 Let me know how it goes...

Hi

 

I have tried to implement your suggestion. The DefaultSelectedItems requires that the value passed is a Table value. VarMainID is of type numeric. So i tried a couple of combinations using:

 

{
  '@odata.type': "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
  Id: 0,
  Value: DataCardValue5.Selected
}

in the DefaultSelectedItems replacing value with Text(VarMainID) and changing the Update of the DataCard to your suggestion without any success.

 

Is there a different approach I should use to achieve objective? The only way i can currently think of is to use one table to store the data oppose to splitting into two tables. It would be nice to know a solution to the original problem, if there is one?

 

Thanks

Eickhel
Most Valuable Professional
Most Valuable Professional

Please give me more info on the global variable "VarMainID". Is this the Id of an existing record in the LookUp?

 

Let's try a different approach, asumming this information:

 

List: TravelExpenses

LookUpField: ReceiptType

 

Combo Box: ReceiptTypeCombo

Items: Choices( TravelExpenses.ReceiptType )

DefaultSelectedItems: TravelExpenses.ReceiptType

 

DataCard:

Update: ReceiptTypeCombo.Selected

 

When do you want to use this default "VarMainID"? I guess only on new records?

I ran into this, too. I have a singe item Combo Box control set up. When I round-trip data, if the user doesn't change the value during the edit, it saves an empty record.

 

 I was using this to set the DefaultSelectedItems:

[ThisItem.myDataField]

With my DataCard Update:

ComboBox1.Selected.Result

It took me a while, but I realized these are obviously different. DefaultSelectedItem(s - plural) is certainly not ComboBox1.Selected (not plural) lol.. 

 

I first came up with:

First(ComboBox1.SelectedItems).Result

Which let me get the SelectedItems from the table format into text. However, again, if I didn't interact with the Combo Box, this was blank.

 

The only way (I could come up with) to get the present value was at the the Data Card, and basically ignore the Combo Box:

ThisItem.myDataField

Which took me down a crazy rabbit hole of nested If() And() functions for the Update:

If(
    And(
	!IsBlank(ThisItem.myDataField),
	IsBlank(ComboBox1.SearchText),
	IsBlank(ComboBox1.Selected.Result)
    ),
    ThisItem.myDataField,
    And(
	!IsBlank(ComboBox1.SearchText),
	IsBlank(ComboBox1.Selected.Result)
    ),
    ComboBox1.SearchText,
    ComboBox1.Selected.Result
)

This allows me to have the present value already selected on my Combo Box, and re-save the record without any changes. Or I can select a different value, or type a new one completely. The only thing I can't do with this is clear the value, for my needs this wouldn't be an option anyway once it was set. 

Luckily I am working with a single item ComboBox, I can't imagine trying to do this with multiple. LOL

ewfefwef
Advocate II
Advocate II

Same issue after following this great article on how to do this 

https://jobs.collab365.community/powerapps-and-related-lists/

 

Everything works unless the user doesn't select the dropdown.

So the default value is not working and you this scenario you want to hide the drop down and always have it use the default.

According to article, you should use 

DataCard : Default

{
ID : varParentItem.ID,
Value : varParentItem.ID
}

But it doesn't worked, tried many ways around this. Microsoft need to make this simple feature easier.

 

So need a solution to link 2 sharepoint lists.

Expense Report and

Expense Items.

One simple 1 to many relationship

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

Top Solution Authors
Top Kudoed Authors
Users online (2,893)