cancel
Showing results for
Did you mean:
Helper V

## sequential numbers in batches

Hi,

I've got the following data layout,

 Item Assigned 1 Person1 2 Person1 3 Person1 4 Person1 5 6 7 8 9 10 Person3 11 12 13 14 15 16 17 18 Person2 19 Person2 20 Person2 ….1000 records

The goal or idea is allow a person input a number which represents a batch of available sequential numbers.

For instance "person 4" wants a batch of 5 items.

The powerapp should assign "person 4" to the following available slots.

The powerapp must always be able to find available sequential numbers in batches based on the amount input.

 Item Assigned 1 Person1 2 Person1 3 Person1 4 Person1 5 Person4 6 Person4 7 Person4 8 Person4 9 Person4 10 Person3 11 12 13 14 15 16 17 18 Person2 19 Person2 20 Person2 ….1000

Need help to figure out how to achieve this. Anyone know?

1 ACCEPTED SOLUTION

Accepted Solutions
Power Apps

Oh this is a fun problem!

We need each record to be aware of its neighboring records. Thinking in this direction, we'll try to find what records are nearby that would be consecutive below it (min) and above it (max). This gets us a range of Item #s which we can filter later.

For best performance, let's Collect the entire set of Items locally. We can shape the Items very easily in collections with no limits by delegation or delay due to calls to a connected data source.

Execute this action in a button or OnVisible:

``ClearCollect(colItems,Items)``

This means, "Collect all of the Items from the table to a collection called colItems."

Our collection can compare against itself--and at multiple levels. We will need to make each row of colItems compare against the same rows of the table. If you were to try this against the connected datasource, it would not be very performant at all--don't do that.

The diagram below shows an example of 3 levels of colItems comparing against itself:

• Suppose you wanted to find the minimum consecutive record near Item #7. We know that the answer is going to be a range of 5-9 with the minimum as 5. Let's calculate how to get 5 as the minimum.
• First we compare 7 to every other record:
• Which other records are blank?
• Which other records are less than 7?
• Of those, we get [5,6]. If you were to find the absolute value between each of those and 7, which ones are the same distance away as the number of unassigned records that should exist in between them?
• Ex: 7-5=2. Check if there are 2 records that are unassigned between 5 and 7. If so, 5 is consecutive. If there is one assigned in between 5 and 7, 5 is not consecutive.
• Ex: 7-6=1. Check if there is 1 record that is unassigned between 6 and 7. If so, 6 is consecutive. If there is one assigned in between 6 and 7, 6 is not consecutive.

``````Filter(
colItems,
"Min",
// Find the lowest consecutive Item.
If(
IsBlank(Assigned),
Min(
// Return the given Item as the lower boundary if no others are found nearby.
Item,
Min(
// For each Item, look at all blank items before it.
Filter(RenameColumns(Sort(Items,Item),"Item","ItemID_1"),
IsBlank(Assigned),
ItemID_1<Item,

// Determine if a record is consecutive if its distance to the main Item is equal to the amount of records in between.
// A record is not consecutive if another Item had been assigned in between, throwing off the count.
Abs(ItemID_1-Item)=CountRows(Filter(RenameColumns(Sort(Items,Item),"Item","ItemID_2"),IsBlank(Assigned),ItemID_2<Item,ItemID_2>=ItemID_1))
),
ItemID_1
)
)
),
"Max",
// Find the highest consecutive Item.
If(
IsBlank(Assigned),
Max(
Item,
Max(
Filter(RenameColumns(Items,"Item","ItemID_1"),
IsBlank(Assigned),
ItemID_1>Item,
Abs(ItemID_1-Item)=CountRows(Filter(RenameColumns(Sort(Items,Item),"Item","ItemID_2"),IsBlank(Assigned),ItemID_2>Item,ItemID_2<=ItemID_1))
),
ItemID_1
)
)
)
),
Max-Min+1>=Slider1.Value
)``````

1.  Starting inside and going out, colItems is the local collection of Items.
2. I add two columns to it, representing what range of consecutive items it belongs to: Min, Max.
3. I filter the range to only show records that match a given interval controlled by Slider1.

