cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
seadude
Memorable Member
Memorable Member

Complex Collection of a Collection

Hello!

Looking for some insights on this one... not sure how its done and tried a few things that didn't work.
Scenario: I have a table with the schema below. I want to Collect a new collection of ONLY the first two items under the "coordinates" subtable.

 

{
    "type": "FeatureCollection",
    "metadata": {
        "generated": 1555194002000,
        "url": "https://earthquake.usgs.gov/fdsnws/event/1/query?format=geojson&starttime=2014-01-01&endtime=2014-01-02&latitude=47&longitude=-122&maxradiuskm=300&orderby=magnitude-asc",
        "title": "USGS Earthquakes",
        "status": 200,
        "api": "1.8.1",
        "count": 9
    },
    "features": [
        {
            "type": "Feature",
            "properties": {
                "mag": -0.33,
                "place": "27km NNW of Packwood, Washington",
                "time": 1388615267370,
                "updated": 1469215317030,
                "tz": -480,
                "url": "https://earthquake.usgs.gov/earthquakes/eventpage/uw60664496",
                "detail": "https://earthquake.usgs.gov/fdsnws/event/1/query?eventid=uw60664496&format=geojson",
                "felt": null,
                "cdi": null,
                "mmi": null,
                "alert": null,
                "status": "reviewed",
                "tsunami": 0,
                "sig": 2,
                "net": "uw",
                "code": "60664496",
                "ids": ",uw60664496,",
                "sources": ",uw,",
                "types": ",general-link,geoserve,nearby-cities,origin,phase-data,",
                "nst": 9,
                "dmin": 0.01894,
                "rms": 0.08,
                "gap": 71,
                "magType": "md",
                "type": "earthquake",
                "title": "M -0.3 - 27km NNW of Packwood, Washington"
            },
            "geometry": {
                "type": "Point",
                "coordinates": [
                    -121.7506667,
                    46.8501667,
                    1.436
                ]
            },
            "id": "uw60664496"
        },
        {
            "type": "Feature",
            "properties": {
                "mag": 0.19,
                "place": "22km S of Sequim, Washington",
                "time": 1388595112000,
                "updated": 1469215316190,
                "tz": -480,
                "url": "https://earthquake.usgs.gov/earthquakes/eventpage/uw60664386",
                "detail": "https://earthquake.usgs.gov/fdsnws/event/1/query?eventid=uw60664386&format=geojson",
                "felt": null,
                "cdi": null,
                "mmi": null,
                "alert": null,
                "status": "reviewed",
                "tsunami": 0,
                "sig": 1,
                "net": "uw",
                "code": "60664386",
                "ids": ",uw60664386,",
                "sources": ",uw,",
                "types": ",cap,general-link,geoserve,nearby-cities,origin,phase-data,",
                "nst": 3,
                "dmin": 0.1492,
                "rms": 0.22,
                "gap": 306,
                "magType": "md",
                "type": "earthquake",
                "title": "M 0.2 - 22km S of Sequim, Washington"
            },
            "geometry": {
                "type": "Point",
                "coordinates": [
                    -123.108,
                    47.881,
                    4.572
                ]
            },
            "id": "uw60664386"
        },
        {
            "type": "Feature",
            "properties": {
                "mag": 0.22,
                "place": "21km NNW of Amboy, Washington",
                "time": 1388536764680,
                "updated": 1469215315430,
                "tz": -480,
                "url": "https://earthquake.usgs.gov/earthquakes/eventpage/uw60664276",
                "detail": "https://earthquake.usgs.gov/fdsnws/event/1/query?eventid=uw60664276&format=geojson",
                "felt": null,
                "cdi": null,
                "mmi": null,
                "alert": null,
                "status": "reviewed",
                "tsunami": 0,
                "sig": 1,
                "net": "uw",
                "code": "60664276",
                "ids": ",uw60664276,",
                "sources": ",uw,",
                "types": ",cap,general-link,geoserve,nearby-cities,origin,phase-data,",
                "nst": 9,
                "dmin": 0.08565,
                "rms": 0.1,
                "gap": 182,
                "magType": "md",
                "type": "earthquake",
                "title": "M 0.2 - 21km NNW of Amboy, Washington"
            },
            "geometry": {
                "type": "Point",
                "coordinates": [
                    -122.5188333,
                    46.0926667,
                    13.97
                ]
            },
            "id": "uw60664276"
        },
        {
            "type": "Feature",
            "properties": {
                "mag": 0.43,
                "place": "19km E of Kelso, Washington",
                "time": 1388577684900,
                "updated": 1469215315950,
                "tz": -480,
                "url": "https://earthquake.usgs.gov/earthquakes/eventpage/uw60664346",
                "detail": "https://earthquake.usgs.gov/fdsnws/event/1/query?eventid=uw60664346&format=geojson",
                "felt": null,
                "cdi": null,
                "mmi": null,
                "alert": null,
                "status": "reviewed",
                "tsunami": 0,
                "sig": 3,
                "net": "uw",
                "code": "60664346",
                "ids": ",uw60664346,",
                "sources": ",uw,",
                "types": ",cap,general-link,geoserve,nearby-cities,origin,phase-data,",
                "nst": 13,
                "dmin": 0.06314,
                "rms": 0.15,
                "gap": 143,
                "magType": "md",
                "type": "earthquake",
                "title": "M 0.4 - 19km E of Kelso, Washington"
            },
            "geometry": {
                "type": "Point",
                "coordinates": [
                    -122.6526667,
                    46.1491667,
                    15.17
                ]
            },
            "id": "uw60664346"
        }
}

JUST THE FIRST TWO ITEMS in the "Coordinates" subtable. I want a Collection that looks like:

 

{id: 1, long: -122.6526667, lat: 46.1491667}
{id: 2, long: -122.5188333, lat: 46.0926667}
{id: 3, long: -123.108, lat: 47.881}

Tried so far:

ClearCollect(
    colSecondCollection,
    First(colFirstCollection.features).features.geometry).geometry
); 
// Results in a table of nested tables. I need the coordinates alone
// Also tried:

ForAll(
    colFirstCollection,
    ClearCollect(
        colSecondCollection,
        First(First(colFirstCollection.features).features.geometry).geometry.coordinates).coordinates
    )
);

// Error:  "this action is not allowed within a ForAll"

Anyone have some idears?

Thank yoU!

 

11 REPLIES 11

@seadude 

You can get part of the way there with this formula:

ClearCollect(finalResults, 
   ForAll(Ungroup(colFirstCollection.features, "features"), 
     {id:Value.id, long:First(Value.geometry.coordinates.Value).Value, lat:Last(FirstN(Value.geometry.coordinates.Value,2)).Value}
  )
)

This will return the record table like you wanted - with one exception...the sequential ID numbering.  In the above formula, you will get the id that is in the original JSON payload not a sequence.

Trying to do sequential numbering in PowerApps is oddly challenging.

 

I hope this puts you on the right track.

_____________________________________________________________________________________
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!
RezaDorrani
Community Champion
Community Champion

@seadude 

Clear(colSecondCollection);ForAll(colFirstCollection.features,Collect(colSecondCollection,features.Value));Clear(colThirdCollection);ForAll(colSecondCollection,Collect(colThirdCollection,Value.geometry))

 

This will give you the main collection colThirdCollection which will contain all the coordinates

image.png

 

Now, if you only need the first 2 coordinates then use 

First(colThirdCollection).coordinates.Value - First coordinates

Last(FirstN(colThirdCollection,2)).coordinates.Value - Second coordinates

 

And to fetch individual values for the coordinates

Example : coordinates: [
-121.7506667,
46.8501667,
1.436
]

 

First(First(colThirdCollection).coordinates.Value).Value    =  -121.7506667

