cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
ericonline
Community Champion
Community Champion

Pulling in large-ish SQL tables

Hello,

Is this how everyone is pulling in large-ish SQL data sets (~35k records)? Or do you use another method?

  1. Set Advanced Settings max to `2000`
  2.  
Concurrent(
    ClearCollect(col1, Filter('[dbo].[bigSqltable]', recordID >= 1 && recordID <= 2000)),
    ClearCollect(col2, Filter('[dbo].[bigSqltable]', recordID >= 2001 && recordID <= 4000)),
    ClearCollect(col3, Filter('[dbo].[bigSqltable]', recordID >= 4001 && recordID <= 6000)),
    ClearCollect(col4, Filter('[dbo].[bigSqltable]', recordID >= 6001 && recordID <= 8000)),
    ClearCollect(col5, Filter('[dbo].[bigSqltable]', recordID >= 8001 && recordID <= 10000)),
    ClearCollect(col6, Filter('[dbo].[bigSqltable]', recordID >= 10001 && recordID <= 12000)),
    ClearCollect(col7, Filter('[dbo].[bigSqltable]', recordID >= 12001 && recordID <= 14000)),
    ClearCollect(col8, Filter('[dbo].[bigSqltable]', recordID >= 14001 && recordID <= 16000)),
    ClearCollect(col9, Filter('[dbo].[bigSqltable]', recordID >= 16001 && recordID <= 18000)),
    ClearCollect(col10, Filter('[dbo].[bigSqltable]', recordID >= 18001 && recordID <= 20000)),
    ClearCollect(col11, Filter('[dbo].[bigSqltable]', recordID >= 20001 && recordID <= 22000)),
    ClearCollect(col12, Filter('[dbo].[bigSqltable]', recordID >= 22001 && recordID <= 24000)),
    ClearCollect(col13, Filter('[dbo].[bigSqltable]', recordID >= 24001 && recordID <= 26000)),
    ClearCollect(col14, Filter('[dbo].[bigSqltable]', recordID >= 26001 && recordID <= 28000)),
    ClearCollect(col15, Filter('[dbo].[bigSqltable]', recordID >= 28001 && recordID <= 30000)),
    ClearCollect(col16, Filter('[dbo].[bigSqltable]', recordID >= 30001 && recordID <= 32000)),
    ClearCollect(col17, Filter('[dbo].[bigSqltable]', recordID >= 32001 && recordID <= 34000)),
    ClearCollect(col18, Filter('[dbo].[bigSqltable]', recordID >= 34001 && recordID <= 35000))
);
ClearCollect(colCombined, 
    col1, col2, col3, col4, col5, col6, col7, col8, col9, col10, col11, col12, col13, col14, col15, col16, col17, col18
)
39 REPLIES 39

@ericonline  Don't know about everyone else, but plus 1 here.  Have used that method for SharePoint lists that are large - with the exception that I'm typically using a text field and startswith to get the same results (as the < and > are not delegable on SharePoint)

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

Awesome. Thanks for sharing! Curious what others are doing as well. 

@ericonline  I really see no other alternative if you need to pull the whole list/table.  I do try to avoid that as much as possible, but there are times...

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!
timl
Super User
Super User

Hi @ericonline 

Out of interest, why do you need to pull in such a large table? Is it because you want to run some non-delegable query against the data, or perhaps you want to work offline with this data?

The reason I ask is because if there's a specific requirement you have, maybe someone can suggest a solution that doesn't require you to pull in 35k rows.

Right on @timl. Yeah, I'd like to take advantage of the recent "SaveData/LoadData Unleashed" announcement for local caching.
Idea:

  • Pull down all 35k records in an intial "Sync" action (using Azure SQL, this is ~6 seconds!)
  • SaveData to device
  • LoadData on subsequent app starts
  • Have lightning fast Lookups, Filters and Searches using Collections
  • Once a week or so, have user "Sync" again to pull latest data down
  • Rinse, Repeat.

My first attempt at this goal, so putting feelers out!

@timl  I can't speak for @ericonline needs, but I can explain our most recent.

We had a SharePoint list of contacts that was around 5000 contacts.  The customer wanted an app to be able to pull up any contact through name or company name.  We needed to search at least 2 fields for the information they wanted. It was a simple request, but took some doing on the PowerApps side.  The only solution was to pull down all of the items in a series of Filters using StartsWith and every letter of the alphabet on each column.  Then combine them all together and use that to do all the rest of the requirements in the app.  

