cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
AuburnMist
Resolver I
Resolver I

Dynamic data source using Switch, then add filters

Hello,

 

I have an app that displays employee leave records in a gallery. Due to the large number of employees, I have built a SharePoint list for a number of different fiscal years. When the Supervisor is entering leave records, they must first select the fiscal year using a dropdown. Based on the selection in the drop down; (2021/2022, 2022/2022, etc.), I am able to use the Switch function in both my form and my gallery so that the records save to the right list in SharePoint. 

 

The issue I am having is that I cannot work out how to apply filters in my gallery along with the Switch function. Is this even possible? 

 

The Items property for both my form and my gallery is; 

Switch(cmbFiscalYear.Selected.Value, "2021/2022", EmployeeLeave2021/2022, "2022/2023", EmployeeLeave2022/2023)

I need to add the above to this code inside of this, somehow:

SortByColumns(
  Filter(
     [my dynamic data source goes here?],
     EmployeeName = galSelectEmployee.Selected.Result,
     StartDate >= 'date(From)Leave'.Value,
     StartDate <= 'date(To)Leave'.Value && (AbsenceType.Value = cmbAbsenceType.Selected.Value || cmbAbsenceType.Selected.Value = Blank()) && (Status.Value = cmbStatus.Selected.Value || cmbStatus.Selected.Value = Blank())
        ),
        "StartDate",
        If(
            SortDescending,
            Ascending,
            Descending
        )
    )


What appears to be happening is that PowerApps is not recognizing the columns inside of the list, even though each list is exactly the same (only the name of the list is different). The error message indicates that EmployeeName is not recognized, same for StartDate, AbsenceType and Status. 

 

Any way around this? 

 

Thanks!

1 ACCEPTED SOLUTION

Accepted Solutions
AuburnMist
Resolver I
Resolver I

Hi! Thank you so much for your thorough advice! I carefully reviewed all of your suggested solutions and had already tried a couple before your response came in. But I did not try the final two. I just attempted them and the last one proposed, was the winner! Yes, the code is quite long, but it operates very quickly so I'm not concerned about the length at all. Thank you so very much! 

 

View solution in original post

3 REPLIES 3
poweractivate
Most Valuable Professional
Most Valuable Professional

@AuburnMist Regarding your formula:

 

//pseudo-formula, untested, adjust as needed

SortByColumns
(
     Filter
     (
         Switch
         (
            cmbFiscalYear.Selected.Value
           ,"2021/2022"
           ,EmployeeLeave2021/2022
           ,"2022/2023"
           ,EmployeeLeave2022/2023
         )
        ,EmployeeName = galSelectEmployee.Selected.Result
           && StartDate >= 'date(From)Leave'.Value,
           && StartDate <= 'date(To)Leave'.Value 
           && 
             (
                AbsenceType.Value = cmbAbsenceType.Selected.Value 
                  || cmbAbsenceType.Selected.Value = Blank()
             ) 
           && 
             (
               Status.Value = cmbStatus.Selected.Value 
                  || cmbStatus.Selected.Value = Blank()
             )
     )
    ,"StartDate"
    ,If
     (
         SortDescending
        ,Ascending
        ,Descending
     )
)
    

 

Although I did not test it, the formula that you gave seems to be correct in terms of syntax. If not, see if using the above version works better, but I think it is probably identical to the one you gave.

 

To resolve the issue, you could try this:

 

1. Try using only one of the data sources by themselves. First try EmployeeLeave2021/2022. Then try  just EmployeeLeave2022/2023. See which one gives the error, or see if both give the error.

 

//pseudo-formula, untested, adjust as needed