Let's break apart the calculation for Min. Note I did not put many comments into Max since it's a similar pattern, only opposite.

``````If(
IsBlank(Assigned),
Min(
// Return the given Item as the lower boundary if no others are found nearby.
Item,
Min(
// For each Item, look at all blank items before it.
Filter(RenameColumns(Sort(Items,Item),"Item","ItemID_1"),
IsBlank(Assigned),
ItemID_1<Item,

// Determine if a record is consecutive if its distance to the main Item is equal to the amount of records in between.
// A record is not consecutive if another Item had been assigned in between, throwing off the count.
Abs(ItemID_1-Item)=CountRows(Filter(RenameColumns(Sort(Items,Item),"Item","ItemID_2"),IsBlank(Assigned),ItemID_2<Item,ItemID_2>=ItemID_1))
),
ItemID_1
)
)
)``````

• This means, "If the given Item is unassigned (Assigned is blank), calculate a minimum consecutive Item.
• Compare the given Item against the same collection to find records that are less than its Item number and unassigned.
• Compare the difference between the respective item against the count of records that should exist in between. If they match, they are consecutive.
• Of the records that would match, pick the smallest one to represent the start of the consecutive range.
• In the event that a record has no unassigned records preceeding it, make it the start of the range (the outer Min function).

You can see the attached app for an example of this in action.

Let me know if this was helpful.

Mr. Dang

5 REPLIES 5
Power Apps

Oh this is a fun problem!

We need each record to be aware of its neighboring records. Thinking in this direction, we'll try to find what records are nearby that would be consecutive below it (min) and above it (max). This gets us a range of Item #s which we can filter later.

For best performance, let's Collect the entire set of Items locally. We can shape the Items very easily in collections with no limits by delegation or delay due to calls to a connected data source.

Execute this action in a button or OnVisible:

``ClearCollect(colItems,Items)``

This means, "Collect all of the Items from the table to a collection called colItems."

Our collection can compare against itself--and at multiple levels. We will need to make each row of colItems compare against the same rows of the table. If you were to try this against the connected datasource, it would not be very performant at all--don't do that.

The diagram below shows an example of 3 levels of colItems comparing against itself:

• Suppose you wanted to find the minimum consecutive record near Item #7. We know that the answer is going to be a range of 5-9 with the minimum as 5. Let's calculate how to get 5 as the minimum.
• First we compare 7 to every other record:
• Which other records are blank?
• Which other records are less than 7?
• Of those, we get [5,6]. If you were to find the absolute value between each of those and 7, which ones are the same distance away as the number of unassigned records that should exist in between them?
• Ex: 7-5=2. Check if there are 2 records that are unassigned between 5 and 7. If so, 5 is consecutive. If there is one assigned in between 5 and 7, 5 is not consecutive.
• Ex: 7-6=1. Check if there is 1 record that is unassigned between 6 and 7. If so, 6 is consecutive. If there is one assigned in between 6 and 7, 6 is not consecutive.

``````Filter(
colItems,
"Min",
// Find the lowest consecutive Item.
If(
IsBlank(Assigned),
Min(
// Return the given Item as the lower boundary if no others are found nearby.
Item,
Min(
// For each Item, look at all blank items before it.
Filter(RenameColumns(Sort(Items,Item),"Item","ItemID_1"),
IsBlank(Assigned),
ItemID_1<Item,

// Determine if a record is consecutive if its distance to the main Item is equal to the amount of records in between.
// A record is not consecutive if another Item had been assigned in between, throwing off the count.
Abs(ItemID_1-Item)=CountRows(Filter(RenameColumns(Sort(Items,Item),"Item","ItemID_2"),IsBlank(Assigned),ItemID_2<Item,ItemID_2>=ItemID_1))
),
ItemID_1
)
)
),
"Max",
// Find the highest consecutive Item.
If(
IsBlank(Assigned),
Max(
Item,
Max(
Filter(RenameColumns(Items,"Item","ItemID_1"),
IsBlank(Assigned),
ItemID_1>Item,
Abs(ItemID_1-Item)=CountRows(Filter(RenameColumns(Sort(Items,Item),"Item","ItemID_2"),IsBlank(Assigned),ItemID_2>Item,ItemID_2<=ItemID_1))
),
ItemID_1
)
)
)
),
Max-Min+1>=Slider1.Value
)``````