Last(FirstN(First(colThirdCollection).coordinates.Value,2)).Value   =  46.8501667

Last(FirstN(First(colThirdCollection).coordinates.Value,3)).Value = 1.436

 

Hope this helps

Hi @RandyHayes and @RezaDorrani ,

Thank you both for the thoughtful replies. This was the easiest for me to implement:

 

ForAll(
    Ungroup(colEarthquakeResults.features, "features"),
        Collect(colEarthquakeLatLongs,
            {long: First(geometry.coordinates.Value).Value, lat: Last(FirstN(geometry.coordinates.Value,2)).Value}
        )
)

It results in:

image.png

@RandyHayes, you were right! It is not easy to implement an incremental ID column in this case! Here's what I tried so far:

ClearCollect(colEarthquakeLatLongs,
    AddColumns(
        ForAll(
            Ungroup(colEarthquakeResults.features, "features"),
            {long:First(geometry.coordinates.Value).Value, lat:Last(FirstN(geometry.coordinates.Value,2)).Value}
        ),
        "id",
        If(
            1 = 1,
CountRows(colEarthquakeLatLongs) + 1 ) ) );
ClearCollect(colEarthquakeLatLongs,
        ForAll(
            Ungroup(colEarthquakeResults.features, "features"),
            {id: Text(CountRows(colEarthquakeLatLongs)) + 1, long: First(geometry.coordinates.Value).Value, lat:Last(FirstN(geometry.coordinates.Value,2)).Value}
        )
    )
ForAll(
    Ungroup(colEarthquakeResults.features, "features"),
        Collect(colEarthquakeLatLongs,
            {id: Value(CountRows(Ungroup(colEarthquakeResults.features, "features"))) + 1, long: First(geometry.coordinates.Value).Value, lat: Last(FirstN(geometry.coordinates.Value,2)).Value}
        )
)
ClearCollect(colEarthquakeLatLongs,
    AddColumns(
        ForAll(
            Ungroup(colEarthquakeResults.features, "features"),
            {long:First(geometry.coordinates.Value).Value, lat:Last(FirstN(geometry.coordinates.Value,2)).Value}
        ),
        "id",
        If(
            !IsEmpty(First(First(First(colEarthquakeResults.features).features.geometry).geometry.coordinates)),
            Text(Value(varCounter) + 1)
        )
    )
)

 

I bet @mr-dang knows how to do this! 🙂

 

@seadude 

Well, here's the loaded question...do you have any idea on how many records you anticipate?

If you have knowledge that there is a preset amount or at least an amount of rows that will never exceed a certain number, then you can alter the formula like this:

ClearCollect(colEarthquakeLatLongs,
             ForAll([1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30],
                    If(Value<=CountRows(Ungroup(colEarthquakeResults, "features")),
                        {id:Value, 
                         long:First(Last(FirstN(Ungroup(colEarthquakeResults, "features"), Value)).Value.geometry.coordinates).Value, 
                         lat:Last(FirstN(Last(FirstN(Ungroup(colEarthquakeResults, "features"), Value)).Value.geometry.coordinates,2)).Value
                        } 
                      )
                   )
            )

Of course, in this case, that gives you only a max of 30 sequential ID's...but you could change that if needed.

 

See if that fits better for you.

 

_____________________________________________________________________________________
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!

Hi @RandyHayes ,

There is no way of knowing exactly how many results will be returned.

  • In this blog post, I found a fun way to create a large Numbers Table.
  • Without a way to programatically create a Value Table based on CountRows or the like, we'll always run into this issue. Bummer!

Ended up going with this MONSTER!:

 

Set(varNumTable, [1, 2, 3, 4, 5, 6, 7, 8, 9, 10]);

Clear(colNumbersTable);

Clear(colRecordToCount);

ClearCollect(colNumTemp, varNumTable);