The bigger trick was that since we were collecting twice, once for name and once for company, we would get duplicates in the collection, so the final step was to Filter them out on the final collect.

We made use of the Concurrent function to reduce the amount of time for loading.  Also, we had a separate collection (alpha) that had all the letters of the Alphabet in and a status field for if the names were loaded and the companies were loaded for that letter.  This would be updated after each complete of a "grab" from the SharePoint. And, this was used then on a Gallery of all the Alphabet letters to change their appearance as they were loaded. (Kind of gave the user a sense that things were happening as they were).

 

Anybody interested???  Here is the formula:

 

//Build the alpha collection for status and feedback to user.
ClearCollect(alpha, {disp:"A",nameLoad:false, compLoad:false}, {disp:"B",nameLoad:false, compLoad:false}, {disp:"C",nameLoad:false, compLoad:false}, {disp:"D",nameLoad:false, compLoad:false}, {disp:"E",nameLoad:false, compLoad:false}, {disp:"F",nameLoad:false, compLoad:false}, {disp:"G",nameLoad:false, compLoad:false}, {disp:"H",nameLoad:false, compLoad:false}, {disp:"I",nameLoad:false, compLoad:false}, {disp:"J",nameLoad:false, compLoad:false}, {disp:"K",nameLoad:false, compLoad:false}, {disp:"L",nameLoad:false, compLoad:false}, {disp:"M",nameLoad:false, compLoad:false}, {disp:"N",nameLoad:false, compLoad:false}, {disp:"O",nameLoad:false, compLoad:false}, {disp:"P",nameLoad:false, compLoad:false}, {disp:"Q",nameLoad:false, compLoad:false}, {disp:"R",nameLoad:false, compLoad:false}, {disp:"S",nameLoad:false, compLoad:false}, {disp:"T",nameLoad:false, compLoad:false}, {disp:"U",nameLoad:false, compLoad:false}, {disp:"V",nameLoad:false, compLoad:false}, {disp:"W",nameLoad:false, compLoad:false}, {disp:"X",nameLoad:false, compLoad:false}, {disp:"Y",nameLoad:false, compLoad:false}, {disp:"Z",nameLoad:false, compLoad:false}); UpdateContext({loadMsg:"Loading Names"});
//Concurrently filter all letters of the alphabet on the Title column, update status as you go.
Concurrent( ClearCollect(local_A, SortByColumns(Filter(Contacts, StartsWith(Title, "A")), "Title")); Patch(alpha, LookUp(alpha, disp="A"), {nameLoad:true}), ClearCollect(local_B, SortByColumns(Filter(Contacts, StartsWith(Title, "B")), "Title")); Patch(alpha, LookUp(alpha, disp="B"), {nameLoad:true}), ClearCollect(local_C, SortByColumns(Filter(Contacts, StartsWith(Title, "C")), "Title")); Patch(alpha, LookUp(alpha, disp="C"), {nameLoad:true}), ClearCollect(local_D, SortByColumns(Filter(Contacts, StartsWith(Title, "D")), "Title")); Patch(alpha, LookUp(alpha, disp="D"), {nameLoad:true}), ClearCollect(local_E, SortByColumns(Filter(Contacts, StartsWith(Title, "E")), "Title")); Patch(alpha, LookUp(alpha, disp="E"), {nameLoad:true}), ClearCollect(local_F, SortByColumns(Filter(Contacts, StartsWith(Title, "F")), "Title")); Patch(alpha, LookUp(alpha, disp="F"), {nameLoad:true}), ClearCollect(local_G, SortByColumns(Filter(Contacts, StartsWith(Title, "G")), "Title")); Patch(alpha, LookUp(alpha, disp="G"), {nameLoad:true}), ClearCollect(local_H, SortByColumns(Filter(Contacts, StartsWith(Title, "H")), "Title")); Patch(alpha, LookUp(alpha, disp="H"), {nameLoad:true}), ClearCollect(local_I, SortByColumns(Filter(Contacts, StartsWith(Title, "I")), "Title")); Patch(alpha, LookUp(alpha, disp="I"), {nameLoad:true}), ClearCollect(local_J, SortByColumns(Filter(Contacts, StartsWith(Title, "J")), "Title")); Patch(alpha, LookUp(alpha, disp="J"), {nameLoad:true}), ClearCollect(local_K, SortByColumns(Filter(Contacts, StartsWith(Title, "K")), "Title")); Patch(alpha, LookUp(alpha, disp="K"), {nameLoad:true}), ClearCollect(local_L, SortByColumns(Filter(Contacts, StartsWith(Title, "L")), "Title")); Patch(alpha, LookUp(alpha, disp="L"), {nameLoad:true}), ClearCollect(local_M, SortByColumns(Filter(Contacts, StartsWith(Title, "M")), "Title")); Patch(alpha, LookUp(alpha, disp="M"), {nameLoad:true}), ClearCollect(local_N, SortByColumns(Filter(Contacts, StartsWith(Title, "N")), "Title")); Patch(alpha, LookUp(alpha, disp="N"), {nameLoad:true}), ClearCollect(local_O, SortByColumns(Filter(Contacts, StartsWith(Title, "O")), "Title")); Patch(alpha, LookUp(alpha, disp="O"), {nameLoad:true}), ClearCollect(local_P, SortByColumns(Filter(Contacts, StartsWith(Title, "P")), "Title")); Patch(alpha, LookUp(alpha, disp="P"), {nameLoad:true}), ClearCollect(local_Q, SortByColumns(Filter(Contacts, StartsWith(Title, "Q")), "Title")); Patch(alpha, LookUp(alpha, disp="Q"), {nameLoad:true}), ClearCollect(local_R, SortByColumns(Filter(Contacts, StartsWith(Title, "R")), "Title")); Patch(alpha, LookUp(alpha, disp="R"), {nameLoad:true}), ClearCollect(local_S, SortByColumns(Filter(Contacts, StartsWith(Title, "S")), "Title")); Patch(alpha, LookUp(alpha, disp="S"), {nameLoad:true}), ClearCollect(local_T, SortByColumns(Filter(Contacts, StartsWith(Title, "T")), "Title")); Patch(alpha, LookUp(alpha, disp="T"), {nameLoad:true}), ClearCollect(local_U, SortByColumns(Filter(Contacts, StartsWith(Title, "U")), "Title")); Patch(alpha, LookUp(alpha, disp="U"), {nameLoad:true}), ClearCollect(local_V, SortByColumns(Filter(Contacts, StartsWith(Title, "V")), "Title")); Patch(alpha, LookUp(alpha, disp="V"), {nameLoad:true}), ClearCollect(local_W, SortByColumns(Filter(Contacts, StartsWith(Title, "W")), "Title")); Patch(alpha, LookUp(alpha, disp="W"), {nameLoad:true}), ClearCollect(local_X, SortByColumns(Filter(Contacts, StartsWith(Title, "X")), "Title")); Patch(alpha, LookUp(alpha, disp="X"), {nameLoad:true}), ClearCollect(local_Y, SortByColumns(Filter(Contacts, StartsWith(Title, "Y")), "Title")); Patch(alpha, LookUp(alpha, disp="Y"), {nameLoad:true}), ClearCollect(local_Z, SortByColumns(Filter(Contacts, StartsWith(Title, "Z")), "Title")); Patch(alpha, LookUp(alpha, disp="Z"), {nameLoad:true}) ); UpdateContext({loadMsg:"Consolidating Names"});
//Combine the results of all collections into one.
ClearCollect(local, local_A, local_B, local_C, local_D, local_E, local_F, local_G, local_H, local_I, local_J, local_K, local_L, local_M, local_N, local_O, local_P, local_Q, local_R, local_S, local_T, local_U, local_V, local_W, local_X, local_Y, local_Z); UpdateContext({loadMsg:"Loading Companies"}); //Concurrently filter all the letters of the alphabet on Company column, update status as you go.
Concurrent( ClearCollect(local_A, SortByColumns(Filter(Contacts, StartsWith(Company, "A")), "Title")); Patch(alpha, LookUp(alpha, disp="A"), {compLoad:true}), ClearCollect(local_B, SortByColumns(Filter(Contacts, StartsWith(Company, "B")), "Title")); Patch(alpha, LookUp(alpha, disp="B"), {compLoad:true}), ClearCollect(local_C, SortByColumns(Filter(Contacts, StartsWith(Company, "C")), "Title")); Patch(alpha, LookUp(alpha, disp="C"), {compLoad:true}), ClearCollect(local_D, SortByColumns(Filter(Contacts, StartsWith(Company, "D")), "Title")); Patch(alpha, LookUp(alpha, disp="D"), {compLoad:true}), ClearCollect(local_E, SortByColumns(Filter(Contacts, StartsWith(Company, "E")), "Title")); Patch(alpha, LookUp(alpha, disp="E"), {compLoad:true}), ClearCollect(local_F, SortByColumns(Filter(Contacts, StartsWith(Company, "F")), "Title")); Patch(alpha, LookUp(alpha, disp="F"), {compLoad:true}), ClearCollect(local_G, SortByColumns(Filter(Contacts, StartsWith(Company, "G")), "Title")); Patch(alpha, LookUp(alpha, disp="G"), {compLoad:true}), ClearCollect(local_H, SortByColumns(Filter(Contacts, StartsWith(Company, "H")), "Title")); Patch(alpha, LookUp(alpha, disp="H"), {compLoad:true}), ClearCollect(local_I, SortByColumns(Filter(Contacts, StartsWith(Company, "I")), "Title")); Patch(alpha, LookUp(alpha, disp="I"), {compLoad:true}), ClearCollect(local_J, SortByColumns(Filter(Contacts, StartsWith(Company, "J")), "Title")); Patch(alpha, LookUp(alpha, disp="J"), {compLoad:true}), ClearCollect(local_K, SortByColumns(Filter(Contacts, StartsWith(Company, "K")), "Title")); Patch(alpha, LookUp(alpha, disp="K"), {compLoad:true}), ClearCollect(local_L, SortByColumns(Filter(Contacts, StartsWith(Company, "L")), "Title")); Patch(alpha, LookUp(alpha, disp="L"), {compLoad:true}), ClearCollect(local_M, SortByColumns(Filter(Contacts, StartsWith(Company, "M")), "Title")); Patch(alpha, LookUp(alpha, disp="M"), {compLoad:true}), ClearCollect(local_N, SortByColumns(Filter(Contacts, StartsWith(Company, "N")), "Title")); Patch(alpha, LookUp(alpha, disp="N"), {compLoad:true}), ClearCollect(local_O, SortByColumns(Filter(Contacts, StartsWith(Company, "O")), "Title")); Patch(alpha, LookUp(alpha, disp="O"), {compLoad:true}), ClearCollect(local_P, SortByColumns(Filter(Contacts, StartsWith(Company, "P")), "Title")); Patch(alpha, LookUp(alpha, disp="P"), {compLoad:true}), ClearCollect(local_Q, SortByColumns(Filter(Contacts, StartsWith(Company, "Q")), "Title")); Patch(alpha, LookUp(alpha, disp="Q"), {compLoad:true}), ClearCollect(local_R, SortByColumns(Filter(Contacts, StartsWith(Company, "R")), "Title")); Patch(alpha, LookUp(alpha, disp="R"), {compLoad:true}), ClearCollect(local_S, SortByColumns(Filter(Contacts, StartsWith(Company, "S")), "Title")); Patch(alpha, LookUp(alpha, disp="S"), {compLoad:true}), ClearCollect(local_T, SortByColumns(Filter(Contacts, StartsWith(Company, "T")), "Title")); Patch(alpha, LookUp(alpha, disp="T"), {compLoad:true}), ClearCollect(local_U, SortByColumns(Filter(Contacts, StartsWith(Company, "U")), "Title")); Patch(alpha, LookUp(alpha, disp="U"), {compLoad:true}), ClearCollect(local_V, SortByColumns(Filter(Contacts, StartsWith(Company, "V")), "Title")); Patch(alpha, LookUp(alpha, disp="V"), {compLoad:true}), ClearCollect(local_W, SortByColumns(Filter(Contacts, StartsWith(Company, "W")), "Title")); Patch(alpha, LookUp(alpha, disp="W"), {compLoad:true}), ClearCollect(local_X, SortByColumns(Filter(Contacts, StartsWith(Company, "X")), "Title")); Patch(alpha, LookUp(alpha, disp="X"), {compLoad:true}), ClearCollect(local_Y, SortByColumns(Filter(Contacts, StartsWith(Company, "Y")), "Title")); Patch(alpha, LookUp(alpha, disp="Y"), {compLoad:true}), ClearCollect(local_Z, SortByColumns(Filter(Contacts, StartsWith(Company, "Z")), "Title")); Patch(alpha, LookUp(alpha, disp="Z"), {compLoad:true}) ); UpdateContext({distinctIDs: Distinct(local, ID)}); //Pull out any duplicate records by ID (which is unique) UpdateContext({loadMsg:"Consolidating Companies A"}); Collect(local, Filter(local_A, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies B"}); Collect(local, Filter(local_B, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies C"}); Collect(local, Filter(local_C, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies D"}); Collect(local, Filter(local_D, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies E"}); Collect(local, Filter(local_E, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies F"}); Collect(local, Filter(local_F, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies G"}); Collect(local, Filter(local_G, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies H"}); Collect(local, Filter(local_H, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies I"}); Collect(local, Filter(local_I, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies J"}); Collect(local, Filter(local_J, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies K"}); Collect(local, Filter(local_K, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies L"}); Collect(local, Filter(local_L, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies M"}); Collect(local, Filter(local_M, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies N"}); Collect(local, Filter(local_N, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies O"}); Collect(local, Filter(local_O, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies P"}); Collect(local, Filter(local_P, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies Q"}); Collect(local, Filter(local_Q, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies R"}); Collect(local, Filter(local_R, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies S"}); Collect(local, Filter(local_S, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies T"}); Collect(local, Filter(local_T, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies U"}); Collect(local, Filter(local_U, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies V"}); Collect(local, Filter(local_V, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies W"}); Collect(local, Filter(local_W, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies X"}); Collect(local, Filter(local_X, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies Y"}); Collect(local, Filter(local_Y, !(ID in distinctIDs))); UpdateContext({loadMsg:"Consolidating Companies Z"}); Collect(local, Filter(local_Z, !(ID in distinctIDs))); //Just because it seems cleaning up is nice to do... Clear(local_A); Clear(local_B); Clear(local_C); Clear(local_D); Clear(local_E); Clear(local_F); Clear(local_G); Clear(local_H); Clear(local_I); Clear(local_J); Clear(local_K); Clear(local_L); Clear(local_M); Clear(local_N); Clear(local_O); Clear(local_P); Clear(local_Q); Clear(local_R); Clear(local_S); Clear(local_T); Clear(local_U); Clear(local_V); Clear(local_W); Clear(local_X); Clear(local_Y); Clear(local_Z); UpdateContext({loadMsg:""}); UpdateContext({loadData:false, _initedContacts:true})

 

