Hi Noel,

Very interesting challenge, do you care which library each set ends up in, or just that they are roughly evenly distributed?

Callum

Hi Noel,

I shared this one with the team to get some ideas, I think this is the most elegant way we could achieve this. Obviously not sure of other aspects of the document storage and what you are doing but from a workflow perspective I think this will work.

The trick will be to do two things:

• Establish a prefix for your destination document buckets (e.g. Bucket 1, Bucket 2) for the title
• Use the web request action to determine which bucket to move them to.

For the web request, you should be able to do effectively the following:

https://me.sharepoint.com/sites/mysite/_api/lists?$orderby=itemCount&$filter=startswith(title,'Bucket')&$select=title,itemCount&$top=1

This will select the lists that start with 'Bucket', order them by item count so that the bucket with the fewest items is on top, then pick the top one and return you the title & count.

One nice thing about this solution is if you need to add more buckets, just add more and they will automatically start being filled before the others as they will have fewer items.

The restriction with this solution would be that since the copy document action cannot accept a variable as a destination library, you would need to use the more flexible Office 365 Download File action to move it. If I can think of a better idea I will let you know.

Thanks

Callum

Hi Callum,

Thanks for the time spent looking into this. I'll incorporate the above and let you know how I get on. This certainly looks like a valid approach.