cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

multi select using lookup field

Hi, 

 

I am having trouble submitting a multi-select value.

 

All data is in CDS.

Here's my screen.

001.png

This is a screen to see the sales rep's target store.

All sales rep has several target store.

So, I would like to submit a multiple value (target store) to "sales_store".

"sales_store" is made with a lookup field form another entity.

"sales_store" is a combo box and the setting is following.

 

002.png 

Can you please help on this?

Thanks and Regards, 

1 ACCEPTED SOLUTION

Accepted Solutions

Hi @Anonymous ,

 

I assume that the sales rep entity is the data source of the gallery. You made the “sales_store” be a LookUp field which could only store a single value of another entity.

 

As you said all sales rep have several targer stores, my question is would some rep have a same target store? If no, the scenario should be a One-to-Many relationship.

 

This means one rep have multiple target stores and the LookUp field should be in the entity which may be named as “Target_Stores” and the lookup field could be named as “Rep_owner” for e.g..

 

On the other hand, if some reps have one or more same target stores, it becomes a N:N relationship.

 

But back to the beginning, the 1:N relationship could not help you achieve the goal.

 

If you only want to choose stores and display their names in the gallery, relationships are not necessary. Below is an easy solution.

 

Assuming we have two tables, one called “Target_stores”  as table1, another called “Sales_stores” as table2. Table 1 has columns “sales_name” and “sales_store” with multiline text. Table 2 has columns “store_name” and “address”.

 

Now we have a gallery and an edit form with data source table1. Replace the text box in the form’s “sales_store” card with a combo box, set the Items property of the combo box as “Sales_stores”.

 

What we want is in the gallery we can see all the sales stores assigned to the sales rep, so we set the Update property of the sales_store card of the form to:

 

Concat( ComboBox1.SelectedItems,store_name ,",")

 

6.png

This helps convert the table value to text, which need to be saved into the sales_store column of table1. If multiple stores be selected, names separated by comma. Since the field type of “sales_store” is multiline text, using Char(10) to replace the comma would be better and more clear to display store names in the gallery.

 

In the combo box, set the DefaultSelectItems to:

 

Filter(Sales_stores,store_name in Gallery1.Selected.sales_store)

 

This make the combo box display proper stores assigned to the sales rep selected in the gallery.

 

If there be any further plans of using the target stores in your scenario, creating a N:N relationship would be the way.

 

First, relate the two entities on the PowerApps portal, and don’t forget to refresh the data source of the entities in your App.

 

7.png

 

Second, set the OnSelect of the Save Botton to:

 

ForAll(

    Gallery1.Selected.Sales_stores,

    If(

        address in ComboBox1.SelectedItems.address,

        "",

        Unrelate(

            Gallery1.Selected.Sales_stores,

            ThisRecord

        )

    )

);

ForAll(

    ComboBox1.SelectedItems,

    If(

        address in Gallery1.Selected.Sales_stores.address,

        "",

        Relate(

            Gallery1.Selected.Sales_stores,

            ThisRecord

        )

    )

);

SubmitForm(Form1)

 

This is adding and deleting the relations between the seleted sales rep in the Gallery and the selected stores in the Combo Box.

 

And the Text property of the Label in the Gallery which you designed to display the names of rep’s  target stores:

 

Concat(ThisItem.Sales_stores,store_name,",  ")

 

Now we have a table “Gallery1.Selected.Sales_stores”, and display all fields of the table’s store_name column in the Gallery.

 

8.png

 

Best regards,
Community Support Team _ Jeffer Ni
If this post helps, then please consider Accept it as the solution to help the other members find it more.

Community Support Team _ Jeffer Ni

If this post helps, then please consider Accept it as the solution to help the other members find it.

View solution in original post

2 REPLIES 2
EricRegnier
Most Valuable Professional
Most Valuable Professional

Hi @Anonymous,

What type of field is store on your sales rep entity? It cannot be a lookup nor an optionset because it can only contain one value.

