cancel
Showing results for
Did you mean:
Helper II

Power Automate Data Transformation From JSON, Triple Nested Apply to Each Loop

I have fictionalized and simplified this problem for discussion purposes.

Suppose I own a toy factory. Let’s keep it simple: This toy factory has a 2 day workweek (Monday and Tuesday) and a 2 hour day (Hour 1 and Hour 2). Every week, the toy factory produces several types of toys (the quantity of different types of toys that are produced can vary).

Before the start of the week, the toy factory manager creates a Toy Production Plan. The most important thing about the Toy Production Plan is it tells us how many units of a particular toy the factory is planning to make that week. The Toy Production Plan might look something like this:

Or, it might look something like this…:

… the point I am trying to make with these examples is that..

1. There is a variety of different toy types that can be manufactured each week
2. The Toy Production Plan starts on the Monday of that week
3. The Toy Production Plan has 4 columns: [Toy], [Workers per Toy], [Monday Target], [Tuesday Target].

Every week, this data will be passed to a Power Automate flow as a JSON object from a Power App.

I essentially need to do a data transformation with a Power Automate flow. The flow needs to transform the factory manager’s production plan into a structure that works with the data table that the data needs to be stored in (dataverse table) Below, I show what the transformation needs to look like:

In the dataverse data table, each row corresponds to a particular date – hour of day – toy combination. Each row of the dataverse table will contain an “Hour Target”, which is the target number of units that must be produced for that particular hour/date/toy. This value is equal to the target of units for the day, divided by 2. I don’t need to make this column in Power Automate, as I can just have a calculated column in the dataverse table that calculates this value simply by dividing the [Day Target] column’s value by 2.

With my current approach to solving this data transformation problem with Power Automate, I am attempting to make a triple nested “Apply to each” loop. The structure of the triple nested “Apply to each” loop may look something like this:

Loop through dates d of the week

Loop through hours h of the day

Loop through the toys t that will be produced that week

Write d, h, t, Day Target, and Workers per Toy to new row in dataverse table

However, when I try to build this flow, I end up running into tons of problems. If someone was able to figure out this flow in Power Automate, I’d worship you like the Power Automate god/goddess that you are.

Thank you!

1 ACCEPTED SOLUTION

Accepted Solutions
Super User

Hopefully this is what you're looking for. Note that I've built it to cater for X number of hours (would need to be passed into the flow, as well as the WC date). It will work out the number of days dynamically based on the Target properties (Monday Target, Tuesday Target, etc.).

For this example, I've used a single JSON object that contains the WC Date, Number of hours, and actual data. Assume this would all be passed into the flow via Power Apps in your solution. Also, note that I haven't added the action to add to your Dataverse table - just building up the objects that you can then easily use.

See full flow below. I'll go into each of the actions.

Body is a Compose that contains the data that would be passed in via Power Apps.

``````{
"WC": "2023-03-20",
"Hours": 3,
"Values": [
{
"Toy": "Ping poing ball",
"Workers per Toy": 20,
"Monday Target": 300,
"Tuesday Target": 200
},
{
"Toy": "Racecar",
"Workers per Toy": 18,
"Monday Target": 200,
"Tuesday Target": 250
},
{
"Workers per Toy": 25,
"Monday Target": 180,
"Tuesday Target": 200
}
]
}``````

XML is a Compose that converts our Values array (our data) to XML so we can use XPath expressions later in the flow. The expression used is.

``xml(json(concat('{"root": { value:', outputs('Body')?['Values'], '}}')))``

Select extracts out the Target property names from our data. This will allow us to retrieve the correct Targets for each day, and to dynamically calculate the number of days. The expressions used are:

``````//From
xpath(outputs('XML'), '//root/value[1]/*[contains(name(), "Target")]')

//Map
replace(xpath(item(), 'name(/*)'), '_x0020_', ' ')``````

Initialize variable Items creates a new variable called Items of type Array. This will eventually contain all of our objects.

Apply to each Day iterates over the number of days (starting with the value 0). If there were 3 days, we would iterate over 0, 1, and 2. It uses the following expression to generate the range we want to iterate over.

``range(0, length(xpath(outputs('XML'), '//root/value[1]/*[contains(name(), "Target")]')))``

Apply to each Hour iterates over each hour (starting with the value 1). If there were 4 hours, we would iterate over 1, 2, 3, and 4. It uses the following expression to generate the range we want to iterate over.

``range(1, outputs('Body')?['Hours'])``