Oh how I longed for a good old For...Next!!

All of this on a Toggle so that we could call a Refresh easily if needed.

 

Enjoy!!

 

(Yikes!  Sorry for the big Formula dump)

 

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

Very clever @ericonline! I'm impressed with the very fast load time from Azure SQL. I'm sure it'll be an amazing app once you get it working.

Like @RandyHayes, I don't think there's any other practical way to do this. You probably know this but if there are columns in [bigSqltable] that you don't need, you could use a SQL View to exclude these and to avoid pulling in any additional data that you don't need.

Good luck!

@RandyHayes ,
How about:

OnStart of App:

Concurrent(
ClearCollect(col1, Filter(sharepointList, recordID >= 1 && recordID <= 2000)),
ClearCollect(col2, Filter(sharepointList, recordID >= 2001 && recordID <= 4000)),
ClearCollect(col3, Filter(sharepointList, recordID >= 4001 && recordID <= 6000))
);
ClearCollect(colCombined,col1,col2,col3)

Set Gallery Control Items Property to:

Filter(
    colCombined,
    searchBar.Text in firstName ||
    searchBar.Text in lastName ||
    searchBar.Text in companyName ||
    searchBar.Text in anyDarnColumnYouWantName
)

Prosper!!

Good point @timl. I had not thought about dropping columns like that to optimize even further. Thank you senor!

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

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!

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

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.    

Summer of Solutions | Week 3 Results | Win free tickets to the Power Platform Conference

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  

Updates to Transitions in the Power Platform Communities

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

Top Solution Authors
Top Kudoed Authors
Users online (4,111)