cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Extracting certain data from initialize variable

Hi guys,

 

I am trying to extract certain bits of information from my flow. Basically the flow starts a runbook which extracts information about license usage in the tenant. I am trying to extract the number of licenses available  vs the number of licenses used. This is the overall Flow:

 

david_ashworth_0-1629262741816.png

 

This is the section i want to extract information from:

 

david_ashworth_4-1629263037397.png

 

In particular i want 2 bits of info from the Value output:

 

david_ashworth_3-1629262977366.png

 

ConsumedUnits : 1

PrepaidUnits - Enabled: 2

 

That way i can tell the tenant has 2 licenses, 1 is used therefore 1 is available. How would i extract those 2 bits of information so i can email the details?

 

Thanks,

David

 

1 ACCEPTED SOLUTION

Accepted Solutions
poweractivate
Most Valuable Professional
Most Valuable Professional

@david_ashworth 

 

You can try something like this:

 

Presuming an input somewhat like this:

82021-class-00.png

 

1. You can Initialize a variable for each of the 2 bits of info you want:

consumedUnits

enabledPrepaidUnits

 

 

Make them both Integer for the Type. You don't have to if it doesn't make sense for your scenario (e.g. if String makes more sense) but I presume for now the data type of the Variables being Integer makes most sense and may even be required.

 

Leave Value blank for both of them.

 

82021-class-01.png

 

2. You can use a Compose block and an expression to split the whole thing by the new line character

 

split(outputs('Compose'),decodeUriComponent('%0A'))

 

 

In Power Automate, the expression in a Flow to explicitly specify a newline character is

 

decodeUriComponent('%0A')

 

and

 

split(outputs('Compose'),decodeUriComponent('%0A'))

 

 

 

The "split" function converts a string given in the first argument (in this case, the original input), into a resulting Array output, where each element of Array is split up (delimited) by the string in the given second argument (in this case, that would be decodeUriComponent('%0A') or in other words, a "new line" character in Power Automate).

 

Like below:

 

82021-class-02.png

 

 

3. Now you can enter into an Apply to Each using the Compose Action Block output, that should have what is now an Array, where each item is each line in sequence from the original input:

82021-class-03.png

 

 

Now inside the Apply to Each:

 

4. First, a Compose can be defined here to split the line by the colon (:) character, as follows:

 

split(items('Apply_to_each'),':')

 

 

82021-class-04.png

 

Next, you can enter into a Switch which has two cases. For now, for the sake of simplicity, the two cases will be consumedunits and enabled. Going over each step, that would be:

 

5. Enter into a Switch  (yes, this is still inside the Apply to Each) and then for the value of "On" use this Expression:

 

toLower(trim(outputs('Compose_3')[0]))

 

 

To break it down,

the meaning of 

 

outputs('Compose_3')[0]

 

 