Apply to each Day iterates over each of our data objects within the Values array. It uses the following expression.

``outputs('Body')?['Values']``

Append to array variable Items appends a new object for the current iteration. Below is the full expression for the object. Beneath that are each of the individual expressions used.

``````{
"Hour of Day": @{items('Apply_to_each_Hour')},
"Toy": @{items('Apply_to_each_Toy')?['Toy']},
"Workers per Toy": @{items('Apply_to_each_Toy')?['Workers per Toy']},
"Day Target": @{items('Apply_to_each_Toy')[body('Select')[items('Apply_to_each_Day')]]},
"Hour Target": @{div(items('Apply_to_each_Toy')[body('Select')[items('Apply_to_each_Day')]], outputs('Body')?['Hours'])}
}``````

``````//Date

//Hour of Day
items('Apply_to_each_Hour')

//Toy
items('Apply_to_each_Toy')?['Toy']

//Workers per Toy
items('Apply_to_each_Toy')?['Workers per Toy']

//Day Target
items('Apply_to_each_Toy')[body('Select')[items('Apply_to_each_Day')]]

//Hour Target (Day Target divided by number of days)
div(items('Apply_to_each_Toy')[body('Select')[items('Apply_to_each_Day')]], outputs('Body')?['Hours'])``````

For your example, you could remove the Items variable completely, and replace it with your Add a new row action and add the data directly into your table using the expressions above.

If we ran the flow, we would see the following output that's stored in our Array variable called Items.

``````[
{
"Date": "2023-03-20",
"Hour of Day": 1,
"Toy": "Ping poing ball",
"Workers per Toy": 20,
"Day Target": 300,
"Hour Target": 100
},
{
"Date": "2023-03-20",
"Hour of Day": 1,
"Toy": "Racecar",
"Workers per Toy": 18,
"Day Target": 200,
"Hour Target": 66
},
{
"Date": "2023-03-20",
"Hour of Day": 1,
"Workers per Toy": 25,
"Day Target": 180,
"Hour Target": 60
},
{
"Date": "2023-03-20",
"Hour of Day": 2,
"Toy": "Ping poing ball",
"Workers per Toy": 20,
"Day Target": 300,
"Hour Target": 100
},
{
"Date": "2023-03-20",
"Hour of Day": 2,
"Toy": "Racecar",
"Workers per Toy": 18,
"Day Target": 200,
"Hour Target": 66
},
{
"Date": "2023-03-20",
"Hour of Day": 2,
"Workers per Toy": 25,
"Day Target": 180,
"Hour Target": 60
},
{
"Date": "2023-03-20",
"Hour of Day": 3,
"Toy": "Ping poing ball",
"Workers per Toy": 20,
"Day Target": 300,
"Hour Target": 100
},
{
"Date": "2023-03-20",
"Hour of Day": 3,
"Toy": "Racecar",
"Workers per Toy": 18,
"Day Target": 200,
"Hour Target": 66
},
{
"Date": "2023-03-20",
"Hour of Day": 3,
"Workers per Toy": 25,
"Day Target": 180,
"Hour Target": 60
},
{
"Date": "2023-03-21",
"Hour of Day": 1,
"Toy": "Ping poing ball",
"Workers per Toy": 20,
"Day Target": 200,
"Hour Target": 66
},
{
"Date": "2023-03-21",
"Hour of Day": 1,
"Toy": "Racecar",
"Workers per Toy": 18,
"Day Target": 250,
"Hour Target": 83
},
{
"Date": "2023-03-21",
"Hour of Day": 1,
"Workers per Toy": 25,
"Day Target": 200,
"Hour Target": 66
},
{
"Date": "2023-03-21",
"Hour of Day": 2,
"Toy": "Ping poing ball",
"Workers per Toy": 20,
"Day Target": 200,
"Hour Target": 66
},
{
"Date": "2023-03-21",
"Hour of Day": 2,
"Toy": "Racecar",
"Workers per Toy": 18,
"Day Target": 250,
"Hour Target": 83
},
{
"Date": "2023-03-21",
"Hour of Day": 2,
"Workers per Toy": 25,
"Day Target": 200,
"Hour Target": 66
},
{
"Date": "2023-03-21",
"Hour of Day": 3,
"Toy": "Ping poing ball",
"Workers per Toy": 20,
"Day Target": 200,
"Hour Target": 66
},
{
"Date": "2023-03-21",
"Hour of Day": 3,
"Toy": "Racecar",
"Workers per Toy": 18,
"Day Target": 250,
"Hour Target": 83
},
{
"Date": "2023-03-21",
"Hour of Day": 3,
"Workers per Toy": 25,
"Day Target": 200,
"Hour Target": 66
}
]``````

