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
RandyHayes
Super User
Super User

@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

Exclusive LIVE Community Event: Power Apps Copilot Coffee Chat with Copilot Studio Product Team

  It's time for the SECOND Power Apps Copilot Coffee Chat featuring the Copilot Studio product team, which will be held LIVE on April 3, 2024 at 9:30 AM Pacific Daylight Time (PDT).     This is an incredible opportunity to connect with members of the Copilot Studio product team and ask them anything about Copilot Studio. We'll share our special guests with you shortly--but we want to encourage to mark your calendars now because you will not want to miss the conversation.   This live event will give you the unique opportunity to learn more about Copilot Studio plans, where we’ll focus, and get insight into upcoming features. We’re looking forward to hearing from the community, so bring your questions!   TO GET ACCESS TO THIS EXCLUSIVE AMA: Kudo this post to reserve your spot! Reserve your spot now by kudoing this post.  Reservations will be prioritized on when your kudo for the post comes through, so don't wait! Click that "kudo button" today.   Invitations will be sent on April 2nd.Users posting Kudos after April 2nd. at 9AM PDT may not receive an invitation but will be able to view the session online after conclusion of the event. Give your "kudo" today and mark your calendars for April 3rd, 2024 at 9:30 AM PDT and join us for an engaging and informative session!

Tuesday Tip: Unlocking Community Achievements and Earning Badges

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!     THIS WEEK'S TIP: Unlocking Achievements and Earning BadgesAcross the Communities, you'll see badges on users profile that recognize and reward their engagement and contributions. These badges each signify a different achievement--and all of those achievements are available to any Community member! If you're a seasoned pro or just getting started, you too can earn badges for the great work you do. Check out some details on Community badges below--and find out more in the detailed link at the end of the article!       A Diverse Range of Badges to Collect The badges you can earn in the Community cover a wide array of activities, including: Kudos Received: Acknowledges the number of times a user’s post has been appreciated with a “Kudo.”Kudos Given: Highlights the user’s generosity in recognizing others’ contributions.Topics Created: Tracks the number of discussions initiated by a user.Solutions Provided: Celebrates the instances where a user’s response is marked as the correct solution.Reply: Counts the number of times a user has engaged with community discussions.Blog Contributor: Honors those who contribute valuable content and are invited to write for the community blog.       A Community Evolving Together Badges are not only a great way to recognize outstanding contributions of our amazing Community members--they are also a way to continue fostering a collaborative and supportive environment. As you continue to share your knowledge and assist each other these badges serve as a visual representation of your valuable contributions.   Find out more about badges in these Community Support pages in each Community: All About Community Badges - Power Apps CommunityAll About Community Badges - Power Automate CommunityAll About Community Badges - Copilot Studio CommunityAll About Community Badges - Power Pages Community

Tuesday Tips: Powering Up Your Community Profile

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!   This Week's Tip: Power Up Your Profile!  🚀 It's where every Community member gets their start, and it's essential that you keep it updated! Your Community User Profile is how you're able to get messages, post solutions, ask questions--and as you rank up, it's where your badges will appear and how you'll be known when you start blogging in the Community Blog. Your Community User Profile is how the Community knows you--so it's essential that it works the way you need it to! From changing your username to updating contact information, this Knowledge Base Article is your best resource for powering up your profile.     Password Puzzles? No Problem! Find out how to sync your Azure AD password with your community account, ensuring a seamless sign-in. No separate passwords to remember! Job Jumps & Email Swaps Changed jobs? Got a new email? Fear not! You'll find out how to link your shiny new email to your existing community account, keeping your contributions and connections intact. Username Uncertainties Unraveled Picking the perfect username is crucial--and sometimes the original choice you signed up with doesn't fit as well as you may have thought. There's a quick way to request an update here--but remember, your username is your community identity, so choose wisely. "Need Admin Approval" Warning Window? If you see this error message while using the community, don't worry. A simple process will help you get where you need to go. If you still need assistance, find out how to contact your Community Support team. Whatever you're looking for, when it comes to your profile, the Community Account Support Knowledge Base article is your treasure trove of tips as you navigate the nuances of your Community Profile. It’s the ultimate resource for keeping your digital identity in tip-top shape while engaging with the Power Platform Community. So, dive in and power up your profile today!  💪🚀   Community Account Support | Power Apps Community Account Support | Power AutomateCommunity Account Support | Copilot Studio  Community Account Support | Power Pages

