I have an array of email addresses like this:
[
"email@email.com",
"another@email.com",
"qwerty@abc.com"
]
The array can contain anywhere from 1 to thousands of emails. I want to change the array so that the emails are in groups of 300 e.g.
[
{
"email@email.com",
"another@email.com",
"qwerty@abc.com"
...to 300
},
{
"more@email.com"
...to another 300
}
]
What is the best way to achieve this?
Solved! Go to Solution.
Quick Answer
You will need to use the take() and skip() functions in an expression.
It's best to do this with the length() of the original array in mind.
If you're already pretty good with the logic side, then that should be all you need.
Solution
Here's my flow to handle this, you will replace the "3" with "100".
This could be minimised a bit by moving some of the actions into expressions, but this shows you the logic I was aiming for.
I will edit in explanation shortly.
You can read on if you like.
Logic
Essentially, this works out how many runs are needed to divide the array into chunks of 3 (100 for you), then, for the set amount of turns, it will set the arrayVAR from the arrayWorkerVAR, with increasingly less (by 3) items than before.
Each run, it will also place those three deleted items into an object that will be placed into the newArrayVAR array.
Expressions/Code Used
Initialize divvyVAR
This looks more complicated than it is (see explanation) but essentially a normal division doesn't see the "remainder" so I had to see if the number of loops needed one more.
if(contains(string(div(float(length(variables('arrayVAR'))), 3)), '.'), add(div(length(variables('arrayVAR')), 3), 1), div(length(variables('arrayVAR')), 3))
jsonObject
This uses the take() function to take the first 3 items from the arrayVAR variable and create a new array.
The code:
{
"chunk": @{take(variables('arrayVAR'), 3)}
}
The expression within:
take(variables('arrayVAR'), 3)
Set arrayWorkerVAR
This uses the skip() function to skip over the first 3 items in the arrayVAR variable, to create a new array.
The reason the flow needs an extra array here, is because you cannot set a variable's value from itself.
skip(variables('arrayVAR'), 3)
Detailed Explanation for the Long IF Statement in divvyVAR
Explaining quickly the basic functions:
So ... if I get a floating point number from my division, then I will need an extra step to catch the remainder of the items in the array ... meaning:
IF - The result of dividing the number of entries in the original array produces a number with a decimal point, then the contains() function will return TRUE.
THEN - Add 1 to the number of a *normal* (not floating point) division of the length.
ELSE - Just take the normal division of the number.
Quick Answer
You will need to use the take() and skip() functions in an expression.
It's best to do this with the length() of the original array in mind.
If you're already pretty good with the logic side, then that should be all you need.
Solution
Here's my flow to handle this, you will replace the "3" with "100".
This could be minimised a bit by moving some of the actions into expressions, but this shows you the logic I was aiming for.
I will edit in explanation shortly.
You can read on if you like.
Logic
Essentially, this works out how many runs are needed to divide the array into chunks of 3 (100 for you), then, for the set amount of turns, it will set the arrayVAR from the arrayWorkerVAR, with increasingly less (by 3) items than before.
Each run, it will also place those three deleted items into an object that will be placed into the newArrayVAR array.
Expressions/Code Used
Initialize divvyVAR
This looks more complicated than it is (see explanation) but essentially a normal division doesn't see the "remainder" so I had to see if the number of loops needed one more.
if(contains(string(div(float(length(variables('arrayVAR'))), 3)), '.'), add(div(length(variables('arrayVAR')), 3), 1), div(length(variables('arrayVAR')), 3))
jsonObject
This uses the take() function to take the first 3 items from the arrayVAR variable and create a new array.
The code:
{
"chunk": @{take(variables('arrayVAR'), 3)}
}
The expression within:
take(variables('arrayVAR'), 3)
Set arrayWorkerVAR
This uses the skip() function to skip over the first 3 items in the arrayVAR variable, to create a new array.
The reason the flow needs an extra array here, is because you cannot set a variable's value from itself.
skip(variables('arrayVAR'), 3)
Detailed Explanation for the Long IF Statement in divvyVAR
Explaining quickly the basic functions:
So ... if I get a floating point number from my division, then I will need an extra step to catch the remainder of the items in the array ... meaning:
IF - The result of dividing the number of entries in the original array produces a number with a decimal point, then the contains() function will return TRUE.
THEN - Add 1 to the number of a *normal* (not floating point) division of the length.
ELSE - Just take the normal division of the number.
This is fantastic thank you, I will try this out today and let you know how I get on.
You, sir, are a fantastic human being. This does exactly what I wanted! Very comprehensive answer and well explained, thank you so much.
I know someone has already offered a solution, but there is another way too.
My solution uses a range(i,n) expression to generate a list of index offsets into your array.
This is used in a simple for-each loop along with the take() and skip() operatations that the other solution mentions. The benefit of this approach is that I can avoid setting variables and so allow my loop interations to run concurrently!
Overview:
In the example I just did a compose on an array of Id numbers I got from a SharePoint list
I had something like 640 records and I want to spilt it into chunks of 30.
I used a compose (how-many) with this expression:
length(outputs('get-segment-items')?['value'])
NOTE: Could easliy skip this and just use the expression later.
range(0,
add(
if(
greater(
mod(outputs('how-many'),30),
0
),
1,
0
),
div(
outputs('how-many'),
30
)
)
)
The range() expression nees a start index and a length. The start is easy, zero.
The number of chunks looks overly complex (as in the other posed solution) but is essentially just the div() of the number of items by a hard coded size, in this case 30.
That would allow you to get all the items in full mutiples of 30, but we need to add one more if there is a remainder after doing the integer divide. The other solution converted the number to a string and looked for a decimal point, that works too but here I keep everything in numbers. The if(<test>,1,0) is used to determine if an extract litem is needed in the list. It would be expressed more more simply as:-
If the total items divided by 30 (integer division) has a remainder then add 1
The result of this on my 640 items is 22 iterations (#0 to #21)
Inside the loop you need to reference back to the source array using take and skip
take(
skip(
outputs('get-segment-items')?['value'],
mul(30, item())
),
30
)
The item() value here will be the number 0 to 21 from the range.
So no items will be skipped in the first iteration but by the last (no 21) 630 items will be skipped and the take expression gets the next 30 (or part thereof) items from the source array.
The bonus is that you can set the for-each cocurrency level and get parallel processing of your loop. No variables outisde are needed.
@darren-h-gill-m and @eliotcole Woww, I landed on the right post and helped me a lot. Greatly appreciate your solution.
Thanks,
Ramesh
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 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 SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24 17 @Anil_g 7 @ManishSolanki 13 @eetuRobo 5 @David_MA 10 @VishnuReddy1997 5 @SpongYe 9JhonatanOB19932 (tie) @Nived_Nambiar 8 @maltie 2 (tie) @PA-Noob 2 (tie) @LukeMcG 2 (tie) @tgut03 2 (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. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate @Deenuji 12@ManishSolanki 19 @Anil_g 10 @NathanAlvares24 17 @VishnuReddy1997 6 @Expiscornovus 10 @Tjan 5 @Nived_Nambiar 10 @eetuRobo 3 @SudeepGhatakNZ 8 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 Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22 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 Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2 Anil_g2 SharonS2
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