----------------------------------------------------------------------
If you like my response, please consider giving it a Thumbs Up.
6 REPLIES 6
Super User

Challenge accepted 🙂

A couple of questions:

1. Will the Week Commencing Date also be passed into Power Automate from the Power App?
2. Does it need to work for any number of days and hours? And if so, how would you know the total number of hours.
3. Would it be a different number of days and/or hours each time you pass it into Power Automate from Power Apps?

I have it working for the simple set of data you provided in your example, but not flexible with regards to number of days/hours.

----------------------------------------------------------------------
If you like my response, please consider giving it a Thumbs Up.
Helper II

@grantjenkins Yes, the week commencing date will be passed into Power Automate from the Power App.

While I am interested in seeing what a solution would look like for any number of days and hours, for now I think its best to keep it simple (because my Power Automate skills are not advanced yet) and assume the number of work days and work hours stays constant. In the real-world situation where I will have to apply this solution, I will need to make it work for 5 business days in a work week, and 9 work hours in a work-day.

Super User

Hopefully this is what you're looking for. Note that I've built it to cater for X number of hours (would need to be passed into the flow, as well as the WC date). It will work out the number of days dynamically based on the Target properties (Monday Target, Tuesday Target, etc.).

For this example, I've used a single JSON object that contains the WC Date, Number of hours, and actual data. Assume this would all be passed into the flow via Power Apps in your solution. Also, note that I haven't added the action to add to your Dataverse table - just building up the objects that you can then easily use.

See full flow below. I'll go into each of the actions.

Body is a Compose that contains the data that would be passed in via Power Apps.

``````{
"WC": "2023-03-20",
"Hours": 3,
"Values": [
{
"Toy": "Ping poing ball",
"Workers per Toy": 20,
"Monday Target": 300,
"Tuesday Target": 200
},
{
"Toy": "Racecar",
"Workers per Toy": 18,
"Monday Target": 200,
"Tuesday Target": 250
},
{
"Workers per Toy": 25,
"Monday Target": 180,
"Tuesday Target": 200
}
]
}``````

XML is a Compose that converts our Values array (our data) to XML so we can use XPath expressions later in the flow. The expression used is.

``xml(json(concat('{"root": { value:', outputs('Body')?['Values'], '}}')))``

Select extracts out the Target property names from our data. This will allow us to retrieve the correct Targets for each day, and to dynamically calculate the number of days. The expressions used are:

``````//From
xpath(outputs('XML'), '//root/value[1]/*[contains(name(), "Target")]')

//Map
replace(xpath(item(), 'name(/*)'), '_x0020_', ' ')``````

Initialize variable Items creates a new variable called Items of type Array. This will eventually contain all of our objects.

Apply to each Day iterates over the number of days (starting with the value 0). If there were 3 days, we would iterate over 0, 1, and 2. It uses the following expression to generate the range we want to iterate over.

``range(0, length(xpath(outputs('XML'), '//root/value[1]/*[contains(name(), "Target")]')))``

Apply to each Hour iterates over each hour (starting with the value 1). If there were 4 hours, we would iterate over 1, 2, 3, and 4. It uses the following expression to generate the range we want to iterate over.

``range(1, outputs('Body')?['Hours'])``

Apply to each Day iterates over each of our data objects within the Values array. It uses the following expression.

``outputs('Body')?['Values']``

Append to array variable Items appends a new object for the current iteration. Below is the full expression for the object. Beneath that are each of the individual expressions used.

``````{
"Hour of Day": @{items('Apply_to_each_Hour')},
"Toy": @{items('Apply_to_each_Toy')?['Toy']},
"Workers per Toy": @{items('Apply_to_each_Toy')?['Workers per Toy']},
"Day Target": @{items('Apply_to_each_Toy')[body('Select')[items('Apply_to_each_Day')]]},
"Hour Target": @{div(items('Apply_to_each_Toy')[body('Select')[items('Apply_to_each_Day')]], outputs('Body')?['Hours'])}
}``````

``````//Date

//Hour of Day
items('Apply_to_each_Hour')

//Toy
items('Apply_to_each_Toy')?['Toy']

//Workers per Toy
items('Apply_to_each_Toy')?['Workers per Toy']

//Day Target
items('Apply_to_each_Toy')[body('Select')[items('Apply_to_each_Day')]]