Super User of the Month | Chris Piasecki

In our 2nd installment of this new ongoing feature in the Community, we're thrilled to announce that Chris Piasecki is our Super User of the Month for March 2024. If you've been in the Community for a while, we're sure you've seen a comment or marked one of Chris' helpful tips as a solution--he's been a Super User for SEVEN consecutive seasons!       Since authoring his first reply in April 2020 to his most recent achievement organizing the Canadian Power Platform Summit this month, Chris has helped countless Community members with his insights and expertise. In addition to being a Super User, Chris is also a User Group leader, Microsoft MVP, and a featured speaker at the Microsoft Power Platform Conference. His contributions to the new SUIT program, along with his joyous personality and willingness to jump in and help so many members has made Chris a fixture in the Power Platform Community.   When Chris isn't authoring solutions or organizing events, he's actively leading Piasecki Consulting, specializing in solution architecture, integration, DevOps, and more--helping clients discover how to strategize and implement Microsoft's technology platforms. We are grateful for Chris' insightful help in the Community and look forward to even more amazing milestones as he continues to assist so many with his great tips, solutions--always with a smile and a great sense of humor.You can find Chris in the Community and on LinkedIn. Thanks for being such a SUPER user, Chris! 💪🌠

Find Out What Makes Super Users So Super

We know many of you visit the Power Platform Communities to ask questions and receive answers. But do you know that many of our best answers and solutions come from Community members who are super active, helping anyone who needs a little help getting unstuck with Business Applications products? We call these dedicated Community members Super Users because they are the real heroes in the Community, willing to jump in whenever they can to help! Maybe you've encountered them yourself and they've solved some of your biggest questions. Have you ever wondered, "Why?"We interviewed several of our Super Users to understand what drives them to help in the Community--and discover the difference it has made in their lives as well! Take a look in our gallery today: What Motivates a Super User? - Power Platform Community (microsoft.com)

March User Group Update: New Groups and Upcoming Events!

  Welcome to this month’s celebration of our Community User Groups and exciting User Group events. We’re thrilled to introduce some brand-new user groups that have recently joined our vibrant community. Plus, we’ve got a lineup of engaging events you won’t want to miss. Let’s jump right in: New User Groups   Sacramento Power Platform GroupANZ Power Platform COE User GroupPower Platform MongoliaPower Platform User Group OmanPower Platform User Group Delta StateMid Michigan Power Platform Upcoming Events  DUG4MFG - Quarterly Meetup - Microsoft Demand PlanningDate: 19 Mar 2024 | 10:30 AM to 12:30 PM Central America Standard TimeDescription: Dive into the world of manufacturing with a focus on Demand Planning. Learn from industry experts and share your insights. Dynamics User Group HoustonDate: 07 Mar 2024 | 11:00 AM to 01:00 PM Central America Standard TimeDescription: Houston, get ready for an immersive session on Dynamics 365 and the Power Platform. Connect with fellow professionals and expand your knowledge. Reading Dynamics 365 & Power Platform User Group (Q1)Date: 05 Mar 2024 | 06:00 PM to 09:00 PM GMT Standard TimeDescription: Join our virtual meetup for insightful discussions, demos, and community updates. Let’s kick off Q1 with a bang! Leaders, Create Your Events!    Leaders of existing User Groups, don’t forget to create your events within the Community platform. By doing so, you’ll enable us to share them in future posts and newsletters. Let’s spread the word and make these gatherings even more impactful! Stay tuned for more updates, inspiring stories, and collaborative opportunities from and for our Community User Groups.   P.S. Have an event or success story to share? Reach out to us – we’d love to feature you!

Top Solution Authors
Top Kudoed Authors
Users online (5,913)