is that since now Compose_3 should contain an Array which is that particular line split by the colon (:) character, the element 0 should contain the left side. If using [1] that would refer to the right side. It is presumed for now and for simplicity, that we are only interested in those lines which have Key : Value like syntax (if any line does not have that format, it's fine - there won't be any error, you'll see later why).

 

Please note that for good practice, it may be better to use the syntax ?[0] rather than [0] as I am using here, as the question mark in the expression prefixing the index access may result in the index access attempt being more tolerant to unexpected cases such as a "completely empty value" for "outputs('Compose_3')" and to at least return an empty value rather than to just error out in some cases - for simplicity and for now, this question mark syntax is not used, and with the test run (see end of post) this did not cause any error anyway.

 

trim(outputs('Compose_3')[0])

 

The above "trim" function will remove leading and trailing white space to make sure any comparisons later won't fail due to leading or trailing whitespace related reasons, and finally

 

toLower(trim(outputs('Compose_3')[0]))

 

The above "toLower"  function will make it all lower-case to make sure any comparisons later won't fail due to potential case-sensitivity related reasons.

 

 

So you can enter into the switch like this:

82021-class-05.png

 

Even if some of the lines don't even have a colon - that's fine - the Switch will just flow to the Default case and do nothing, which is exactly fine for these purposes.

 

 

Here is the content of each Case:

 

6. For the condition of the first Case, i.e. the field that says "Equals" you can have:

consumedunits

Yes, it is all lowercase and with no trailing and leading whitespace - due to the expression used in the Switch On itself previously, the comparison will be case insensitive and should work no matter how many trailing or leading spaces there were during the split.

 

 You can add a Set variable Action block,

for the Name select the following from the dropdown:

consumedUnits

(Note: this is the name of one of the variables defined in the Initialize Variable in Step 1 at the top, and it should be selected from the dropdown under 'Name' for the 'Set Variable' Action block)

and for the Value, use

 

int(trim(outputs('Compose_3')[1]))

 

"trim" removes leading and trailing whitespace.

 

The reason for the outer wrapped function "int" is to convert the result to an Integer - since remember the variable was initialized as an Integer. Not using the int expression here, will cause in an error in the Flow run, because just the trim will still make it tobe left as a string if the "int" function is not wrapped there, which takes that String and converts it to an Integer.

 

As mentioned before, [0] was to access the left side - now [1] is used to access the right side, or in other words, the actual value of the bit of data that is desired!

 

82021-class-06.png

 

 

7. To the right the ellipses on the "Case" Action block, there should be a circle with a plus sign. Click that to add another Case.

There should now be a block named Case 2

Do something almost identical the previous step - use a Set variable block - use the same Value 

but this time, use this for the "Equals" use this:

enabled

And yes, all lowercase like before.

Also, for the "Name" select the following value from the dropdown

enabledPrepaidUnits

(Note: this is the name of one of the variables defined in the Initialize Variable in Step 1 at the top, and it should be selected from the dropdown under 'Name' for the 'Set Variable 2' Action block)

 

See below for example:

 

82021-class-07.png

 Now, outside of the Switch and outside of the Apply to Each:

8. Finally, you can add two Compose blocks (outside of the Switch and outside of the Apply to Each) at the very end of the Flow to clearly check if it is really working.

 

82021-class-08.png

 

9. When testing my above Flow, I get the expected values for the Variables based on the Compose 4 and 5 :

2 for consumedUnits, and

1 for enabledPrepaidUnits:

 

For consumedUnits (Compose 4) and prepaidEnabledUnits (Compose 5) shown below, test run results:

 

82021-class-09.png

 

 

As you can see, it is working correctly. 

 

Despite the custom format of the data based on the result of a runbook making it seem like it would be impossible to extract any data, you can use Power Automate and something like my approach above to go through it and extract the data you want seamlessly like this.

 

There is one thing to note: 

 

For now I simplified the PrepaidUnits - Enabled: 2 part.

For example, what happens if you want to extract something else later that's called "Enabled"?

For simplification purposes, I did not cover it in this post, so you may need to adjust that part for your scenario.

 

For now, here are some possible approaches to consider if you really do need to make it more complex for the  PrepaidUnits - Enabled part:

 

Potential Approaches - knowing when you have entered a "class" in your data format

 

Suppose you have one or more lines later with "Enabled" on the left side of a colon - that could pose an issue and the above solution may not suffice. If so, you may have to use additional functionality in the Flow - such as using another variable at the top to keep track when you "enter" and "exit" a "class" and that actually keeps track of the name of the current class entered (you can potentially determine if you entered one by checking if the "right side" of the line contains, e.g. "class licenseunitsdetail", etc. - then using split, etc. to just get that name and set it in the variable - checking for right side of the line only containing a } to check if it exits, etc. - and setting an appropriate variable. What you can then do is something like perhaps having an "outer switch" that branches to different switch based on which "class" it is in, or if it is not in a class use the similar branch kind of like the one I already gave here.

 

If you are able to rely on the specific order of the information in this specific case, and you still need a way to have multiple bits of data that are called "Enabled" across multiple lines but want to avoid the complexity of the above idea, then you might prefer to do a "semi-easier" way for now and just presume that the first occurrence of Enabled must be LicenseUnitsDetail, the second occurrence must be Y, third occurrence must be Z, etc. You would basically do the same as the above except using a hard-coded Array (perhaps a Compose) and the variable can be the index of the occurrence of, say, "Enabled", etc.  In fact, this may be a good idea to do it first this way to test before doing the above way. In case it suffices, it can just be used - if it does not suffice, it can be a way to test the above idea without implementing it all the way at first - then doing the above after that.

 

 

By the way:

To clarify, the steps given above are in order.

In case it helps, here is a 10,000 foot view of the completed Flow:

 

82021-class-10000.png

 

And a 1,000 foot view of what's in just the Apply to Each (with the Switch collapsed / folded in):

82021-class-1000.png

 

 

 

 

Check if it helps @david_ashworth 

 

View solution in original post

1 REPLY 1
poweractivate
Most Valuable Professional
Most Valuable Professional

@david_ashworth 

 

You can try something like this:

 

Presuming an input somewhat like this:

82021-class-00.png

 

1. You can Initialize a variable for each of the 2 bits of info you want:

consumedUnits

enabledPrepaidUnits

 

 

Make them both Integer for the Type. You don't have to if it doesn't make sense for your scenario (e.g. if String makes more sense) but I presume for now the data type of the Variables being Integer makes most sense and may even be required.

 

Leave Value blank for both of them.

 

82021-class-01.png

 

2. You can use a Compose block and an expression to split the whole thing by the new line character

 

split(outputs('Compose'),decodeUriComponent('%0A'))

 

 

In Power Automate, the expression in a Flow to explicitly specify a newline character is

 

decodeUriComponent('%0A')

 

and

 

split(outputs('Compose'),decodeUriComponent('%0A'))

 

 

 

The "split" function converts a string given in the first argument (in this case, the original input), into a resulting Array output, where each element of Array is split up (delimited) by the string in the given second argument (in this case, that would be decodeUriComponent('%0A') or in other words, a "new line" character in Power Automate).

 

Like below:

 

82021-class-02.png

 

 

3. Now you can enter into an Apply to Each using the Compose Action Block output, that should have what is now an Array, where each item is each line in sequence from the original input:

82021-class-03.png

 

 

Now inside the Apply to Each:

 

4. First, a Compose can be defined here to split the line by the colon (:) character, as follows:

 

split(items('Apply_to_each'),':')

 

 

82021-class-04.png

 

Next, you can enter into a Switch which has two cases. For now, for the sake of simplicity, the two cases will be consumedunits and enabled. Going over each step, that would be:

 

5. Enter into a Switch  (yes, this is still inside the Apply to Each) and then for the value of "On" use this Expression:

 

toLower(trim(outputs('Compose_3')[0]))

 

 

To break it down,

the meaning of 

 

outputs('Compose_3')[0]

 

 

is that since now Compose_3 should contain an Array which is that particular line split by the colon (:) character, the element 0 should contain the left side. If using [1] that would refer to the right side. It is presumed for now and for simplicity, that we are only interested in those lines which have Key : Value like syntax (if any line does not have that format, it's fine - there won't be any error, you'll see later why).

 

Please note that for good practice, it may be better to use the syntax ?[0] rather than [0] as I am using here, as the question mark in the expression prefixing the index access may result in the index access attempt being more tolerant to unexpected cases such as a "completely empty value" for "outputs('Compose_3')" and to at least return an empty value rather than to just error out in some cases - for simplicity and for now, this question mark syntax is not used, and with the test run (see end of post) this did not cause any error anyway.

 

trim(outputs('Compose_3')[0])

 

The above "trim" function will remove leading and trailing white space to make sure any comparisons later won't fail due to leading or trailing whitespace related reasons, and finally

 

toLower(trim(outputs('Compose_3')[0]))

 

The above "toLower"  function will make it all lower-case to make sure any comparisons later won't fail due to potential case-sensitivity related reasons.

 

 

So you can enter into the switch like this:

82021-class-05.png

 

Even if some of the lines don't even have a colon - that's fine - the Switch will just flow to the Default case and do nothing, which is exactly fine for these purposes.

 

 

Here is the content of each Case:

 

6. For the condition of the first Case, i.e. the field that says "Equals" you can have:

consumedunits

Yes, it is all lowercase and with no trailing and leading whitespace - due to the expression used in the Switch On itself previously, the comparison will be case insensitive and should work no matter how many trailing or leading spaces there were during the split.

 

 You can add a Set variable Action block,

for the Name select the following from the dropdown:

consumedUnits

(Note: this is the name of one of the variables defined in the Initialize Variable in Step 1 at the top, and it should be selected from the dropdown under 'Name' for the 'Set Variable' Action block)

and for the Value, use

 

int(trim(outputs('Compose_3')[1]))

 

"trim" removes leading and trailing whitespace.

 

The reason for the outer wrapped function "int" is to convert the result to an Integer - since remember the variable was initialized as an Integer. Not using the int expression here, will cause in an error in the Flow run, because just the trim will still make it tobe left as a string if the "int" function is not wrapped there, which takes that String and converts it to an Integer.

 

As mentioned before, [0] was to access the left side - now [1] is used to access the right side, or in other words, the actual value of the bit of data that is desired!

 

82021-class-06.png

 

 

7. To the right the ellipses on the "Case" Action block, there should be a circle with a plus sign. Click that to add another Case.

There should now be a block named Case 2

Do something almost identical the previous step - use a Set variable block - use the same Value 

but this time, use this for the "Equals" use this:

enabled

And yes, all lowercase like before.

Also, for the "Name" select the following value from the dropdown

enabledPrepaidUnits

(Note: this is the name of one of the variables defined in the Initialize Variable in Step 1 at the top, and it should be selected from the dropdown under 'Name' for the 'Set Variable 2' Action block)

 

See below for example:

 

82021-class-07.png

 Now, outside of the Switch and outside of the Apply to Each:

8. Finally, you can add two Compose blocks (outside of the Switch and outside of the Apply to Each) at the very end of the Flow to clearly check if it is really working.

 

82021-class-08.png

 

9. When testing my above Flow, I get the expected values for the Variables based on the Compose 4 and 5 :

2 for consumedUnits, and

1 for enabledPrepaidUnits:

 

For consumedUnits (Compose 4) and prepaidEnabledUnits (Compose 5) shown below, test run results:

 

82021-class-09.png

 

 

As you can see, it is working correctly. 

 

Despite the custom format of the data based on the result of a runbook making it seem like it would be impossible to extract any data, you can use Power Automate and something like my approach above to go through it and extract the data you want seamlessly like this.

 

There is one thing to note: 

 

For now I simplified the PrepaidUnits - Enabled: 2 part.

For example, what happens if you want to extract something else later that's called "Enabled"?

For simplification purposes, I did not cover it in this post, so you may need to adjust that part for your scenario.

 

For now, here are some possible approaches to consider if you really do need to make it more complex for the  PrepaidUnits - Enabled part:

 

Potential Approaches - knowing when you have entered a "class" in your data format

 

Suppose you have one or more lines later with "Enabled" on the left side of a colon - that could pose an issue and the above solution may not suffice. If so, you may have to use additional functionality in the Flow - such as using another variable at the top to keep track when you "enter" and "exit" a "class" and that actually keeps track of the name of the current class entered (you can potentially determine if you entered one by checking if the "right side" of the line contains, e.g. "class licenseunitsdetail", etc. - then using split, etc. to just get that name and set it in the variable - checking for right side of the line only containing a } to check if it exits, etc. - and setting an appropriate variable. What you can then do is something like perhaps having an "outer switch" that branches to different switch based on which "class" it is in, or if it is not in a class use the similar branch kind of like the one I already gave here.

 

If you are able to rely on the specific order of the information in this specific case, and you still need a way to have multiple bits of data that are called "Enabled" across multiple lines but want to avoid the complexity of the above idea, then you might prefer to do a "semi-easier" way for now and just presume that the first occurrence of Enabled must be LicenseUnitsDetail, the second occurrence must be Y, third occurrence must be Z, etc. You would basically do the same as the above except using a hard-coded Array (perhaps a Compose) and the variable can be the index of the occurrence of, say, "Enabled", etc.  In fact, this may be a good idea to do it first this way to test before doing the above way. In case it suffices, it can just be used - if it does not suffice, it can be a way to test the above idea without implementing it all the way at first - then doing the above after that.

 

 

By the way:

To clarify, the steps given above are in order.

In case it helps, here is a 10,000 foot view of the completed Flow:

 

82021-class-10000.png

 

And a 1,000 foot view of what's in just the Apply to Each (with the Switch collapsed / folded in):

82021-class-1000.png

 

 

 

 

Check if it helps @david_ashworth 

 

Helpful resources

Announcements

Update! June 13th, Community Ambassador Call for User Group Leaders and Super Users

Calling all Super Users & User Group Leaders   UPDATE:  We just wrapped up June's Community Ambassador monthly calls for Super Users and User Group Leaders. We had a fantastic call with lots of engagement. We are excited to share some highlights with you!    Big THANK YOU to our special guest Thomas Verhasselt, from the Copilot Studio Product Team for sharing how to use Power Platform Templates to achieve next generation growth.     A few key takeaways: Copilot Studio Cookbook Challenge:  Week 1 results are posted, Keep up the great work!Summer of Solutions:  Starting on Monday, June 17th. Just by providing solutions in the community, you can be entered to win tickets to Power Platform Community Conference.Super User Season 2: Coming SoonAll communities moving to the new platform end of July We also honored two different community members during the call, Mohamed Amine Mahmoudi and Markus Franz! We are thankful for both leaders' contributions and engagement with their respective communities. 🎉   Be sure to mark your calendars and register for the meeting on July 11th and stay up to date on all of the changes that are coming. Check out the Super User Forum boards for details.   We're excited to connect with you and continue building a stronger community together.   See you at the call!

Copilot Cookbook Challenge | Week 2 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery:  https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the 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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  @Dhanush 2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a   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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. Kasun_Pathirana1. ManishSolanki2. cloudatica2. madlad3. n/a3. SpongYe4. n/a4. n/a5. n/a5. n/a

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

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 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**

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏 Markus Franz | LinkedIn  Power Apps: mmbr1606  

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form https://aka.ms/PPCCGotPowerSignup by July 12th with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Tuesday Tip | Accepting Solutions

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.   To enhance our collaborative environment, it's important to acknowledge when your question has been answered satisfactorily. Here's a quick guide on how to accept a solution to your questions: Find the Helpful Reply: Navigate to the reply that has effectively answered your question.Accept as Solution: Look for the "Accept as Solution" button or link, usually located at the bottom of the reply.Confirm Your Selection: Clicking this button may prompt you for confirmation. Go ahead and confirm that this is indeed the solution.Acknowledgment: Once accepted, the reply will be highlighted, and the original post will be marked as "Solved". This helps other community members find the same solution quickly. By marking a reply as an accepted solution, you not only thank the person who helped you but also make it easier for others with similar questions to find answers. Let's continue to support each other by recognizing helpful contributions. 

Users online (4,694)