//Hour Target (Day Target divided by number of days)
div(items('Apply_to_each_Toy')[body('Select')[items('Apply_to_each_Day')]], outputs('Body')?['Hours'])``````

For your example, you could remove the Items variable completely, and replace it with your Add a new row action and add the data directly into your table using the expressions above.

If we ran the flow, we would see the following output that's stored in our Array variable called Items.

``````[
{
"Date": "2023-03-20",
"Hour of Day": 1,
"Toy": "Ping poing ball",
"Workers per Toy": 20,
"Day Target": 300,
"Hour Target": 100
},
{
"Date": "2023-03-20",
"Hour of Day": 1,
"Toy": "Racecar",
"Workers per Toy": 18,
"Day Target": 200,
"Hour Target": 66
},
{
"Date": "2023-03-20",
"Hour of Day": 1,
"Workers per Toy": 25,
"Day Target": 180,
"Hour Target": 60
},
{
"Date": "2023-03-20",
"Hour of Day": 2,
"Toy": "Ping poing ball",
"Workers per Toy": 20,
"Day Target": 300,
"Hour Target": 100
},
{
"Date": "2023-03-20",
"Hour of Day": 2,
"Toy": "Racecar",
"Workers per Toy": 18,
"Day Target": 200,
"Hour Target": 66
},
{
"Date": "2023-03-20",
"Hour of Day": 2,
"Workers per Toy": 25,
"Day Target": 180,
"Hour Target": 60
},
{
"Date": "2023-03-20",
"Hour of Day": 3,
"Toy": "Ping poing ball",
"Workers per Toy": 20,
"Day Target": 300,
"Hour Target": 100
},
{
"Date": "2023-03-20",
"Hour of Day": 3,
"Toy": "Racecar",
"Workers per Toy": 18,
"Day Target": 200,
"Hour Target": 66
},
{
"Date": "2023-03-20",
"Hour of Day": 3,
"Workers per Toy": 25,
"Day Target": 180,
"Hour Target": 60
},
{
"Date": "2023-03-21",
"Hour of Day": 1,
"Toy": "Ping poing ball",
"Workers per Toy": 20,
"Day Target": 200,
"Hour Target": 66
},
{
"Date": "2023-03-21",
"Hour of Day": 1,
"Toy": "Racecar",
"Workers per Toy": 18,
"Day Target": 250,
"Hour Target": 83
},
{
"Date": "2023-03-21",
"Hour of Day": 1,
"Workers per Toy": 25,
"Day Target": 200,
"Hour Target": 66
},
{
"Date": "2023-03-21",
"Hour of Day": 2,
"Toy": "Ping poing ball",
"Workers per Toy": 20,
"Day Target": 200,
"Hour Target": 66
},
{
"Date": "2023-03-21",
"Hour of Day": 2,
"Toy": "Racecar",
"Workers per Toy": 18,
"Day Target": 250,
"Hour Target": 83
},
{
"Date": "2023-03-21",
"Hour of Day": 2,
"Workers per Toy": 25,
"Day Target": 200,
"Hour Target": 66
},
{
"Date": "2023-03-21",
"Hour of Day": 3,
"Toy": "Ping poing ball",
"Workers per Toy": 20,
"Day Target": 200,
"Hour Target": 66
},
{
"Date": "2023-03-21",
"Hour of Day": 3,
"Toy": "Racecar",
"Workers per Toy": 18,
"Day Target": 250,
"Hour Target": 83
},
{
"Date": "2023-03-21",
"Hour of Day": 3,
"Workers per Toy": 25,
"Day Target": 200,
"Hour Target": 66
}
]``````

----------------------------------------------------------------------
If you like my response, please consider giving it a Thumbs Up.
Helper II