ForAll(colNumTemp,
    ForAll(colNumTemp,
        ForAll(colNumTemp,
            Collect(colRecordToCount,
                {
                    record: 1
                }
            );
            Collect(colNumbersTable,
                {
                    number: CountRows(colRecordToCount)
                }
            )
        )

    )
);

ClearCollect(
    colEarthquakeResults,
    earthquakeAPI.GETearthquakes(
        {
            format: "geojson",
            starttime: Today() - 1,
            endtime: Today(),
            latitude: Location.Latitude,
            longitude: Location.Longitude,
            maxradiuskm: 1000,
            orderby: "magnitude-asc"
        }
    )
);

ClearCollect(colEarthquakeLatLongs,
    ForAll(colNumbersTable,
        If(number <= CountRows(Ungroup(colEarthquakeResults.features, "features")),
            {
                id: number, 
                long: First(
Last(
FirstN(
Ungroup(colEarthquakeResults.features, "features"),
number
)
).geometry.coordinates
).Value, lat: Last(
FirstN(
Last(
FirstN(
Ungroup(colEarthquakeResults.features, "features"),
number
)
).geometry.coordinates,2
)
).Value } ) ) )

...all to get an ID column in this Collection!:

image.png

@RandyHayesand @RezaDorrani , thanks for the Sunday help! Have a great week!

 

@seadude 

I just hope we don't have that many earthquakes!!  Smiley LOL

Glad things are working now.

_____________________________________________________________________________________
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!

Thanks for the help here @RezaDorrani @RandyHayes.

 

One thing I'll add. When I want to understand the structure a little bit more and figure out when I need to use First() Last() etc., I use a JSON viewer:

 

code beautify.png

 

This one is Code Beautify which is one of the prettier viewers. The collapsing helps to understand things.

Microsoft Employee
@8bitclassroom

@RandyHayes, hep meh! I'm missing the pattern here... Looking to do a similar thing, but this time I have a different schema. Instead of earthquakes, I want to take the results of a Fuzzy Search and plot pins on a map.

Heres the schema:

 

{
    "summary": {
        "query": "pub",
        "queryType": "NON_NEAR",
        "queryTime": 39,
        "numResults": 10,
        "offset": 0,
        "totalResults": 30,
        "fuzzyLevel": 1,
        "geoBias": {
            "lat": 47.56328695,
            "lon": -122.37870965
        }
    },
    "results": [
        {
            "type": "POI",
            "id": "US/POI/p0/8718662",
            "score": 2.575,
            "dist": 128.26041102796466,
            "info": "search:ta:840539001007346-US",
            "poi": {
                "name": "West Seattle Brewing Company",
                "phone": "+(1)-(206)-7086627",
                "categorySet": [
                    {
                        "id": 9376007
                    }
                ],
                "categories": [
                    "café/pub",
                    "microbrewery/beer garden"
                ],
                "classifications": [
                    {
                        "code": "CAFE_PUB",
                        "names": [
                            {
                                "nameLocale": "en-US",
                                "name": "microbrewery/beer garden"
                            },
                            {
                                "nameLocale": "en-US",
                                "name": "café/pub"
                            }
                        ]
                    }
                ]
            },
            "address": {
                "streetNumber": "4415",
                "streetName": "Fauntleroy Way SW",
                "municipalitySubdivision": "Seattle, Genesee, Fairmount Park",
                "municipality": "Seattle",
                "countrySecondarySubdivision": "King",
                "countryTertiarySubdivision": "Seattle",
                "countrySubdivision": "WA",
                "postalCode": "98126",
                "extendedPostalCode": "981262631",
                "countryCode": "US",
                "country": "United States",
                "countryCodeISO3": "USA",
                "freeformAddress": "4415 Fauntleroy Way SW, Seattle, WA 98126",
                "localName": "Seattle",
                "countrySubdivisionName": "Washington"
            },
            "position": {
                "lat": 47.56428,
                "lon": -122.37784
            },
            "viewport": {
                "topLeftPoint": {
                    "lat": 47.56518,
                    "lon": -122.37917
                },
                "btmRightPoint": {
                    "lat": 47.56338,
                    "lon": -122.37651
                }
            },
            "entryPoints": [
                {
                    "type": "main",
                    "position": {
                        "lat": 47.56412,
                        "lon": -122.37767
                    }
                }
            ]
        }
    ]
}

 

