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:
This is the section i want to extract information from:
In particular i want 2 bits of info from the Value output:
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
Accepted Solutions
You can try something like this:
Presuming an input somewhat like this:
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.
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:
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:
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'),':')
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:
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!
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:
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.
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:
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:
And a 1,000 foot view of what's in just the Apply to Each (with the Switch collapsed / folded in):
Check if it helps @david_ashworth
You can try something like this:
Presuming an input somewhat like this:
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.
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:
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:
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'),':')
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:
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!
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:
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.
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:
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:
And a 1,000 foot view of what's in just the Apply to Each (with the Switch collapsed / folded in):
Check if it helps @david_ashworth
Helpful resources
A new month means it's time to celebrate and welcome the new user groups that have joined our community. We are excited to announce that we have more than 8 New Groups, which is no surprise after the amazing Microsoft Power Platform Conference. This month, we are breaking them out by the different community categories. If your group is listed here, give this post a kudo so we can celebrate with you! Don't forget to take a look at the many events happening near you or virtually! It's a great time of year to connect and engage with User Groups both locally and online. Please Welcome Our NEW User Groups Power Platform: PowerIT User Group: Nottingham Power Platform User Group: Bergen Power Platform User Group: Danmark Nashville Power Platform User Group Microsoft Ambassador Program y Mujer Latina Technolochicas NCWIT Community Copilot Studio: Copilot User Group Italia Dynamics365: Dynamics User Group AdriaticDynamic 365 Azerbaijan December User Group Events 01 Dec 2023 Aprendiendo Desarrollo web, creando mi primer power app y power page. 01 Dec 2023 Q4 Hybrid Philadelphia Dynamics 365 & Power Platform User Group Meeting05 Dec 2023APAC Dynamics 365 FastTrack Bootcamp - BI and Analytics07 Dec 2023Bay Area Power Platform Meetup: Learn, Share, and Connect07 Dec 2023Indiana D365/AX December User Group Meeting07 Dec 2023Dynamics User Group Meeting: Houston09 Dec 2023 December '23 - NEW Power Apps User Group Meeting - Online 12 Dec 2023December Cleveland Power Platform User Group Meeting12 Dec 2023 RW2 Data Stewardship Open Forum Discussion 13 Dec 2023 Black Country Power Platform User Group - December 2023 - West Midlands
Our ongoing BACK TO BASICS: TUESDAY TIP series dedicated to helping both new members and seasoned veterans of our community learn and grow reached a milestone ten posts! We're excited to present this "one stop" post for each of our #TuesdayTips, making it easier to find what you're looking for and help you understand the community: from ranking and badges to profile avatars, from being a Super User to blogging in the community, and so much more. Thank you for your incredible support for this series--we are so glad it was able to help so many of you navigate your community experience. Back to Basics Tuesday Tip #1: All About Your Community Account Find out the basics of your community account. Whether it's changing your username, updating an email address, understanding GDPR, or customizing your profile, this is the place to begin. ○ Power Apps ○ Power Automate ○ Power Pages ○ Copilot Studio Back to Basics Tuesday Tip #2: All About Community Ranks Have you ever wondered how your fellow community members earn the different ranks available? What is the difference between an Advocate and a Helper, a Solution Sage and a Community Champion? In this #TuesdayTip, we share the secrets and tips to help YOU keep your ranking growing--and why it's so important to our communities. ○ Power Apps ○ Power Automate ○ Power Pages ○ Copilot Studio Back to Basics Tuesday Tip #3: Contributing to the Community If you need to understand how subscriptions or notifications work, how to use search to find the answers you're looking for, or editing your posts, this is the place to start. With these handy tips, you'll find what you're looking for, ask some great questions, and format your posts perfectly! ○ Power Apps ○ Power Automate ○ Power Pages ○ Copilot Studio Back to Basics Tuesday Tip #4: What is a Super User? Have you ever been exploring the community and come across a user with this unique icon next to their name? It means you have found the actual, real-life superheroes of the Power Platform Community! Super Users are our heroes because of the way they are consistently helpful with everything from solutions to flagging spam, offering insight on the community, and so much more! Find out more in this #TuesdayTip. ○ Power Apps ○ Power Automate ○ Power Pages ○ Copilot Studio Back to Basics Tuesday Tip #5: How to Become a Community Blog Author We want YOU to be part of the community blog! Sharing your knowledge of Power Platform is an essential part of our community! By sharing what you know and have learned with the community in the Power Platform in the community blog, you help us create a more engaged and informed community, better equipped to tackle complex challenges. To get started with blogging across the Power Platform communities, please visit the following links. ○ Power Apps ○ Power Automate ○ Power Pages ○ Copilot Studio Back to Basics Tuesday Tip #6 All About Community User Groups Being part of, starting, or leading a User Group can have many great benefits for our community members who want to learn, share, and connect with others who are interested in the Microsoft Power Platform and the low-code revolution. Don't wait. Get involved with (or maybe even start) a User Group today--just follow the tips below to get started. ○ Power Apps ○ Power Automate ○ Power Pages ○ Copilot Studio Back to Basics Tuesday Tip #7: Resources for User Groups Once you've launched your Community User Group, we are excited to have many resources available that can help you lead, engage, and grow your User Group! Whether it's access to the Microsoft Community Tenant for User Groups, help with finding speakers for your User Group meetings (both local and virtual speakers), and even finding spaces to have your meetings in--check out this #TuesdayTip to get what you need! ○ Power Apps ○ Power Automate ○ Power Pages ○ Copilot Studio Back to Basics Tuesday Tip #8: All About Subscriptions and Notifications Keeping track of what you want to know and how you want to find out about it may seem confusing. This #TuesdayTip is all about your community profile's subscriptions and notifications settings. Check out the links below for clear directions and how-to's. ○ Power Apps ○ Power Automate ○ Power Pages ○ Copilot Studio Back to Basics Tuesday Tip #9: All About the Community Galleries Have you checked out the library of content in our galleries? Whether you're looking for the latest info on an upcoming event, a helpful webinar, or tips and tricks from some of our most experienced community members, our galleries are full of the latest and greatest video content for the Power Platform communities. Find out more by following the links below. ○ Power Apps ○ Power Automate ○ Power Pages ○ Copilot Studio Back to Basics Tuesday Tip #10: Community Support Whether you're a seasoned community veteran or just getting started, you may need a bit of help from time to time! If you need to share feedback with the Community Engagement team about the community or are looking for ways we can assist you with user groups, events, or something else, Community Support is the place to start. Community Support is part of every one of our communities, accessible to all our community members, so find out what it means for your community with our last #TuesdayTip. ○ Power Apps ○ Power Automate ○ Power Pages ○ Copilot Studio Thank you for your support for our #TuesdayTip series. We look forward to bringing you more tips and tricks to help make your community experience the best it can be!
Welcome to our November Newsletter, where we highlight the latest news, product releases, upcoming events, and the amazing work of our outstanding Community members. If you're new to the Community, please make sure to follow the latest News & Announcements and check out the Community on LinkedIn as well! It's the best way to stay up-to-date with all the news from across the Power Platform and beyond. This month's highlights:- - Our most active community members- Microsoft Power Up Program- Microsoft Community Days website - The latest blogs and more COMMUNITY HIGHLIGHTS Check out the most active community members of the last month. These hardworking members are posting regularly, answering questions, kudos, and providing top solutions in their communities. We are so thankful for each of you--keep up the great work! If you hope to see your name here next month, just get active! FLMikePstork1Nived_NambiarWarrenBelzSprongYeManishSolankiLaurensMwskinnermlcAgniusExpiscornovuscreativeopinion KatieAUinzil2kHaressh2728hafizsultan242douicmccaughanwoLucas001domliu Power Up Program Click the image below to discover more about the amazing Microsoft Power Up Program, as Reem Omar, Abbas Godhrawala, Chahine Atallah, Ruby Ruiz Brown, Juan Francisco Sánchez Enciso, Joscelyne Andrade Arévalo, Eric G. and Paulina Pałczyńska share how non-tech professionals can successfully advance into a new career path using Microsoft #PowerPlatform. To find out more about this amazing initiative, click here to apply for the program and reboot your journey into low-code app development today! Community Days - Event Website Have you checked out the Community Days website yet? Dedicated to the volunteer community organizers around the world, Community Days is the perfect place to find an event near you or add an event for wider exposure. Many thanks to Thomas Daly, Sharon Weaver, Sedat Tum, Jonathan Weaver, Manpreet Singh, David Leveille, Jason Rivera, Mike Maadarani, Rob Windsor and the team for all their hard work. Anyone can host a Community Day on any topic relevant to our industry, just click the image below to find out more. EVENT NEWS Power Platform French Summit - Paris/Virtual - 6-7th Dec It's not long now until the Power Platform French Summit, which takes place both virtually and in-person at the Microsoft France conference center in Paris on 6-7th December 2023. If you can't make it in-person, all sessions will also be broadcast on virtual networks for better distribution and accessibility. There's a fantastic array of speakers, including Jérémy LAPLAINE, Amira Beldjilali, Rémi Chambard, Erika Beaumier, Makenson Frena, Assia Boutera, Elliott Pierret, Clothilde Facon, Gilles Pommier, Marie Aubert, Antoine Herbosa, Chloé Moreau, Raphaël Senis, Rym Ben Hamida, Loïc Cimon, Joséphine Salafia, David Zoonekyndt, Aïcha Charpentier, Henry Jammes, Milene Rochard, Mehdi EL YASSIR, and many more. Click the image below for more information. LATEST COMMUNITY BLOG ARTICLES Power Apps Community Blog Power Automate Community Blog Copilot Community Blog Power Pages Community Blog
This is the TENTH post in our ongoing series dedicated to helping the amazing members of our community--both new members and seasoned veterans--learn and grow in how to best engage in the community! Each Tuesday, we feature new content that will help you best understand the community--from ranking and badges to profile avatars, from Super Users to blogging in the community. Our hope is that this information will help each of our community members grow in their experience with Power Platform, with the community, and with each other! This Week: All About Community Support Whether you're a seasoned community veteran or just getting started, you may need a bit of help from time to time! If you need to share feedback with the Community Engagement team about the community or are looking for ways we can assist you with user groups, events, or something else, Community Support is the place to start. Community Support is part of every one of our communities, accessible to all our community members. Power Apps: https://powerusers.microsoft.com/t5/Community-Support/ct-p/pa_community_support Power Automate: https://powerusers.microsoft.com/t5/Community-Support/ct-p/mpa_community_support Power Pages: https://powerusers.microsoft.com/t5/Community-Support/ct-p/mpp_community_support Copilot Studio: https://powerusers.microsoft.com/t5/Community-Support/ct-p/pva_community-support Within each community's Community Support page, you'll find three distinct areas, each with a different focus to help you when you need support from us most. Community Accounts & Registration is the go-to source for any and all information related to your account here in the community. It's full of great knowledge base articles that will help you manage your community account and know what steps to take if you wish to close your account. ● Power Apps ● Power Automate ● Power Pages, ● Copilot Studio Using the Community is your source for assistance with everything from Community User Groups to FAQ's and more. If you want to know what kudos are, how badges work, how to level up your User Group or something else, you will probably find the answers here. ● Power Apps ● Power Automate ● Power Pages ● Copilot Studio Community Feedback is where you can share opportunities, concerns, or get information from the Community Engagement team. It's your best place to post a question about an issue you're having in the community, a general question you need answered. Whatever it is, visit Community Feedback to get the answers you need right away. Our team is honored to partner with you and can't wait to help you! ● Power Apps ● Power Automate ● Power Pages ● Copilot Studio
What an amazing event we had this year, as Microsoft showcased the latest advancements in how AI has the potential to reshape how customers, partners and developers strategize the future of work. Check out below some of our handpicked videos and Ignite announcements to see how Microsoft is driving real change for users and businesses across the globe. Video Highlights Click the image below to check out a selection of Ignite 2023 videos, including the "Microsoft Cloud in the era of AI" keynote from Scott Guthrie, Charles Lamanna, Arun Ulag, Sarah Bird, Rani Borkar, Eric Boyd, Erin Chapple, Ali Ghodsi, and Seth Juarez. There's also a great breakdown of the amazing Microsoft Copilot Studio with Omar Aftab, Gary Pretty, and Kendra Springer, plus exciting sessions from Rajesh Jha, Jared Spataro, Ryan Jones, Zohar Raz, and many more. Blog Announcements Microsoft Copilot presents an opportunity to reimagine the way we work—turning natural language into the most powerful productivity tool on the planet. With AI, organizations can unearth value in data across productivity tools like business applications and Microsoft 365. Click the link below to find out more. Check out the latest features in Microsoft Power Apps that will help developers create AI-infused apps faster, give administrators more control over managing thousands of Microsoft Power Platform makers at scale, and deliver better experiences to users around the world. Click the image below to find out more. Click below to discover new ways to orchestrate business processes across your organization with Copilot in Power Automate. With its user-friendly interface that offers hundreds of prebuilt drag-and-drop actions, more customers have been able to benefit from the power of automation. Discover how Microsoft Power Platform and Microsoft Dataverse are activating the strength of your enterprise data using AI, the announcement of “plugins for Microsoft Copilot for Microsoft 365”, plus two new Power Apps creator experiences using Excel and natural language. Click below to find out more about the general availability of Microsoft Fabric and the public preview of Copilot in Microsoft Fabric. With the launch of these next-generation analytics tools, you can empower your data teams to easily scale the demand on your growing business. And for the rest of all the good stuff, click the link below to visit the Microsoft Ignite 2023 "Book of News", with over ONE HUNDRED announcements across infrastructure, data, security, new tools, AI, and everything else in-between!
This is the ninth post in our series dedicated to helping the amazing members of our community--both new members and seasoned veterans--learn and grow in how to best engage in the community! Each Tuesday, we feature new content that will help you best understand the community--from ranking and badges to profile avatars, from Super Users to blogging in the community. Our hope is that this information will help each of our community members grow in their experience with Power Platform, with the community, and with each other! Today's Tip: All About the Galleries Have you checked out the library of content in our galleries? Whether you're looking for the latest info on an upcoming event, a helpful webinar, or tips and tricks from some of our most experienced community members, our galleries are full of the latest and greatest video content for the Power Platform communities. There are several different galleries in each community, but we recommend checking these out first: Community Connections & How-To Videos Hosted by members of the Power Platform Community Engagement Team and featuring community members from around the world, these helpful videos are a great way to "kick the tires" of Power Platform and find out more about your fellow community members! Check them out in Power Apps, Power Automate, Power Pages, and Copilot Studio! Webinars & Video Gallery Each community has its own unique webinars and videos highlighting some of the great work being done across the Power Platform. Watch tutorials and demos by Microsoft staff, partners, and community gurus! Check them out: Power Apps Webinars & Video Gallery Power Automate Webinars & Video Gallery Power Pages Webinars & Video Gallery Copilot Studio Webinars & Video Gallery Events Whether it's the excitement of the Microsoft Power Platform Conference, a local event near you, or one of the many other in-person and virtual connection opportunities around the world, this is the place to find out more about all the Power Platform-centered events. Power Apps Events Power Automate Events Power Pages Events Copilot Studio Events Unique Galleries to Each Community Because each area of Power Platform has its own unique features and benefits, there are areas of the galleries dedicated specifically to videos about that product. Whether it's Power Apps samples from the community or the Power Automate Cookbook highlighting unique flows, the Bot Sharing Gallery in Copilot Studio or Front-End Code Samples in Power Pages, there's a gallery for you! Check out each community's gallery today! Power Apps Gallery Power Automate Gallery Power Pages Gallery Copilot Studio Gallery
