I have a rather complex collection where I add in a bunch of new columns...
It's not so bad basically
ClearCollect(CollectionName,AddColumns(ExistingTable as _existing,"My New Col1",somecode1,"My New Col2",somecode2))
What I want to do is perform calculations on these new columns...preferably when adding in the collection...at the time they are added. As the "somecode" for each column is pretty long, I really didn't want to repeat myself and I was hoping I could do this. But that doesn't appear to be the case...
If('My New Col1'="Mickey" && 'My New Col12'="Mouse","Awesome","Bummer")
Is there a way to do the above or must I either...
1) simply do it in another collection
2) re-type the whole code for the extra new column comparison - so this would seriously suffer some "DRY"
ClearCollect(CollectionName,AddColumns(ExistingTable as _existing,"My New Col1",somecode1,"My New Col2",somecode2,"GreatDay",If(somecode1 ="Mickey" and somecode2="Mouse","awesome","bummer")))
Here's the current full code, and my intent is that the new columns will have lengthy statements, so if that's the case it appears that I'll do another collection for simplicity's sake?
ClearCollect(
WorkloadSnapshot,
AddColumns(
Attendees As _Att,
"FlightArrivalDate",
LookUp(
EventFlightsArr,
Email = _Att.Email || If(!IsBlank(WorkerNo) && WorkerNo <> "Guest", WorkerNo = _Att.SourceId) || (Trim(Upper(LastName)) in _Att.'Last Name' && Trim(Upper(FirstName)) in _Att.'First Name'),
FlightArrivalDate
),
"FlightDepartDate",
LookUp(
EventFlightsDep,
Email = _Att.Email || If(!IsBlank(WorkerNo) && WorkerNo <> "Guest", WorkerNo = _Att.SourceId) || (Trim(Upper(LastName)) in _Att.'Last Name' && Trim(Upper(FirstName)) in _Att.'First Name'),
FlightDepartDate
),
"Hotel Bookings",
LookUp(
EventHotels,
Email = _Att.Email || If(!IsBlank(WorkerNo) && WorkerNo <> "Guest", WorkerNo = _Att.SourceId) || (Trim(Upper(LastName)) in _Att.'Last Name' && Trim(Upper(FirstName)) in _Att.'First Name'),
Bookings
),
"HotelMinCheckIn",
LookUp(
EventHotels,
Email = _Att.Email || If(!IsBlank(WorkerNo) && WorkerNo <> "Guest", WorkerNo = _Att.SourceId) || (Trim(Upper(LastName)) in _Att.'Last Name' && Trim(Upper(FirstName)) in _Att.'First Name'),
MinCheckIn
),
"HotelMaxCheckOut",
LookUp(
EventHotels,
Email = _Att.Email || If(!IsBlank(WorkerNo) && WorkerNo <> "Guest", WorkerNo = _Att.SourceId) || (Trim(Upper(LastName)) in _Att.'Last Name' && Trim(Upper(FirstName)) in _Att.'First Name'),
MaxCheckOut
),
"HotelNtsBooked",
LookUp(
EventHotels,
Email = _Att.Email || If(!IsBlank(WorkerNo) && WorkerNo <> "Guest", WorkerNo = _Att.SourceId) || (Trim(Upper(LastName)) in _Att.'Last Name' && Trim(Upper(FirstName)) in _Att.'First Name'),
NtsBooked
),
"HotelNtsExpected",
LookUp(
EventHotels,
Email = _Att.Email || If(!IsBlank(WorkerNo) && WorkerNo <> "Guest", WorkerNo = _Att.SourceId) || (Trim(Upper(LastName)) in _Att.'Last Name' && Trim(Upper(FirstName)) in _Att.'First Name'),
NtsExpected
)
)
);
Solved! Go to Solution.
Let's start with a Formula change...Please consider changing your Formula to the following:
ClearCollect(
WorkloadSnapshot,
ForAll(Attendees As _Att,
With({_lookup: LookUp(
EventFlightsArr,
Email = _Att.Email || If(!IsBlank(WorkerNo) && WorkerNo <> "Guest", WorkerNo = _Att.SourceId) || (Trim(Upper(LastName)) in _Att.'Last Name' && Trim(Upper(FirstName)) in _Att.'First Name'
)},
Patch(_Att,
{FlightArrivalDate: _lookup.FlightArrivalDate,
FlightDepartDate: _lookup.FlightDepartDate,
'Hotel Bookings': _lookup.Bookings,
HotelMinCheckIn: _lookup.MinCheckIn,
HotelMaxCheckOut: _lookup.MaxCheckOut,
HotelNtsBooked: _lookup.NtsBooked,
HotelNtsExpected: _lookup.NtsExpected
}
)
)
)
);
This will cut down on the length of your formula considerably and also reduce the number of Lookups that you are doing in the formula for performance.
Now...how about calculations? This can be done by just reshaping the table level after level.
For example (and consider this in context of the above Formula).
Let's say you wanted to do some calculation on the Flight dates to get the amount of time from Arrival to Depart...
ClearCollect(
WorkloadSnapshot,
AddColumns
ForAll(Attendees As _Att,
With({_lookup: LookUp(
EventFlightsArr,
Email = _Att.Email || If(!IsBlank(WorkerNo) && WorkerNo <> "Guest", WorkerNo = _Att.SourceId) || (Trim(Upper(LastName)) in _Att.'Last Name' && Trim(Upper(FirstName)) in _Att.'First Name'
)},
Patch(_Att,
{FlightArrivalDate: _lookup.FlightArrivalDate,
FlightDepartDate: _lookup.FlightDepartDate,
'Hotel Bookings': _lookup.Bookings,
HotelMinCheckIn: _lookup.MinCheckIn,
HotelMaxCheckOut: _lookup.MaxCheckOut,
HotelNtsBooked: _lookup.NtsBooked,
HotelNtsExpected: _lookup.NtsExpected
}
)
)
),
"TimeHere", DateDiff(FlightArrivalDate, FlightDepartDate, Days)
)
);
You can see in the above, we just added another column to the results for the Table from the ForAll, and we did a calculation on it.
You can continue to "build" on the calculations with more AddColumns.
Ex.
ClearCollect(
WorkloadSnapshot,
AddColumns(
AddColumns
ForAll(Attendees As _Att,
With({_lookup: LookUp(
EventFlightsArr,
Email = _Att.Email || If(!IsBlank(WorkerNo) && WorkerNo <> "Guest", WorkerNo = _Att.SourceId) || (Trim(Upper(LastName)) in _Att.'Last Name' && Trim(Upper(FirstName)) in _Att.'First Name'
)},
Patch(_Att,
{FlightArrivalDate: _lookup.FlightArrivalDate,
FlightDepartDate: _lookup.FlightDepartDate,
'Hotel Bookings': _lookup.Bookings,
HotelMinCheckIn: _lookup.MinCheckIn,
HotelMaxCheckOut: _lookup.MaxCheckOut,
HotelNtsBooked: _lookup.NtsBooked,
HotelNtsExpected: _lookup.NtsExpected
}
)
)
),
"TimeHere", DateDiff(FlightArrivalDate, FlightDepartDate, Days)
),
"someText", "You will be here " & Text(TimeHere) & " days and will checkin at " & HotelMinCheckIn &". We will see you depart " & FlightDepartDate
)
);
I hope this is helpful for you.
As usual - I am in awe of your wisdom. Thanks Randy.
Let's start with a Formula change...Please consider changing your Formula to the following:
ClearCollect(
WorkloadSnapshot,
ForAll(Attendees As _Att,
With({_lookup: LookUp(
EventFlightsArr,
Email = _Att.Email || If(!IsBlank(WorkerNo) && WorkerNo <> "Guest", WorkerNo = _Att.SourceId) || (Trim(Upper(LastName)) in _Att.'Last Name' && Trim(Upper(FirstName)) in _Att.'First Name'
)},
Patch(_Att,
{FlightArrivalDate: _lookup.FlightArrivalDate,
FlightDepartDate: _lookup.FlightDepartDate,
'Hotel Bookings': _lookup.Bookings,
HotelMinCheckIn: _lookup.MinCheckIn,
HotelMaxCheckOut: _lookup.MaxCheckOut,
HotelNtsBooked: _lookup.NtsBooked,
HotelNtsExpected: _lookup.NtsExpected
}
)
)
)
);
This will cut down on the length of your formula considerably and also reduce the number of Lookups that you are doing in the formula for performance.
Now...how about calculations? This can be done by just reshaping the table level after level.
For example (and consider this in context of the above Formula).
Let's say you wanted to do some calculation on the Flight dates to get the amount of time from Arrival to Depart...
ClearCollect(
WorkloadSnapshot,
AddColumns
ForAll(Attendees As _Att,
With({_lookup: LookUp(
EventFlightsArr,
Email = _Att.Email || If(!IsBlank(WorkerNo) && WorkerNo <> "Guest", WorkerNo = _Att.SourceId) || (Trim(Upper(LastName)) in _Att.'Last Name' && Trim(Upper(FirstName)) in _Att.'First Name'
)},
Patch(_Att,
{FlightArrivalDate: _lookup.FlightArrivalDate,
FlightDepartDate: _lookup.FlightDepartDate,
'Hotel Bookings': _lookup.Bookings,
HotelMinCheckIn: _lookup.MinCheckIn,
HotelMaxCheckOut: _lookup.MaxCheckOut,
HotelNtsBooked: _lookup.NtsBooked,
HotelNtsExpected: _lookup.NtsExpected
}
)
)
),
"TimeHere", DateDiff(FlightArrivalDate, FlightDepartDate, Days)
)
);
You can see in the above, we just added another column to the results for the Table from the ForAll, and we did a calculation on it.
You can continue to "build" on the calculations with more AddColumns.
Ex.
ClearCollect(
WorkloadSnapshot,
AddColumns(
AddColumns
ForAll(Attendees As _Att,
With({_lookup: LookUp(
EventFlightsArr,
Email = _Att.Email || If(!IsBlank(WorkerNo) && WorkerNo <> "Guest", WorkerNo = _Att.SourceId) || (Trim(Upper(LastName)) in _Att.'Last Name' && Trim(Upper(FirstName)) in _Att.'First Name'
)},
Patch(_Att,
{FlightArrivalDate: _lookup.FlightArrivalDate,
FlightDepartDate: _lookup.FlightDepartDate,
'Hotel Bookings': _lookup.Bookings,
HotelMinCheckIn: _lookup.MinCheckIn,
HotelMaxCheckOut: _lookup.MaxCheckOut,
HotelNtsBooked: _lookup.NtsBooked,
HotelNtsExpected: _lookup.NtsExpected
}
)
)
),
"TimeHere", DateDiff(FlightArrivalDate, FlightDepartDate, Days)
),
"someText", "You will be here " & Text(TimeHere) & " days and will checkin at " & HotelMinCheckIn &". We will see you depart " & FlightDepartDate
)
);
I hope this is helpful for you.
As usual - I am in awe of your wisdom. Thanks Randy.
I have a follow up question Randy as I have to deviate slightly here...
This is my revised version based on your input which works brilliantly...
As there are 3 different data sources and only the EventHotels involved multiple needs to lookup, I did the with for that one only and then did Lookups with the EventFlightsArr and EventFlightsDep.
I don't like the Lookups piece because I prefer to reference something like this...
Email = _Att.Email
Instead of like this...
Email = EventFlightsArr[@Email]
Is it possible to improve on this?
ClearCollect(
WorkloadSnapshot,
AddColumns(
ForAll(
Attendees As _Att,
With(
{
_EventHotels: LookUp(
EventHotels,
Email = _Att.Email || If(
!IsBlank(WorkerNo) && WorkerNo <> "Guest",
WorkerNo = _Att.SourceId
) || (Trim(Upper(LastName)) in _Att.'Last Name' && Trim(Upper(FirstName)) in _Att.'First Name')
)
},
Patch(
_Att,
{
HotelMinCheckIn: _EventHotels.MinCheckIn,
HotelMaxCheckOut: _EventHotels.MaxCheckOut,
HotelNtsBooked: _EventHotels.NtsBooked,
HotelNtsExpected: _EventHotels.NtsExpected,
HotelBookings: _EventHotels.Bookings
}
)
)
),
"FlightDepartDate",
LookUp(
EventFlightsDep,
Email = EventFlightsDep[@Email] || If(
!IsBlank(EventFlightsDep[@WorkerNo]) && EventFlightsDep[@WorkerNo] <> "Guest",
SourceId = EventFlightsDep[@WorkerNo]
) || (Trim(Upper('Last Name')) in EventFlightsDep[@LastName] && Trim(Upper('First Name')) in EventFlightsDep[@FirstName]),
FlightDepartDate
),
"FlightArrivalDate",
LookUp(
EventFlightsArr,
Email = EventFlightsArr[@Email] || If(
!IsBlank(EventFlightsArr[@WorkerNo]) && EventFlightsArr[@WorkerNo] <> "Guest",
SourceId = EventFlightsArr[@WorkerNo]
) || (Trim(Upper('Last Name')) in EventFlightsArr[@LastName] && Trim(Upper('First Name')) in EventFlightsArr[@FirstName]),
FlightArrivalDate
)
)
);
Have a go with this...
ClearCollect(
WorkloadSnapshot,
AddColumns(
ForAll(
Attendees As _Att,
With(
{
_EventHotels: LookUp(
EventHotels,
Email = _Att.Email || If(
!IsBlank(WorkerNo) && WorkerNo <> "Guest",
WorkerNo = _Att.SourceId
) || (Trim(Upper(LastName)) in _Att.'Last Name' && Trim(Upper(FirstName)) in _Att.'First Name')
),
_EventFlightsDep: LookUp(
EventFlightsDep As _departs,
_departs.Email = _Att.Email ||
If(!IsBlank(_departs.WorkerNo) && (_departs.@WorkerNo <> "Guest"), SourceId = _departs.WorkerNo) ||
(Trim(Upper('Last Name')) in =_departs.LastName && Trim(Upper('First Name')) in _dpearts.FirstName)
),
_EventFlightsArr: LookUp(
EventFlightsArr As _arrives,
_arrives.Email = _Att.Email ||
If(!IsBlank(_arrives.WorkerNo) && (_arrives.WorkerNo <> "Guest"), SourceId = _arrives.WorkerNo) ||
(Trim(Upper('Last Name')) in _arrives.LastName && Trim(Upper('First Name')) in _arrives.FirstName)
)
},
Patch(
_Att,
{
HotelMinCheckIn: _EventHotels.MinCheckIn,
HotelMaxCheckOut: _EventHotels.MaxCheckOut,
HotelNtsBooked: _EventHotels.NtsBooked,
HotelNtsExpected: _EventHotels.NtsExpected,
HotelBookings: _EventHotels.Bookings
}
)
)
),
"FlightDepartDate", _EventFlightsDep.FlightDepartDate,
"FlightArrivalDate", _EventFlightsArr.FlightArrivalDate
)
);
Just because this is pretty cool, I'm sharing the revised code ... yet, to work on the error variables but now I have everything and it's cleaner than it was before and easier for the rest of my team to do the presentation layer in the gallery!
ClearCollect(
WorkloadSnapshot,
AddColumns(
ForAll(
Attendees As _Att,
With(
{
_EventHotels: LookUp(
EventHotels,
Email = _Att.Email || If(
!IsBlank(WorkerNo) && WorkerNo <> "Guest",
WorkerNo = _Att.SourceId
) || (Trim(Upper(LastName)) in _Att.'Last Name' && Trim(Upper(FirstName)) in _Att.'First Name')
),
_EventFlightsDep: LookUp(
EventFlightsDep As _departs,
_departs.Email = _Att.Email || If(
!IsBlank(_departs.WorkerNo) && _departs.WorkerNo <> "Guest",
_departs.WorkerNo = _Att.SourceId
) || (Trim(Upper(_departs.LastName)) in _Att.'Last Name' && Trim(Upper(_departs.FirstName)) in _Att.'First Name')
),
_EventFlightsArr: LookUp(
EventFlightsArr As _arrives,
_arrives.Email = _Att.Email || If(
!IsBlank(_arrives.WorkerNo) && _arrives.WorkerNo <> "Guest",
_arrives.WorkerNo = _Att.SourceId
) || (Trim(Upper(_arrives.LastName)) in _Att.'Last Name' && Trim(Upper(_arrives.FirstName)) in _Att.'First Name')
)
},
Patch(
_Att,
{
HotelMinCheckIn: _EventHotels.MinCheckIn,
HotelMaxCheckOut: _EventHotels.MaxCheckOut,
HotelNtsBooked: _EventHotels.NtsBooked,
HotelNtsExpected: _EventHotels.NtsExpected,
HotelBookings: _EventHotels.Bookings,
FlightArrivalDate: _EventFlightsArr.FlightArrivalDate,
FlightDepartDate: _EventFlightsDep.FlightDepartDate
}
) // end of patch
) // end of with
), // end of forall
/* add remaining columns for the gallery to better function */
"isQcError",false,
"isHotelError",false,
"isAirError",false,
"isAirInError",false,
"isAirOutError",false
)
);
haring what I think is the
@sasrsc
Yes...I am all about the maintainability of formulas! When another person has to revise something, the cleaner the better. I also personally hate repeating any formula (like all the Lookups you had at first) - mostly because, if all of a sudden there was some other criteria that was needed for the Lookup...then you would have to adjust every one of them...that can get painful (especially if you accidentally miss one).
Anyway, I am glad to help out!
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