Problem: I can only get the first set of Lat / Longs from the Fuzzy Search results

Tried so far:

/*====================================================================
Create a numbers table for ForAll looping purposes
====================================================================*/

Set(varNumTable, [1, 2, 3, 4, 5, 6, 7, 8, 9, 10]);

Clear(colNumbersTable);

Clear(colRecordToCount);

ClearCollect(colNumTemp, varNumTable);

ForAll(colNumTemp,
    ForAll(colNumTemp,
        ForAll(colNumTemp,
            Collect(colRecordToCount,
                {
                    record: 1
                }
            );
            Collect(colNumbersTable,
                {
                    number: CountRows(colRecordToCount)
                }
            )
        )

    )
);

/*====================================================================
Collect all nearby "pubs" within a 2mile (~3200 meter) radius
====================================================================*/

ClearCollect(
    colNearbySpots,
    azureMapTimezone.GETSearchFuzzy(1.0,1,3,
        {
            query: "pub",
            lon: Location.Longitude,
            lat: Location.Latitude,
            radius: 3200
        }
    )
);

/*====================================================================
Using the numbers table, create a Collection of all nearby spot Lat/Longs returned from 
the previous API call.

Thank god for the PowerApps forums!: https://powerusers.microsoft.com/t5/General-Discussion/Complex-Collection-of-a-Collection/m-p/267273#M78095
====================================================================*/
ClearCollect(colNearbySpotLatLongs,
    ForAll(colNumbersTable,
        If(number <= CountRows(Ungroup(colNearbySpots.results, "results")),
            {
                id:number, 
                long: First(First(colNearbySpots.results).results.position).position.lon,
                lat: First(First(colNearbySpots.results).results.position).position.lat
            } 
        )
    )
);

/*====================================================================
Using the table of nearby spot Lat/Longs and the numbers table, call the Azure Maps API 
to get a map image of these spots with pins, at each zoom level!
====================================================================*/
Clear(colNearbySpotMaps);

ForAll(
    Filter(colNumbersTable, number >= 10 && number <= 14),
    AddColumns(
        Collect(colNearbySpotMaps,
        azureMapTimezone.GetMapImageWithPins(
            1.0,
            600,
            600,
            {
                zoom: number,
                center: Concatenate(Text(Location.Longitude), ",", Text(Location.Latitude)),
                pins: Concatenate("default||", Concat(colNearbySpotLatLongs, lat & " " & lat, "|")),
                path: Concatenate("ra3200", "||", Text(Location.Longitude), " ", Text(Location.Latitude))
            }
        )
    ) ,
    "id",
    number
    )
);

ClearCollect(colNearbySpotMapsWithIDs,
    ForAll(colNumbersTable,
        If(number <= CountRows(colNearbySpots),
            {
                id:number,
                mapImage: colNearbySpotMaps
            }
        )
    )
)

I also tried First(Ungroup(colNearbySpots.results, "results").position).position.lon (/lat).

I end up with a lat/long list that only shows the first Result copied a bunch:

Screenshot from 2019-06-01 08-47-59.png
...and colNearbySpotMapsWithID is nested instead of a flat table:

image.png
image.png
I know this is a long post 🙂 . Hopefully the patterns that emerge for unfolding JSON will help others too.

Thank you!

@seadude 

So, I breezed through some of the post because I had a question from the start.  I see only one record with a position record in it...is the assumption that you have multiple records in the results array?

I'll start there - I saw some issues with the remaining formulas, but we can cover that after I clarify the above as I don't want to start down a road that is on the road trail.

_____________________________________________________________________________________
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!

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!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

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

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.    

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

Users online (816)