@grantjenkins
FYI: I'm still working on your solution idea, I will update you as soon as I've got it worked out (I've got some new concepts to learn here like XML and Xpath)

Helper II

@grantjenkins
Thank you for this. Very impressive solution. I just mimicked your solution on my environment. I understand it for the most part.
Next I am going to try to implement this proof of concept into the real-world business problem I'm facing. I'll keep you posted.

Helper II

@grantjenkins  Just did a bigger, more realistic test of this solution. It worked! Just "Accepted as Solution".

This solution will be good for helping people do some advanced data transformations in Power Automate.

Announcements

Announcing the MPPC's Got Power Talent Show at #MPPC23

Are you attending the Microsoft Power Platform Conference 2023 in Las Vegas? If so, we invite you to join us for the MPPC's Got Power Talent Show!      Our talent show is more than a show—it's a grand celebration of connection, inspiration, and shared journeys. Through stories, skills, and collective experiences, we come together to uplift, inspire, and revel in the magic of our community's diverse talents. This year, our talent event promises to be an unforgettable experience, echoing louder and brighter than anything you've seen before.    We're casting a wider net with three captivating categories:  Demo Technical Solutions: Show us your Power Platform innovations, be it apps, flows, chatbots, websites or dashboards... Storytelling: Share tales of your journey with Power Platform. Hidden Talents: Unveil your creative side—be it dancing, singing, rapping, poetry, or comedy. Let your talent shine!    Got That Special Spark? A Story That Demands to Be Heard? Your moment is now!  Sign up to Showcase Your Brilliance: https://aka.ms/MPPCGotPowerSignUp  Deadline for submissions: Thursday, Sept 28th    How It Works:  Submit this form to sign up: https://aka.ms/MPPCGotPowerSignUp  We'll contact you if you're selected. Get ready to be onstage!  The Spotlight is Yours: Each participant has 3-5 minutes to shine, with insightful commentary from our panel of judges. We’re not just giving you a stage; we’re handing you the platform to make your mark.     Be the Story We Tell: Your talents and narratives will not just entertain but inspire, serving as the bedrock for our community’s future stories and successes.    Celebration, Surprises, and Connections: As the curtain falls, the excitement continues! Await surprise awards and seize the chance to mingle with industry experts, Microsoft Power Platform leaders, and community luminaries. It's not just a show; it's an opportunity to forge connections and celebrate shared successes.    Event Details:  Date and Time: Wed Oct 4th, 6:30-9:00PM   Location: MPPC23 at the MGM Grand, Las Vegas, NV, USA

September User Group Success Story: Reading Dynamics 365 & Power Platform User Group

The Reading Dynamics 365 and Power Platform User Group is a community-driven initiative that started in September 2022. It has quickly earned recognition for its enthusiastic leadership and resilience in the face of challenges. With a focus on promoting learning and networking among professionals in the Dynamics 365 and Power Platform ecosystem, the group has grown steadily and gained a reputation for its commitment to its members!   The group, which had its inaugural event in January 2023 at the Microsoft UK Headquarters in Reading, has since organized three successful gatherings, including a recent social lunch. They maintain a regular schedule of four events per year, each attended by an average of 20-25 enthusiastic participants who enjoy engaging talks and, of course, pizza.   The Reading User Group's presence is primarily spread through LinkedIn and Meetup, with the support of the wider community. This thriving community is managed by a dedicated team consisting of Fraser Dear, Tim Leung, and Andrew Bibby, who serves as the main point of contact for the UK Dynamics 365 and Power Platform User Groups.   Andrew Bibby, an active figure in the Dynamics 365 and Power Platform community, nominated this group due to his admiration for the Reading UK User Group's efforts. He emphasized their remarkable enthusiasm and success in running the group, noting that they navigated challenges such as finding venues with resilience and smiles on their faces. Despite being a relatively new group with 20-30 members, they have managed to achieve high attendance at their meetings.   The group's journey began when Fraser Dear moved to the Reading area and realized the absence of a user group catering to professionals in the Dynamics 365 and Power Platform space. He reached out to Andrew, who provided valuable guidance and support, allowing the Reading User Group to officially join the UK Dynamics 365 and Power Platform User Groups community.   One of the group's notable achievements was overcoming the challenge of finding a suitable venue. Initially, their "home" was the Microsoft UK HQ in Reading. However, due to office closures, they had to seek a new location with limited time. Fortunately, a connection with Stephanie Stacey from Microsoft led them to Reading College and its Institute of Technology. The college generously offered them event space and support, forging a mutually beneficial partnership where the group promotes the Institute and encourages its members to support the next generation of IT professionals.   With the dedication of its leadership team, the Reading Dynamics 365 and Power Platform User Group is poised to continue growing and thriving! Their story exemplifies the power of community-driven initiatives and the positive impact they can have on professional development and networking in the tech industry. As they move forward with their upcoming events and collaborations with Reading College, the group is likely to remain a valuable resource for professionals in the Reading area and beyond.

A Celebration of What We've Achieved--And Announcing Our Winners

As the sun sets on the #SummerofSolutions Challenge, it's time to reflect and celebrate! The journey we embarked upon together was not just about providing answers – it was about fostering a sense of community, encouraging collaboration, and unlocking the true potential of the Power Platform tools.   From the initial announcement to the final week's push, the Summer of Solutions Challenge has been a whirlwind of engagement and growth. It was a call to action for every member of our Power Platform community, urging them to contribute their expertise, engage in discussions, and elevate collective knowledge across the community as part of the low-code revolution.   Reflecting on the Impact As the challenge ends, it's essential to reflect on the impact it’s had across our Power Platform communities: Community Resilience: The challenge demonstrated the resilience of our community. Despite geographical distances and diverse backgrounds, we came together to contribute, learn, and collaborate. This resilience is the cornerstone of our collective strength.Diverse Expertise: The solutions shared during the challenge underscore the incredible expertise within our community. From intricate technical insights to creative problem-solving, our members showcased their diverse skill sets, enhancing our community's depth.Shared Learning: Solutions spurred shared learning. They provided opportunities for members to grasp new concepts, expand their horizons, and uncover the Power Platform tools' untapped potential. This learning ripple effect will continue to shape our growth. Empowerment: Solutions empowered community members. They validated their knowledge, boosted their confidence, and highlighted their contributions. Each solution shared was a step towards personal and communal empowerment. We are proud and thankful as we conclude the Summer of Solutions Challenge. The challenge showed the potential of teamwork, the benefit of knowledge-sharing, and the resilience of our Power Platform community. The solutions offered by each member are more than just answers; they are the expression of our shared commitment to innovation, growth, and progress!     Drum roll, Please... And now, without further ado, it's time to announce the winners who have risen above the rest in the Summer of Solutions Challenge!   These are the top community users and Super Users who have not only earned recognition but have become beacons of inspiration for us all.   Power Apps Community:  Community User Winner: @SpongYe Super User Winner: Pending Acceptance Power Automate Community:  Community User Winner: @trice602 Super User Winner: @Expiscornovus  Power Virtual Agents Community: Community User Winner: Pending AcceptanceSuper User: Pending Acceptance Power Pages Community: Community User Winner: @OOlashyn Super User Winner: @ChristianAbata   We are also pleased to announced two additional tickets that we are awarding to the Overall Top Solution providers in the following communities:    Power Apps: @LaurensM   Power Automate: @ManishSolanki    Thank you for making this challenge a resounding success. Your participation has reaffirmed the strength of our community and the boundless potential that lies within each of us. Let's keep the spirit of collaboration alive as we continue on this incredible journey in Power Platform together.Winners, we will see you in Vegas! Every other amazing solutions superstar, we will see you in the Community!Congratulations, everyone!

Ayonija Shatakshi, a seasoned senior consultant at Improving, Ohio, is a passionate advocate for M365, SharePoint, Power Platform, and Azure, recognizing how they synergize to deliver top-notch solutions. Recently, we asked Ayonija to share her journey as a user group leader, shedding light on her motivations and the benefits she's reaped from her community involvement.      Ayonija embarked on her role as a user group leader in December 2022, driven by a desire to explore how the community leveraged various Power Platform components. When she couldn't find a suitable local group, she decided to create one herself!    Speaking about the impact of the community on her professional and personal growth, Ayonija says, "It's fascinating to witness how everyone navigates the world of Power Platform, dealing with license constraints and keeping up with new features. There's so much to learn from their experiences.:        Her favorite aspect of being a user group leader is the opportunity to network and engage in face-to-face discussions with fellow enthusiasts, fostering deeper connections within the community. Offering advice to budding user group leaders, Ayonija emphasized the importance of communication and consistency, two pillars that sustain any successful community initiative.      When asked why she encourages others to become user group leaders, Ayonija said, "Being part of a user group is one of the best ways to connect with experienced professionals in the same field and glean knowledge from them. If there isn't a local group, consider starting one; you'll soon find like-minded individuals."      Her highlight from the past year as a user group leader was witnessing consistent growth within the group, a testament to the thriving community she has nurtured. Advocating for user group participation, Ayonija stated, "It's the fastest route to learning from the community, gaining insights, and staying updated on industry trends."   Check out her group: Cleveland Power Platform User Group

An MPPC23 Invitation from Charles Lamanna, CVP of Microsoft Business Applications & Platform

Hear from Corporate Vice President for Microsoft Business Applications & Platform, Charles Lamanna, as he looks ahead to the second annual Microsoft Power Platform Conference from October 3rd-5th 2023 at the MGM Grand in Las Vegas.Have you got your tickets yet? Register today at www.powerplatformconf.com

Top Solution Authors
Top Kudoed Authors
Users online (3,685)