You can use Multi Select Option Set. The optionset item are integers and the selection stored in your parent entity (i.e. sales rep) is a string delimited by a comma. E.g. "123,456,789". This would required an integer/whole number equivalent on your store entity which you would then build your string delimited selection.

 

The other option is with a many-to-many (N-N) relationship between sales rep and store. You can leverage the out-of-the-box N-N relationship or with another custom junction entity with 2 lookups, one on sales rep and the other on store. The custom junctions is more flexibility as you can specific more properties of the relationship whereas out-of-the-box N-N you can't. There are also other limitations with out-of-the-box N-N but it's more of an advanced topic...

Hope this helps...

Hi @Anonymous ,

 

I assume that the sales rep entity is the data source of the gallery. You made the “sales_store” be a LookUp field which could only store a single value of another entity.

 

As you said all sales rep have several targer stores, my question is would some rep have a same target store? If no, the scenario should be a One-to-Many relationship.

 

This means one rep have multiple target stores and the LookUp field should be in the entity which may be named as “Target_Stores” and the lookup field could be named as “Rep_owner” for e.g..

 

On the other hand, if some reps have one or more same target stores, it becomes a N:N relationship.

 

But back to the beginning, the 1:N relationship could not help you achieve the goal.

 

If you only want to choose stores and display their names in the gallery, relationships are not necessary. Below is an easy solution.

 

Assuming we have two tables, one called “Target_stores”  as table1, another called “Sales_stores” as table2. Table 1 has columns “sales_name” and “sales_store” with multiline text. Table 2 has columns “store_name” and “address”.

 

Now we have a gallery and an edit form with data source table1. Replace the text box in the form’s “sales_store” card with a combo box, set the Items property of the combo box as “Sales_stores”.

 

What we want is in the gallery we can see all the sales stores assigned to the sales rep, so we set the Update property of the sales_store card of the form to:

 

Concat( ComboBox1.SelectedItems,store_name ,",")

 

6.png

This helps convert the table value to text, which need to be saved into the sales_store column of table1. If multiple stores be selected, names separated by comma. Since the field type of “sales_store” is multiline text, using Char(10) to replace the comma would be better and more clear to display store names in the gallery.

 

In the combo box, set the DefaultSelectItems to:

 

Filter(Sales_stores,store_name in Gallery1.Selected.sales_store)

 

This make the combo box display proper stores assigned to the sales rep selected in the gallery.

 

If there be any further plans of using the target stores in your scenario, creating a N:N relationship would be the way.

 

First, relate the two entities on the PowerApps portal, and don’t forget to refresh the data source of the entities in your App.

 

7.png

 

Second, set the OnSelect of the Save Botton to:

 

ForAll(

    Gallery1.Selected.Sales_stores,

    If(

        address in ComboBox1.SelectedItems.address,

        "",

        Unrelate(

            Gallery1.Selected.Sales_stores,

            ThisRecord

        )

    )

);

ForAll(

    ComboBox1.SelectedItems,

    If(

        address in Gallery1.Selected.Sales_stores.address,

        "",

        Relate(

            Gallery1.Selected.Sales_stores,

            ThisRecord

        )

    )

);

SubmitForm(Form1)

 

This is adding and deleting the relations between the seleted sales rep in the Gallery and the selected stores in the Combo Box.

 

And the Text property of the Label in the Gallery which you designed to display the names of rep’s  target stores:

 

Concat(ThisItem.Sales_stores,store_name,",  ")

 

Now we have a table “Gallery1.Selected.Sales_stores”, and display all fields of the table’s store_name column in the Gallery.

 

8.png

 

Best regards,
Community Support Team _ Jeffer Ni
If this post helps, then please consider Accept it as the solution to help the other members find it more.

Community Support Team _ Jeffer Ni

If this post helps, then please consider Accept it as the solution to help the other members find it.

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 (555)