cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
nmasmo
Helper III
Helper III

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:

nmasmo_0-1679348206666.png

 

Or, it might look something like this…:

nmasmo_1-1679348206669.png

 

… 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:

nmasmo_2-1679348206672.png

 

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

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.

grantjenkins_0-1679442650015.png

 

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
        },
        {
            "Toy": "Basketball",
            "Workers per Toy": 25,
            "Monday Target": 180,
            "Tuesday Target": 200
        }
    ]
}

grantjenkins_1-1679442719528.png

 

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'], '}}')))

grantjenkins_2-1679442787566.png

 

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_', ' ')

grantjenkins_3-1679442928919.png

 

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

grantjenkins_4-1679442982069.png

 

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")]')))

grantjenkins_5-1679443099982.png

 

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'])

grantjenkins_6-1679443598720.png

 

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

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

grantjenkins_7-1679443687019.png

 

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.

{
    "Date": @{addDays(outputs('Body')?['WC'], items('Apply_to_each_Day'), 'yyyy-MM-dd')},
    "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
addDays(outputs('Body')?['WC'], items('Apply_to_each_Day'), 'yyyy-MM-dd')

//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'])

grantjenkins_8-1679443924983.png

 

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,
    "Toy": "Basketball",
    "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,
    "Toy": "Basketball",
    "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,
    "Toy": "Basketball",
    "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,
    "Toy": "Basketball",
    "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,
    "Toy": "Basketball",
    "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,
    "Toy": "Basketball",
    "Workers per Toy": 25,
    "Day Target": 200,
    "Hour Target": 66
  }
]

 


----------------------------------------------------------------------
If I've answered your question, please mark the post as Solved.
If you like my response, please consider giving it a Thumbs Up.

View solution in original post

6 REPLIES 6
grantjenkins
Super User
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 I've answered your question, please mark the post as Solved.
If you like my response, please consider giving it a Thumbs Up.
nmasmo
Helper III
Helper III

@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.

 

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.

grantjenkins_0-1679442650015.png

 

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
        },
        {
            "Toy": "Basketball",
            "Workers per Toy": 25,
            "Monday Target": 180,
            "Tuesday Target": 200
        }
    ]
}

grantjenkins_1-1679442719528.png

 

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'], '}}')))

grantjenkins_2-1679442787566.png

 

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_', ' ')

grantjenkins_3-1679442928919.png

 

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

grantjenkins_4-1679442982069.png

 

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")]')))

grantjenkins_5-1679443099982.png

 

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'])

grantjenkins_6-1679443598720.png

 

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

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

grantjenkins_7-1679443687019.png

 

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.

{
    "Date": @{addDays(outputs('Body')?['WC'], items('Apply_to_each_Day'), 'yyyy-MM-dd')},
    "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
addDays(outputs('Body')?['WC'], items('Apply_to_each_Day'), 'yyyy-MM-dd')

//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'])

grantjenkins_8-1679443924983.png

 

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,
    "Toy": "Basketball",
    "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,
    "Toy": "Basketball",
    "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,
    "Toy": "Basketball",
    "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,
    "Toy": "Basketball",
    "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,
    "Toy": "Basketball",
    "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,
    "Toy": "Basketball",
    "Workers per Toy": 25,
    "Day Target": 200,
    "Hour Target": 66
  }
]

 


----------------------------------------------------------------------
If I've answered your question, please mark the post as Solved.
If you like my response, please consider giving it a Thumbs Up.
nmasmo
Helper III
Helper III

@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)

nmasmo
Helper III
Helper III

@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.

nmasmo
Helper III
Helper III

@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.

Helpful resources

Announcements

Celebrating the May Super User of the Month: Laurens Martens

  @LaurensM  is an exceptional contributor to the Power Platform Community. Super Users like Laurens inspire others through their example, encouragement, and active participation. We are excited to celebrated Laurens as our Super User of the Month for May 2024.   Consistent Engagement:  He consistently engages with the community by answering forum questions, sharing insights, and providing solutions. Laurens dedication helps other users find answers and overcome challenges.   Community Expertise: As a Super User, Laurens plays a crucial role in maintaining a knowledge sharing environment. Always ensuring a positive experience for everyone.   Leadership: He shares valuable insights on community growth, engagement, and future trends. Their contributions help shape the Power Platform Community.   Congratulations, Laurens Martens, for your outstanding work! Keep inspiring others and making a difference in the community!   Keep up the fantastic work!        

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Users online (5,620)