SortByColumns
(
     Filter
     (
         EmployeeLeave2021/2022
        ,EmployeeName = galSelectEmployee.Selected.Result
....

 

 

2. If just one gives the error,  which I suspect it might do, let's suppose for example only EmployeeLeave2022/2023 - then make a note which one gives the error. 

 

3. Based on the error, try revising your formula like this:

 

//pseudo-formula, untested, adjust as needed. Replace YourTableName with the name of the data source it is complaining about.
...
        ,YourTableName[@EmployeeName] = galSelectEmployee.Selected.Result
...

 

 

4. If the above does not work, then EmployeeName is not actually the name of the field, and it only seemed like the two lists were identical, but were not. See what field it really wants for just EmployeeLeave2022/2023 . Let's suppose for sake of example it is just EmplName . If so, then try this:

 

//pseudo-formula, untested, adjust as needed

SortByColumns
(
     Filter
     (
         Switch
         (
            cmbFiscalYear.Selected.Value
           ,"2021/2022"
           ,EmployeeLeave2021/2022
           ,"2022/2023"
           ,EmployeeLeave2022/2023
         )
        ,Switch
         (
            cmbFiscalYear.Selected.Value
           ,"2021/2022"
           ,EmployeeName = galSelectEmployee.Selected.Result
           ,"2022/2023"
           ,EmplName = galSelectEmployee.Selected.Result
         )
 ......

 

 

5. If the above does not work, try using the disambiguation operator once more to see if it works:

 

//pseudo-formula, untested, adjust as needed

SortByColumns
(
     Filter
     (
         Switch
         (
            cmbFiscalYear.Selected.Value
           ,"2021/2022"
           ,EmployeeLeave2021/2022
           ,"2022/2023"
           ,EmployeeLeave2022/2023
         )
        ,Switch
         (
            cmbFiscalYear.Selected.Value
           ,"2021/2022"
           ,EmployeeLeave2021/2022[@EmployeeName] = galSelectEmployee.Selected.Result
           ,"2022/2023"
           ,EmployeeLeave2022/2023[@EmployeeName] = galSelectEmployee.Selected.Result
         )
 ......

 

 

6. If nothing like the above works, or you keep on getting more and more errors that all have to be individually fixed with more of the same kind of switch statements like the above on more clauses, then switching on every variation on so many clauses may end up seriously becoming more cumbersome and difficult to maintain, than just outright repeating the whole giant formula again by switching on the entire thing instead. If that ends up working better for you, then you should try that instead:

 

//pseudo-formula, untested, adjust as needed

Switch
(
     cmbFiscalYear.Selected.Value
	,"2021/2022"
	,SortByColumns
	 (
	 	 Filter
	 	 (
	 		 EmployeeLeave2021/2022
	 		,EmployeeName = galSelectEmployee.Selected.Result
	 		   && StartDate >= 'date(From)Leave'.Value,
	 		   && StartDate <= 'date(To)Leave'.Value 
	 		   && 
	 			 (
	 				AbsenceType.Value = cmbAbsenceType.Selected.Value 
	 				  || cmbAbsenceType.Selected.Value = Blank()
	 			 ) 
	 		   && 
	 			 (
	 			   Status.Value = cmbStatus.Selected.Value 
	 				  || cmbStatus.Selected.Value = Blank()
	 			 )
	 	 )
	 	,"StartDate"
	 	,If
	 	 (
	 		 SortDescending
	 		,Ascending
	 		,Descending
	 	 )
	 )
	,"2022/2023"
	,SortByColumns
	 (
	 	 Filter
	 	 (
	 		 EmployeeLeave2022/2023
	 		,EmployeeName = galSelectEmployee.Selected.Result //adjust as needed
	 		   && StartDate >= 'date(From)Leave'.Value, //adjust as needed
	 		   && StartDate <= 'date(To)Leave'.Value  //adjust as needed
	 		   && 
	 			 (
	 				AbsenceType.Value = cmbAbsenceType.Selected.Value //adjust as needed
	 				  || cmbAbsenceType.Selected.Value = Blank() //adjust as needed
	 			 ) 
	 		   && 
	 			 (
	 			   Status.Value = cmbStatus.Selected.Value  //adjust as needed
	 				  || cmbStatus.Selected.Value = Blank() //adjust as needed
	 			 )
	 	 )
	 	,"StartDate" //adjust as needed
	 	,If //adjust as needed
	 	 (
	 		 SortDescending //adjust as needed
	 		,Ascending //adjust as needed
	 		,Descending //adjust as needed
	 	 )
	 )   	
)    

 

 

See if it helps @AuburnMist 

AuburnMist
Resolver I
Resolver I

Hi! Thank you so much for your thorough advice! I carefully reviewed all of your suggested solutions and had already tried a couple before your response came in. But I did not try the final two. I just attempted them and the last one proposed, was the winner! Yes, the code is quite long, but it operates very quickly so I'm not concerned about the length at all. Thank you so very much! 

 

poweractivate
Most Valuable Professional
Most Valuable Professional

@AuburnMist 

 

Yes, in general, just switching on the whole thing and even repeating the same giant inner formula again, is just easier. Even if it worked by using inner witch statements, if you need to put so many Switch statements for every possible variation in the inner formulas it's even more difficult to maintain in that case, and may even end up actually being longer itself than the seemingly giant formula repeating the huge inner formula! It is actually the single outer switch with the repeated giant inner formulas, that ironically may end up being easier to maintain and even, possibly itself be shorter, than the alternative of attempting to repeat the same switch statement to account for variations in the inner formula.

 

However, just in case:

 

Not sure you have time to try it, but I am curious if the following works. I suspect it won't work though:

 

//pseudo-formula, untested, adjust as needed
With
(
	{
		myDataSource: Switch
			 (
				cmbFiscalYear.Selected.Value
			   ,"2021/2022"
			   ,EmployeeLeave2021/2022
			   ,"2022/2023"
			   ,EmployeeLeave2022/2023
			 )
	}
	,SortByColumns
	 (
	 	 Filter
	 	 (
	 		 myDataSource
	 		,EmployeeName = galSelectEmployee.Selected.Result
	 		   && StartDate >= 'date(From)Leave'.Value,
	 		   && StartDate <= 'date(To)Leave'.Value 
	 		   && 
	 			 (
	 				AbsenceType.Value = cmbAbsenceType.Selected.Value 
	 				  || cmbAbsenceType.Selected.Value = Blank()
	 			 ) 
	 		   && 
	 			 (
	 			   Status.Value = cmbStatus.Selected.Value 
	 				  || cmbStatus.Selected.Value = Blank()
	 			 )
	 	 )
	 	,"StartDate"
	 	,If
	 	 (
	 		 SortDescending
	 		,Descending
	 		,Ascending
	 	 )
	 )
) 

 

 

If not, I wonder if replacing the Switch with the below works (however, the Switch is preferable to the below):

 

If
(
   cmbFiscalYear.Selected.Value = "2021/2022"
  ,EmployeeLeave2021/2022
  ,If
   (
      cmbFiscalYear.Selected.Value ="2022/2023"
     ,EmployeeLeave2022/2023
     ,EmployeeLeave2022/2023 //add a default clause and use one of the data sources, to give it the data source it likes most anyway, especially prefer which one it complains least about when you try it by itself, and put that one here so it always has something valid, and never a blank value. This will ideally never be reached - but in case it ever is, or to make the evaluator think it's valid anyway, just try this anyway and see if it for some reason works
   )
)

 

 If for some reason the above works, see if the below works:

 

Switch
(
   cmbFiscalYear.Selected.Value
  ,"2021/2022"
  ,EmployeeLeave2021/2022
  ,"2022/2023"
  ,EmployeeLeave2022/2023
  ,EmployeeLeave2022/2023//add a default clause and use one of the data sources, to give it the data source it likes most anyway, especially prefer which one it complains least about when you try it by itself, and put that one here so it always has something valid, and never a blank value. This will ideally never be reached - but in case it ever is, or to make the evaluator think it's valid anyway, just try this anyway and see if it for some reason works
)

 

And then trying the above (both of them) but without the "With" and using the original way you had it, but just making sure to have that default clause in there - try the Switch version, and the If version - see if either of them work. 

 

I did not try these above, however, I was curious if for some reason, any of the above actually end up working. If you did want to try it (and had a moment) and for some reason it really worked, I'd be curious to know. If it really does work, you may prefer it then.

 

You always could use the long formula, which is still probably the best way, especially if there's more than one variation since multiple Switch statements to account for multiple variations may actually end up being more difficult to maintain, and actually end up being possibly longer itself, even than simply using one giant Switch statement with the repeated giant inner formulas!

 

It is possible, however, that you really do have absolutely no variation in the List. If that's the case, you can try the above in case it works. However, if you discover that ultimately, there was something as minor as a single letter difference in as few as two columns, it's probably better to use the giant Switch statement anyway.

 

I presume that even if your two data sources are really "identical", the above might still not work because Power Apps may not like this sort of situation on trying to use two different data sources here in this way, and may believe that the schema does not match, cannot properly infer the schema for the inner parts of the formula, and ultimately may just prefer the giant switch statement instead to begin with. In general, the giant switch statement is probably generally easier. I included this response just in case that for some reason, anything I mentioned here actually worked and if so, it could, in some select few cases, reduce the repetition and create some benefit or could be preferable in some select few situations (however, there is still a possibility that it could complain with an error later on changes of either data source, and the giant Switch statement is in a way, safer and probably just easier to maintain in general). 

 

 

 

 

Helpful resources

Announcements

Copilot Cookbook Challenge | Week 3 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.  n/a2.   @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     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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. Parul_Yadav_Neo1. n/a2. SpongYe2. n/a3. n/a3. n/a4. n/a4. n/a5. n/a5. n/a

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

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 the end of July 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 

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

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  

Top Solution Authors
Top Kudoed Authors
Users online (4,227)