I have a gallery that I want to repurpose instead of making individual screens for all of my Position.
Currently I have this on the Items property of the gallery
With({_items:
Filter(
'POWER SYSTEM ELECTRICIAN Work Hours',
'Apprentice Name' = Upper(varCurrentUserFullName),
'Year Entered' >= 2020
)
},
Sort(
AddColumns(
GroupBy(_items,
"Year", "_data"
),
"_totals",
{
Codes:Sum(_items,Code),
Safety:Sum (_items,Safety),
BluePrints: Sum (_items,Blueprints),
WiringEqiup: Sum(_items,'Wiring Equip'),
InstallSubstationEquip: Sum(_items,'Install Substation Equip'),
InstallDispEquipment:Sum (_items,'Install Disp Equipment'),
InstallMotorsGenerators: Sum(_items,'Install Motors Generators'),
ShopWorkElectEquip: Sum(_items,'Shop Work Elect Equip'),
PwrWiringBusBarInstall: Sum(_items,'Pwr Wiring Bus Bar Install'),
Welding:Sum (_items,Welding),
OJTMeterRelayTech: Sum(_items,'OJT Meter Relay Tech'),
OJTLineman: Sum(_items,'OJT Lineman'),
OJTDistDispatcher: Sum(_items,'OJT Dispatch'),
OJTSrSystemOperator: Sum(_items,'OJT Sr System Oper.'),
RSISupvd: Sum(_items,'RSI-Supvd'),
RSIUnSupvd: Sum(_items,'RSI-UnSupvd')
}
),
Year,
Ascending
)
)
Works great does what it is supposed to do, however I want to do a switch/if to have it changed based on the users position which I have in varPosition.
I tried this
With({_items:
Filter(
Switch(varPosition,
"Power System Electrician",
'POWER SYSTEM ELECTRICIAN Work Hours',
"Fleet Utility Mechanic",
'Fleet Utility Mechanic Work Hours'),
'Apprentice Name' = Upper(varCurrentUserFullName),
'Year Entered' >= 2020
)
},
Sort(
AddColumns(
GroupBy(_items,
"Year", "_data"
),
"_totals",
{
Codes:Sum(_items,Code),
Safety:Sum (_items,Safety),
BluePrints: Sum (_items,Blueprints),
WiringEqiup: Sum(_items,'Wiring Equip'),
InstallSubstationEquip: Sum(_items,'Install Substation Equip'),
InstallDispEquipment:Sum (_items,'Install Disp Equipment'),
InstallMotorsGenerators: Sum(_items,'Install Motors Generators'),
ShopWorkElectEquip: Sum(_items,'Shop Work Elect Equip'),
PwrWiringBusBarInstall: Sum(_items,'Pwr Wiring Bus Bar Install'),
Welding:Sum (_items,Welding),
OJTMeterRelayTech: Sum(_items,'OJT Meter Relay Tech'),
OJTLineman: Sum(_items,'OJT Lineman'),
OJTDistDispatcher: Sum(_items,'OJT Dispatch'),
OJTSrSystemOperator: Sum(_items,'OJT Sr System Oper.'),
RSISupvd: Sum(_items,'RSI-Supvd'),
RSIUnSupvd: Sum(_items,'RSI-UnSupvd')
}
),
Year,
Ascending
)
)
However now everything is broke in all of the other stuff
I know I am close but my syntax is a bit off, would really appreciate some help.
Solved! Go to Solution.
Hi @Dorinda
Based on this scenario, I think it's easiest to Switch on the whole thing instead of the individual components such as just the List name or just the Records, etc. because of there being one or more substantial differences in the schema in one of the two lists.
Also, if you already have to Switch on more than one part of your original formula, you would have to repeat the same Switch statement more than once (at least twice), i.e. multiple times, at that point it would be best to instead have just one Switch statement and to have it for the whole thing!
(I'm suspecting it's the second List:
'Fleet Utility Mechanic Work Hours'
for which it is really complaining about.
As a troubleshooting step, try to remove the Switch in your original formula, and try only one of the Lists.
I recommend trying with the first list only.
'POWER SYSTEM ELECTRICIAN Work Hours'
If there are no errors (and I suspect there are probably none when using this List), now try the second list
'Fleet Utility Mechanic Work Hours'
If there are errors now, there's where your issue is. You are trying to return a Record for this List which does not match the schema, so Power Apps simply cannot do it.
However, what you want to do should still be possible.
Based on the above, I'd recommend switching on the whole thing - and I mean you have a whole second With statement and everything in it for the other Switch case and the other List.
Here's how you would do it:
In case you want to try it on your own first, I will put the below in a Spoiler tag, and you may reveal it in case you want to check for a starting approach:
//untested pseudo-formula - you may need to modify it as appropriate
Switch
(
varPosition
,"Power System Electrician"
,With
(
{_items:Filter
(
'POWER SYSTEM ELECTRICIAN Work Hours'
,'Apprentice Name' = Upper(varCurrentUserFullName)
,'Year Entered' >= 2020
)
}
,Sort(
AddColumns(
GroupBy(
_items
,"Year"
,"_data"
)
,"_totals"
,{
Codes:Sum(_items,Code),
Safety:Sum (_items,Safety),
BluePrints: Sum (_items,Blueprints),
WiringEqiup: Sum(_items,'Wiring Equip'),
InstallSubstationEquip: Sum(_items,'Install Substation Equip'),
InstallDispEquipment:Sum (_items,'Install Disp Equipment'),
InstallMotorsGenerators: Sum(_items,'Install Motors Generators'),
ShopWorkElectEquip: Sum(_items,'Shop Work Elect Equip'),
PwrWiringBusBarInstall: Sum(_items,'Pwr Wiring Bus Bar Install'),
Welding:Sum (_items,Welding),
OJTMeterRelayTech: Sum(_items,'OJT Meter Relay Tech'),
OJTLineman: Sum(_items,'OJT Lineman'),
OJTDistDispatcher: Sum(_items,'OJT Dispatch'),
OJTSrSystemOperator: Sum(_items,'OJT Sr System Oper.'),
RSISupvd: Sum(_items,'RSI-Supvd'),
RSIUnSupvd: Sum(_items,'RSI-UnSupvd')
}
)
,Year
,Ascending
)
)
,"Fleet Utility Mechanic"
,With
(
{_items:Filter
(
'Fleet Utility Mechanic Work Hours'
,'Apprentice Name' = Upper(varCurrentUserFullName) //adjust if needed
,'Year Entered' >= 2020 //adjust if needed
)
}
,Sort(
AddColumns(
GroupBy(
_items
,"Year" //adjust if needed
,"_data"
)
,"_totals"
,{
//adjust ANY or ALL of the below, where applicable and if needed
Codes:Sum(_items,Code),
Safety:Sum (_items,Safety),
BluePrints: Sum (_items,Blueprints),
WiringEqiup: Sum(_items,'Wiring Equip'),
InstallSubstationEquip: Sum(_items,'Install Substation Equip'),
InstallDispEquipment:Sum (_items,'Install Disp Equipment'),
InstallMotorsGenerators: Sum(_items,'Install Motors Generators'),
ShopWorkElectEquip: Sum(_items,'Shop Work Elect Equip'),
PwrWiringBusBarInstall: Sum(_items,'Pwr Wiring Bus Bar Install'),
Welding:Sum (_items,Welding),
OJTMeterRelayTech: Sum(_items,'OJT Meter Relay Tech'),
OJTLineman: Sum(_items,'OJT Lineman'),
OJTDistDispatcher: Sum(_items,'OJT Dispatch'),
OJTSrSystemOperator: Sum(_items,'OJT Sr System Oper.'),
RSISupvd: Sum(_items,'RSI-Supvd'),
RSIUnSupvd: Sum(_items,'RSI-UnSupvd')
}
)
,Year
,Ascending
)
)
)
Check if it helps @Dorinda
In your formula
With({_items:Filter
(
Switch
(
varPosition,
"Power System Electrician",
'POWER SYSTEM ELECTRICIAN Work Hours',
"Fleet Utility Mechanic",
'Fleet Utility Mechanic Work Hours'
),
'Apprentice Name' = Upper(varCurrentUserFullName),
'Year Entered' >= 2020
)
},
Sort(
AddColumns(
GroupBy(_items,
"Year", "_data"
),
"_totals",
{
Codes:Sum(_items,Code),
Safety:Sum (_items,Safety),
BluePrints: Sum (_items,Blueprints),
WiringEqiup: Sum(_items,'Wiring Equip'),
InstallSubstationEquip: Sum(_items,'Install Substation Equip'),
InstallDispEquipment:Sum (_items,'Install Disp Equipment'),
InstallMotorsGenerators: Sum(_items,'Install Motors Generators'),
ShopWorkElectEquip: Sum(_items,'Shop Work Elect Equip'),
PwrWiringBusBarInstall: Sum(_items,'Pwr Wiring Bus Bar Install'),
Welding:Sum (_items,Welding),
OJTMeterRelayTech: Sum(_items,'OJT Meter Relay Tech'),
OJTLineman: Sum(_items,'OJT Lineman'),
OJTDistDispatcher: Sum(_items,'OJT Dispatch'),
OJTSrSystemOperator: Sum(_items,'OJT Sr System Oper.'),
RSISupvd: Sum(_items,'RSI-Supvd'),
RSIUnSupvd: Sum(_items,'RSI-UnSupvd')
}
),
Year,
Ascending
)
)
If you are switching between two whole data sources and you have to re-use the other part, there are some issues to consider
1. Are all columns the exact same name and columns schema?
2. Is 'Year Entered' a valid column and of the same type in both sources?
If the answer to any of the above is "no" then it's not enough to Switch on the Data source, you have to Switch on the whole column that's returned too and make adjustments if needed on where there's any differences in the schema.
At the very least, 'Year Entered' cannot be used for both.
I don't think I can give a complete formula based on the info provided, because:
A. Is the Grouping by Year necessary here? Whether it is or not will impact what solution is best.
B. If the Grouping by Year is necessary here, is that true for BOTH data sources you're switching on, or just one?
C. Is it intended to return the Sum of those specific columns for BOTH Switch cases of the Variable?
D. Are all the columns having the exact same name and schema in general in both data sources? Whether it is or not will impact what solution is best.
See if it helps as starting point @Dorinda
Hi @Dorinda
Based on this scenario, I think it's easiest to Switch on the whole thing instead of the individual components such as just the List name or just the Records, etc. because of there being one or more substantial differences in the schema in one of the two lists.
Also, if you already have to Switch on more than one part of your original formula, you would have to repeat the same Switch statement more than once (at least twice), i.e. multiple times, at that point it would be best to instead have just one Switch statement and to have it for the whole thing!
(I'm suspecting it's the second List:
'Fleet Utility Mechanic Work Hours'
for which it is really complaining about.
As a troubleshooting step, try to remove the Switch in your original formula, and try only one of the Lists.
I recommend trying with the first list only.
'POWER SYSTEM ELECTRICIAN Work Hours'
If there are no errors (and I suspect there are probably none when using this List), now try the second list
'Fleet Utility Mechanic Work Hours'
If there are errors now, there's where your issue is. You are trying to return a Record for this List which does not match the schema, so Power Apps simply cannot do it.
However, what you want to do should still be possible.
Based on the above, I'd recommend switching on the whole thing - and I mean you have a whole second With statement and everything in it for the other Switch case and the other List.
Here's how you would do it:
In case you want to try it on your own first, I will put the below in a Spoiler tag, and you may reveal it in case you want to check for a starting approach:
//untested pseudo-formula - you may need to modify it as appropriate
Switch
(
varPosition
,"Power System Electrician"
,With
(
{_items:Filter
(
'POWER SYSTEM ELECTRICIAN Work Hours'
,'Apprentice Name' = Upper(varCurrentUserFullName)
,'Year Entered' >= 2020
)
}
,Sort(
AddColumns(
GroupBy(
_items
,"Year"
,"_data"
)
,"_totals"
,{
Codes:Sum(_items,Code),
Safety:Sum (_items,Safety),
BluePrints: Sum (_items,Blueprints),
WiringEqiup: Sum(_items,'Wiring Equip'),
InstallSubstationEquip: Sum(_items,'Install Substation Equip'),
InstallDispEquipment:Sum (_items,'Install Disp Equipment'),
InstallMotorsGenerators: Sum(_items,'Install Motors Generators'),
ShopWorkElectEquip: Sum(_items,'Shop Work Elect Equip'),
PwrWiringBusBarInstall: Sum(_items,'Pwr Wiring Bus Bar Install'),
Welding:Sum (_items,Welding),
OJTMeterRelayTech: Sum(_items,'OJT Meter Relay Tech'),
OJTLineman: Sum(_items,'OJT Lineman'),
OJTDistDispatcher: Sum(_items,'OJT Dispatch'),
OJTSrSystemOperator: Sum(_items,'OJT Sr System Oper.'),
RSISupvd: Sum(_items,'RSI-Supvd'),
RSIUnSupvd: Sum(_items,'RSI-UnSupvd')
}
)
,Year
,Ascending
)
)
,"Fleet Utility Mechanic"
,With
(
{_items:Filter
(
'Fleet Utility Mechanic Work Hours'
,'Apprentice Name' = Upper(varCurrentUserFullName) //adjust if needed
,'Year Entered' >= 2020 //adjust if needed
)
}
,Sort(
AddColumns(
GroupBy(
_items
,"Year" //adjust if needed
,"_data"
)
,"_totals"
,{
//adjust ANY or ALL of the below, where applicable and if needed
Codes:Sum(_items,Code),
Safety:Sum (_items,Safety),
BluePrints: Sum (_items,Blueprints),
WiringEqiup: Sum(_items,'Wiring Equip'),
InstallSubstationEquip: Sum(_items,'Install Substation Equip'),
InstallDispEquipment:Sum (_items,'Install Disp Equipment'),
InstallMotorsGenerators: Sum(_items,'Install Motors Generators'),
ShopWorkElectEquip: Sum(_items,'Shop Work Elect Equip'),
PwrWiringBusBarInstall: Sum(_items,'Pwr Wiring Bus Bar Install'),
Welding:Sum (_items,Welding),
OJTMeterRelayTech: Sum(_items,'OJT Meter Relay Tech'),
OJTLineman: Sum(_items,'OJT Lineman'),
OJTDistDispatcher: Sum(_items,'OJT Dispatch'),
OJTSrSystemOperator: Sum(_items,'OJT Sr System Oper.'),
RSISupvd: Sum(_items,'RSI-Supvd'),
RSIUnSupvd: Sum(_items,'RSI-UnSupvd')
}
)
,Year
,Ascending
)
)
)
Check if it helps @Dorinda
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!
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
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.
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