cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
elysy
New Member

Showing View Selector and Command bar on Subgrid Custom Compnonent

Hi!


I'd like to retain the view selector on the subgrid when I'm applying a dataset custom control just so I can switch between my custom control and ootb subgrid. This should be possible because when I set the ootb subgrid as the default control and I switch to my PCF control thru the subgrid view selector, the whole command bar still remains.
Any advice on how I can make this to work?

Cheers!

29 REPLIES 29

@AnqiChen @ScottDurow 

 

I tried to use the approach Scott suggest and it works correctly for alphabets and All keyword but for # it doesn't seems to work. Below is my code.

 

Where char is alphabet letter.

 

  var condition = null;
            if (char == "#") {
                let alphabets: string[]  = ["0", "1", "2", "3", "4", "5", "6", "7", "8", "9"];
                condition = {
                    attributeName: "name",
                    conditionOperator: 8, //
                    value: alphabets,
                    entityAliasName: "opportunity",
                };
            }
            else {
                char = char + "%";
                condition = {
                    attributeName: "name",
                    conditionOperator: 6, //
                    value: char,
                    entityAliasName: "opportunity",
                };
            }
            const conditionArray = [];
            conditionArray.push(condition);
            this.contextObj.parameters.sampleDataSet.filtering.setFilter({
                // @ts-ignore
                conditions: conditionArray,
                filterOperator: 1, // Or
            });
            this.contextObj.parameters.sampleDataSet.refresh();

 

What am I doing wrong here ?

 

I also tried to use the keyword displayIndex:true and indeed it display the bar at the right side so as of now we can't use it.

I think the issue is that you are using the 'in' operator on the list of numbers - but actually you need to still use the like:

let alphabets: string[]  = ["0", "1", "2", "3", "4", "5", "6", "7", "8", "9"];
                condition = {
                    attributeName: "name",
                    conditionOperator: 8, //
                    value: alphabets,
                    entityAliasName: "opportunity",
                };

 

This will only match opportunities that have a name EXACTLY equal to 1,2,3...

I would use the same approach you are using for the like - but add a list of conditions that are grouped in a filter OR group:

 

{
        "filterOperator": 1, // OR
	"conditions": [
		{
			"attributeName": "fullname",
			"conditionOperator": 6, // LIKE
			"value": "0%"
		},
		{
			"attributeName": "fullname",
			"conditionOperator": 6, // LIKE
			"value": "1%"
		},
		{
			"attributeName": "fullname",
			"conditionOperator": 6, // LIKE
			"value": "2%"
		},
		{
			"attributeName": "fullname",
			"conditionOperator": 6, // LIKE
			"value": "3%"
		}
		...
	]
}

 

@ScottDurow 

Yes I do tried with IN condition and array but this doesn't work .I was in assumption that it will take array directly.

 

let alphabets: string[]  = ["0", "1", "2", "3", "4", "5", "6", "7", "8", "9"];
                condition = {
                    attributeName: "name",
                    conditionOperator: 6, //
                    value: alphabets,
                    entityAliasName: "opportunity",
                };

 

But after looping through list of condition not just passing the array it works.

 let numbers: string[] = ["0", "1", "2", "3", "4", "5", "6", "7", "8", "9"];
                for (var num of numbers) {
                    num = num + "%";
                    condition = {
                        attributeName: "name",
                        conditionOperator: 6, // Equal or Under
                        value: num,
                        entityAliasName: "opportunity",
                    };
                    conditionArray.push(condition);
                }

 

Thanks for your response.

a33ik
Most Valuable Professional
Most Valuable Professional

@AnqiChen @HemantG  can you confirm that this cds-data-set-options setting of dataset works in subgrids? I tried different combinations and nothing worked fine for me. I use CLI v1.1.6 and CDS v9.1.0000.10743. Here is piece of my manifest file:

<data-set name="exampleDataSet" display-name-key="exampleDataSet" cds-data-set-options="displayCommandBar:true;displayViewSelector:true;displayQuickFindSearch:true">
</data-set>

hi ,

 

Yes they should work well for subgrid. It might not show in CLI, but should show in product.

For ViewSelector and QuickFindSearch, u might need also to enable them in the form designer.

 

Also, the <data-set> should be the first property in the whole control.

 

 
 
a33ik
Most Valuable Professional
Most Valuable Professional

@AnqiChen then I have an issue to report. I can confirm that I do have that setting in the dataset tag set and dataset is the first property in the manifest file. Also I can confirm that I have viewsector enabled in the subgrid with one different that I use "Selected Views" option instead of "All Views". Should I check anything else?

hi,

 

I test it myself and it seems workable right now.

Attached is the sample app solution that contains one PCF control, and the form with the PCF control. The app is 'TestAppForDataSet'.

 

Once you import the solution, just create a new record through 'New' and then Save. You should see Commandbar/ViewSelector/QuickFind there.

 

I am not sure about the issue at your environment, it could be:

1) The cds-data-set-options should be "displayCommandBar:true;displayViewSelector:true;displayQuickFind:true". It's displayQuickFind, not displayQuickFindSearch.

I am not sure if this is the issue, if this is the issue, it definitely is our bug

2) Or the environment is legacy? what's the build version of the environment? is it an OnPrem environment?

 

If still have issue, please let us know or create a ticket to us. So we could check in details.

 

 

a33ik
Most Valuable Professional
Most Valuable Professional

@AnqiChen I was finally able to play with it myself and here are my results:

1. When you set the custom dataset control as a default one to be shown - view selector and search box are shown properly.

2. When I use default view (standard grid) and switch to custom control after - view selector and search box disappear. For me it looks like a bug.

cc: @HemantG 

@a33ik 

 

1) Thanks for reporting the issue. I am able to reproduce at my end

 

2) Our current stage is that the ViewSelector/QuickFind... as others, they need to go with the first rendered control before any 'ShowAs'.

 

For example, suppose the first rendered control is ControlA, then using 'ShowAs', we could switch to 'ControlB'. Then if 'ControlA' is not compatible with things like 'ViewSelector', then 'ControlB' won't show 'ViewSelector'

 

This is to prevent any confusion that suppose for the inititial view is

1) View 1 / Control A, then click 'ShowAs' to switch to Control B, then

2) View 1 / Control B, then use view selector to go to View 2

3) View 2/ Control B, then if we use 'ShowAs' to go back to 'ControlA', then

4) View 1/ControlA, or View 2/ControlA?

At this moment, as the ControlA could not see any view, it might have some confusion.

If we show View1, then the previous stage is View2

If we show View2, then at very initial stage, it is View1. should it be idempotent after these series of switchs?

 

In order to avoid any change, then we make it honor the first control's setting.

 

3) We do have a bug that our ReadonlyGrid/EditableGrid manifest does not claim they are compatible with quickFind/ViewSelector. Those are added by some hard-coded logic but its metadata does not claim it. If it switch to other controls, other controls will go with the ReadonlyGrid/EditableGrid setting so far.

We open a bug internally to update the metadata to make them compatible

 

 

 

 

Hi Scott, I have an existing PCF where I added the code below to display the command bar of the sub-grid where the PCF is attached.

<data-set name="dataset" display-name-key="Dataset" cds-data-set-options="displayCommandBar:true;displayViewSelector:true;displayquickfind:true">

It works but when I attached the PCF to a view on a dashboard, the command bar and view selector are still not visible. Am I missing anything? 

 

Thank you in advance for your reply.

Helpful resources

Announcements

Update! June 13th, Community Ambassador Call for User Group Leaders and Super Users

Calling all Super Users & User Group Leaders     UPDATE:  We just wrapped up June's Community Ambassador monthly calls for Super Users and User Group Leaders. We had a fantastic call with lots of engagement. We are excited to share some highlights with you!    Big THANK YOU to our special guest Thomas Verhasselt, from the Copilot Studio Product Team for sharing how to use Power Platform Templates to achieve next generation growth.     A few key takeaways: Copilot Studio Cookbook Challenge:  Week 1 results are posted, Keep up the great work!Summer of Solutions:  Starting on Monday, June 17th. Just by providing solutions in the community, you can be entered to win tickets to Power Platform Community Conference.Super User Season 2: Coming SoonAll communities moving to the new platform end of July We also honored two different community members during the call, Mohamed Amine Mahmoudi and Markus Franz! We are thankful for both leaders' contributions and engagement with their respective communities. 🎉   Be sure to mark your calendars and register for the meeting on July 11th and stay up to date on all of the changes that are coming. Check out the Super User Forum boards for details.   We're excited to connect with you and continue building a stronger community together.   See you at the call!  

Win free tickets to the Power Platform Conference | Summer of Solutions

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**

Copilot Cookbook Challenge | Week 2 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery: https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the 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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  @Dhanush 2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a   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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. Kasun_Pathirana1. ManishSolanki2. cloudatica2. madlad3. n/a3. SpongYe4. n/a4. n/a5. n/a5. n/a

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏   Markus Franz | LinkedIn  Power Apps: mmbr1606  

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form https://aka.ms/PPCCGotPowerSignup by July 12th with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Tuesday Tip | Accepting Solutions

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   To enhance our collaborative environment, it's important to acknowledge when your question has been answered satisfactorily. Here's a quick guide on how to accept a solution to your questions: Find the Helpful Reply: Navigate to the reply that has effectively answered your question.Accept as Solution: Look for the "Accept as Solution" button or link, usually located at the bottom of the reply.Confirm Your Selection: Clicking this button may prompt you for confirmation. Go ahead and confirm that this is indeed the solution.Acknowledgment: Once accepted, the reply will be highlighted, and the original post will be marked as "Solved". This helps other community members find the same solution quickly. By marking a reply as an accepted solution, you not only thank the person who helped you but also make it easier for others with similar questions to find answers. Let's continue to support each other by recognizing helpful contributions. 

Users online (2,373)