1.  Starting inside and going out, colItems is the local collection of Items.
2. I add two columns to it, representing what range of consecutive items it belongs to: Min, Max.
3. I filter the range to only show records that match a given interval controlled by Slider1.

Let's break apart the calculation for Min. Note I did not put many comments into Max since it's a similar pattern, only opposite.

``````If(
IsBlank(Assigned),
Min(
// Return the given Item as the lower boundary if no others are found nearby.
Item,
Min(
// For each Item, look at all blank items before it.
Filter(RenameColumns(Sort(Items,Item),"Item","ItemID_1"),
IsBlank(Assigned),
ItemID_1<Item,

// Determine if a record is consecutive if its distance to the main Item is equal to the amount of records in between.
// A record is not consecutive if another Item had been assigned in between, throwing off the count.
Abs(ItemID_1-Item)=CountRows(Filter(RenameColumns(Sort(Items,Item),"Item","ItemID_2"),IsBlank(Assigned),ItemID_2<Item,ItemID_2>=ItemID_1))
),
ItemID_1
)
)
)``````

• This means, "If the given Item is unassigned (Assigned is blank), calculate a minimum consecutive Item.
• Compare the given Item against the same collection to find records that are less than its Item number and unassigned.
• Compare the difference between the respective item against the count of records that should exist in between. If they match, they are consecutive.
• Of the records that would match, pick the smallest one to represent the start of the consecutive range.
• In the event that a record has no unassigned records preceeding it, make it the start of the range (the outer Min function).

You can see the attached app for an example of this in action.

Let me know if this was helpful.

Mr. Dang

Helper V

Hi Mr Dang,

Downloaded the sample app and its a massive help. Going over code as much as I can. Thank you, for the explanations.

I've applied the code to the "onchange" property of the slicer in order to take the results into another collection. My next step is linking a gallery to the new collection for multi selection editing which will then be written back to the source.

This was very helpful and the desired result looks achievable, will let you know. Thank you!

Big Fan! From South Africa.

Power Apps

I'm happy this was helpful. It is incomplete though as you'll probably need to use GroupBy to stick together each set of Items. Good luck with the rest of it and feel free to share your add-ons so others can learn from you. 🤓

Helper V

Like bait to a fish "It is incomplete though as you'll probably need to use GroupBy to stick together each set of Items".

If assuming correctly, we'll create a index number for each batch/group on a new column? Yeah that'll be great.

What did you have in mind?

Power Apps

In its current form, the app reduces the Items to only the unassigned items. But each Item is still an individual record. If you click 7, you will only have 7 selected. But what you actually want is to select 5-9 with one click.

The GroupBy function takes one column of that table and effectively looks for unique values. In the image above, 5 and 11 are the two unique values for Min. Then for each unique value, it creates a child table of the rows that match.

If I were to use the formula below:

``GroupBy(the_entire_formula_shared_earlier, "Min", "ItemSet")``

This creates a table with two rows under the Min column: 5, 11.

Beside the row for 5 is a table whose name is ItemSet and contains items 5-9 since they match the value of 5 in the Min column.

Beside the row for 11 is a table of items 11-17.

The child table would contain columns for Item, Assigned, and Max.

Now that the items are grouped, you can take action on a selected group.

Announcements

#### Copilot Cookbook Challenge | WINNERS ANNOUNCED | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge random winners have been selected for the Challenge.  Thank you to everyone who participated in this challenge.    Copilot Cookbook Gallery:Power Apps Cookbook Gallery: 1. @swaminawale  1. @renatoromao     2.  @SpongYe  2.   @nickpotts10  *Please note if for any reason a winner declines, we will have another random drawing.   Check out all of the Cookbook Submissions: 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 30WINNERS ANNOUNCED - JULY 8th     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. Early Bird Submissions: @renato 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   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.   Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. @nickpotts10  1. @ShrushtiShah  2. @Suniti_0020 2. @swaminawale 3. n/a3. @farukhis786 4. n/a4. @ManishSolanki  5. n/a5.  n/a