cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
eliotcole
Super User
Super User

String Ends With A Pattern

Hi,

 

I realise I'm probably just being monumentally stupid, but:

 

My Problem

I have a text field in an array of data, and I need to confirm that it ends with:
(AAA######)

Where each "A" is a capital letter, and each "#" is a number 0-9.

 

The Reason

I need to do this with as little hassle as possible because it needs to be done on potentially hundreds of entries. The reason for it is to be used in a Filter connector to lessen the amount of entries that I'll be performing For Each actions on. Basically, anything ending in that, won't be processed.

 

---

Additional Info (you don't need to know)

That's all I need to do, and I'm not creating an account with or giving data to Plumsail for their Regex connector. If their connector doesn't require an account, and passes no data to Plumsail, then cool, I'm in. 😅

 

If it is there, it will always be eleven characters long, starting with an open bracket, and ending with a closed bracket, as above.

 

If I were to guess at the RegEx for the letters and numbers it might be the following, but I'm not really au-fait with it:

([A-Z]{3})([0-9]{6})

 

Any help would be really well received!

 

-----

What I've Tried

I've tried using either of these, and neither worked, because I don't think there's support for any of the syntax used:

  • endsWith(!MatchAll(triggerBody()['text'], "(([A-Z]{3})([0-9]{6}))"))
  • endsWith(!MatchAll(triggerBody()['text'], Letter & Letter & Letter & Digit & Digit & Digit & Digit & Digit & Digit))
1 ACCEPTED SOLUTION

Accepted Solutions
eliotcole
Super User
Super User

Even though I'm sure that there's no swift way of doing this here, I thought I'd come back and show the logic that I've used to affect a similar result.

 

I'm now resigned to the fact that I'm going to have to process each one in an 'Apply to each' connector run, it's a shame, but thems the breaks. Also, in an effort to avoid Condition actions which would work just fine, I'm introducing Integer Traps.

 

Still, if I'm going down that route, I can at least ensure that I process it as simply as possible.

 

What I've done here, is to map out using a few flow variables what I'll be subsuming into a single (large) expression once I have got to the end.

 

Separately, I've also found another source of information to confirm what this end of these strings, which is a more sure method of confirming that data. However the logic below would still work here, too. The key is to assume that I have isolated the data I need to analyse.

 

So ... this doesn't quite answer the question, but it gets me most of the way there ... ... anyway ... forward!

 

----

 

So, each of these codes needs to:

  1. Be 9 characters long.
  2. Start with a 3 character string of letters that is a month.
  3. Finish with a 6 character set of numbers.

It was realising that the 6 numbers would be an integer every time that got me set right here.

 

I'll work with one item for this example, and without the brackets.

Integer Traps FlowInteger Traps Flow

 

You may notice a dependence on what I call "Integer Traps" here. Essentially, these will mirror any failures to create what is needed in a full expression, but they're really useful if you are running out of layers in your flow due to many scopes, conditions, loops, etc. I'm sure I'm not the first to use them, and hopefully I'll not be the last.

 

My Integer Traps are basically; if a particular condition is true, you will create an integer (useful in this case!), if it is false, you try to make an integer out of the word "ERROR", which will fail. You then run a success branch for if it makes the integer, and a failure branch if it doesn't. On the failure branch you 'Configure run after' to only run on failure.

 

Always ensure that you 'close' an integer trap, though. Usually by making the closing action run after all possibilities from all previous branches. In this case, though, it wasn't required.

 

-----

 

On to the logic ... and up front there is the month and monthsVAR (an array of months):

substring(variables('input'), 0, 3)substring(variables('input'), 0, 3)

 

[ "JAN", "FEB", "MAR", "APR", "MAY", "JUN", "JUL", "AUG", "SEP", "OCT", NOV", "DEC" ][ "JAN", "FEB", "MAR", "APR", "MAY", "JUN", "JUL", "AUG", "SEP", "OCT", NOV", "DEC" ]

 

These are going to be used to ensure that the first three characters are the right format.

 

The first integer trap that's here will be counting the length of the input, and only allowing the flow to continue if the length is exactly 9 characters long.

if(equals(int(length(variables('input'))), 9), 9, 'ERROR')if(equals(int(length(variables('input'))), 9), 9, 'ERROR')

 

You can see here that there is a true/false check on whether the length is 9, then if it is, the value is set to 9, if not, the value is set to 'ERROR'. If I get the 9 that I want, then I will just run a quick check on that 3 character month format:

and(contains(variables('monthsVAR'), substring(variables('input'), 0, 3)), equals(variables('length'), 9))and(contains(variables('monthsVAR'), substring(variables('input'), 0, 3)), equals(variables('length'), 9))

 

Breaking down the conditions in the 'and' logical expression (all conditions must be true) that is in the Success branch of integer trap 1:

  • The 'contains' logical check will loop through the monthsVAR array to see if those first 3 characters match one of the entries there, and if it does, it presents a 'true' value.
  • The 'equals' check feels redundant as it is performed in the previous step, but it feeds a boolean to the and upon whether the length is 9 or not.

 

Since I am setting an Integer variable to 'ERROR' upon a false statement, this would normally cause the flow to fail, so I need to have a branch to allow things to progress despite that. My Compose action does that.

Configure run afterConfigure run after

 

All that is done here is is click the menu and select 'Configure run after':

Select 'Configure run after'Select 'Configure run after'

 

Then select only the option "has failed":

has failedhas failed

 

This branch will now only run if the integer creation fails.

 

Great. Now on to handling the next check, the last 6 characters being all numbers. Luckily, if they are all numbers, then they will convert in to an integer perfectly. So, I get to use an integer trap ... to trap some integers!

if(variables('allOk'), int(substring(variables('input'), 3)), 'ERROR')if(variables('allOk'), int(substring(variables('input'), 3)), 'ERROR')

 

However, it's very important here (as mentioned above) to close the previous integer trap. So whilst that would usually involve me ensuring that I have action run *whatever* happens in either the success or failure branches previously (check all items on each - you'd have to go in twice) ... here, I actually want THIS branch to be skipped if the failure branch runs. So here I will *only* allow the 'Initialize int' action to go if:

  1. It can 'run after' the allOk branch "is successful."
  2. It can 'run after' the failure branch "is skipped."

 

allOk is successful OR Compose is skippedallOk is successful OR Compose is skipped

 

So, now, that will either leave me with a successful code to use wherever, or, it won't run, because the previous error branch was successful, and so this branch will be skipped.

 

All that leaves me to do in order to progress forward is to manage the success and failure branches of this particular action.

 

Here, in this example flow it's the end, and I have Success/Failure branches set.

 

However in a longer flow, I would probably append the successfully managed code to a new array, or on failure, do nothing, then have a nonsense Compose action to close the success/failure branches and run on all eventualities of both branches. Which (in an 'Apply to each' loop) would then mean it can move on to the next item.

 

------

 

That's it, basically. With the added bonus of with a tiny bit of tweaking, this can all be hearded into one MASSIVE expression - which I'll edit in once I've tested it! 😅

 

EDIT 1 - OK, here is that whole flow as one expression, assuming that there is still the 'input' variable.

if(and(contains(variables('monthsVAR'), substring(variables('input'), 0, 3)), equals(length(variables('input')), 9)), int(substring(variables('input'), 3)), 'ERROR')

Obviously that's great because it's down to 3 steps (months variable), but you could make it two by replacing the month variable with:

json('["JAN","FEB","MAR","APR","MAY","JUN","JUL","AUG","SEP","OCT","NOV","DEC"]')

The important question to ask here is whether this is too complex for someone without this knowledge to parse in the future. The reason we're all here is to have easy access to this stuff, and that's dangerously 'codey'. 😉

 

Either way, edit two will have it in one step. 😅

EDIT 2 - One step - Since I'll be handling the input of a 'Apply to each' action, I can use item() to refer to the current item. The current item in this case is a pre-sorted, tab separated, line of information. Of which we only need the first piece. So:

if(and(contains(json('["JAN","FEB","MAR","APR","MAY","JUN","JUL","AUG","SEP","OCT","NOV","DEC"]'), substring(trim(first(split(item(), uriComponentToString('%09')))), 0, 3)), equals(length(trim(first(split(item(), uriComponentToString('%09'))))), 9)), int(substring(trim(first(split(item(), uriComponentToString('%09')))), 3)), 'ERROR')

It's basically some excel monkey's wet dream, though now. Which is the reason we're here to avoid this stuff. 😏

 

 

It's not an answer, but it's how I'm managing this for now.

 

((( If I was going to manage each integer separately, I'd use a similar method to the months. )))

View solution in original post

5 REPLIES 5
Paulie78
Super User
Super User

I wrote a blog post on how to do Regex in Power Automate:

https://www.tachytelic.net/2021/04/power-automate-regex/

But although it can do what you want I don’t think it will be any good for you as Office Scripts are limited to 200 runs per day. Unless you can modify it so you can do all the entries in one batch.

eliotcole
Super User
Super User

Hi, Paulie

 

I think I might've seen that in my (seemingly extensive) searches on the matter.

 

The issue is that I think it's a little too intensive for the desired functionality, and I'm not particularly keen on doing it via another application.

 

Also, heh, as you say, there's the upper limit of those scripts.

 

If I wanted to I suppose I could put it all into an excel sheet, and do it all there, but that's defeating the purpose, for me. I'd really like to try to get this done simply.

 

I'm building expression logic now, but it feels like it'd be rather painful in the end. 😏

 

Thanks, though, mate. 👍

 

E

 

Paulie78
Super User
Super User

If you could get every entry into an array, the office script could pass you back all the processed entries in one action.

Thanks, they actually already are in an array.

 

So whilst it's a good suggestion, I'd rather process within the flow ... Cheers, Paulie! 🙂

eliotcole
Super User
Super User

Even though I'm sure that there's no swift way of doing this here, I thought I'd come back and show the logic that I've used to affect a similar result.

 

I'm now resigned to the fact that I'm going to have to process each one in an 'Apply to each' connector run, it's a shame, but thems the breaks. Also, in an effort to avoid Condition actions which would work just fine, I'm introducing Integer Traps.

 

Still, if I'm going down that route, I can at least ensure that I process it as simply as possible.

 

What I've done here, is to map out using a few flow variables what I'll be subsuming into a single (large) expression once I have got to the end.

 

Separately, I've also found another source of information to confirm what this end of these strings, which is a more sure method of confirming that data. However the logic below would still work here, too. The key is to assume that I have isolated the data I need to analyse.

 

So ... this doesn't quite answer the question, but it gets me most of the way there ... ... anyway ... forward!

 

----

 

So, each of these codes needs to:

  1. Be 9 characters long.
  2. Start with a 3 character string of letters that is a month.
  3. Finish with a 6 character set of numbers.

It was realising that the 6 numbers would be an integer every time that got me set right here.

 

I'll work with one item for this example, and without the brackets.

Integer Traps FlowInteger Traps Flow

 

You may notice a dependence on what I call "Integer Traps" here. Essentially, these will mirror any failures to create what is needed in a full expression, but they're really useful if you are running out of layers in your flow due to many scopes, conditions, loops, etc. I'm sure I'm not the first to use them, and hopefully I'll not be the last.

 

My Integer Traps are basically; if a particular condition is true, you will create an integer (useful in this case!), if it is false, you try to make an integer out of the word "ERROR", which will fail. You then run a success branch for if it makes the integer, and a failure branch if it doesn't. On the failure branch you 'Configure run after' to only run on failure.

 

Always ensure that you 'close' an integer trap, though. Usually by making the closing action run after all possibilities from all previous branches. In this case, though, it wasn't required.

 

-----

 

On to the logic ... and up front there is the month and monthsVAR (an array of months):

substring(variables('input'), 0, 3)substring(variables('input'), 0, 3)

 

[ "JAN", "FEB", "MAR", "APR", "MAY", "JUN", "JUL", "AUG", "SEP", "OCT", NOV", "DEC" ][ "JAN", "FEB", "MAR", "APR", "MAY", "JUN", "JUL", "AUG", "SEP", "OCT", NOV", "DEC" ]

 

These are going to be used to ensure that the first three characters are the right format.

 

The first integer trap that's here will be counting the length of the input, and only allowing the flow to continue if the length is exactly 9 characters long.

if(equals(int(length(variables('input'))), 9), 9, 'ERROR')if(equals(int(length(variables('input'))), 9), 9, 'ERROR')

 

You can see here that there is a true/false check on whether the length is 9, then if it is, the value is set to 9, if not, the value is set to 'ERROR'. If I get the 9 that I want, then I will just run a quick check on that 3 character month format:

and(contains(variables('monthsVAR'), substring(variables('input'), 0, 3)), equals(variables('length'), 9))and(contains(variables('monthsVAR'), substring(variables('input'), 0, 3)), equals(variables('length'), 9))

 

Breaking down the conditions in the 'and' logical expression (all conditions must be true) that is in the Success branch of integer trap 1:

  • The 'contains' logical check will loop through the monthsVAR array to see if those first 3 characters match one of the entries there, and if it does, it presents a 'true' value.
  • The 'equals' check feels redundant as it is performed in the previous step, but it feeds a boolean to the and upon whether the length is 9 or not.

 

Since I am setting an Integer variable to 'ERROR' upon a false statement, this would normally cause the flow to fail, so I need to have a branch to allow things to progress despite that. My Compose action does that.

Configure run afterConfigure run after

 

All that is done here is is click the menu and select 'Configure run after':

Select 'Configure run after'Select 'Configure run after'

 

Then select only the option "has failed":

has failedhas failed

 

This branch will now only run if the integer creation fails.

 

Great. Now on to handling the next check, the last 6 characters being all numbers. Luckily, if they are all numbers, then they will convert in to an integer perfectly. So, I get to use an integer trap ... to trap some integers!

if(variables('allOk'), int(substring(variables('input'), 3)), 'ERROR')if(variables('allOk'), int(substring(variables('input'), 3)), 'ERROR')

 

However, it's very important here (as mentioned above) to close the previous integer trap. So whilst that would usually involve me ensuring that I have action run *whatever* happens in either the success or failure branches previously (check all items on each - you'd have to go in twice) ... here, I actually want THIS branch to be skipped if the failure branch runs. So here I will *only* allow the 'Initialize int' action to go if:

  1. It can 'run after' the allOk branch "is successful."
  2. It can 'run after' the failure branch "is skipped."

 

allOk is successful OR Compose is skippedallOk is successful OR Compose is skipped

 

So, now, that will either leave me with a successful code to use wherever, or, it won't run, because the previous error branch was successful, and so this branch will be skipped.

 

All that leaves me to do in order to progress forward is to manage the success and failure branches of this particular action.

 

Here, in this example flow it's the end, and I have Success/Failure branches set.

 

However in a longer flow, I would probably append the successfully managed code to a new array, or on failure, do nothing, then have a nonsense Compose action to close the success/failure branches and run on all eventualities of both branches. Which (in an 'Apply to each' loop) would then mean it can move on to the next item.

 

------

 

That's it, basically. With the added bonus of with a tiny bit of tweaking, this can all be hearded into one MASSIVE expression - which I'll edit in once I've tested it! 😅

 

EDIT 1 - OK, here is that whole flow as one expression, assuming that there is still the 'input' variable.

if(and(contains(variables('monthsVAR'), substring(variables('input'), 0, 3)), equals(length(variables('input')), 9)), int(substring(variables('input'), 3)), 'ERROR')

Obviously that's great because it's down to 3 steps (months variable), but you could make it two by replacing the month variable with:

json('["JAN","FEB","MAR","APR","MAY","JUN","JUL","AUG","SEP","OCT","NOV","DEC"]')

The important question to ask here is whether this is too complex for someone without this knowledge to parse in the future. The reason we're all here is to have easy access to this stuff, and that's dangerously 'codey'. 😉

 

Either way, edit two will have it in one step. 😅

EDIT 2 - One step - Since I'll be handling the input of a 'Apply to each' action, I can use item() to refer to the current item. The current item in this case is a pre-sorted, tab separated, line of information. Of which we only need the first piece. So:

if(and(contains(json('["JAN","FEB","MAR","APR","MAY","JUN","JUL","AUG","SEP","OCT","NOV","DEC"]'), substring(trim(first(split(item(), uriComponentToString('%09')))), 0, 3)), equals(length(trim(first(split(item(), uriComponentToString('%09'))))), 9)), int(substring(trim(first(split(item(), uriComponentToString('%09')))), 3)), 'ERROR')

It's basically some excel monkey's wet dream, though now. Which is the reason we're here to avoid this stuff. 😏

 

 

It's not an answer, but it's how I'm managing this for now.

 

((( If I was going to manage each integer separately, I'd use a similar method to the months. )))

Helpful resources

Announcements

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  

Copilot Cookbook Challenge | Week 1 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

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. 

Reminder: To register for the Community Ambassador Call on June 13th

Calling all Super Users & User Group Leaders   Reminder: To register for the Community Ambassador Call on June 13th—for an exclusive event for User Group Leaders and Super Users! This month is packed with exciting updates and activities within our community.   What's Happening: Community Updates: We'll share the latest developments and what's new in our vibrant community.Special Guest Speaker: Get ready for an insightful talk and live demo of Microsoft Copilot Studio templates by our special guest.Regular Updates: Stay informed with our routine updates for User Groups and Super Users.Community Insights: We'll provide general information about ongoing and upcoming community initiatives. Don't Miss Out: Register Now: Choose the session that fits your schedule best.Check your private messages or Super User Forum for registration links. We're excited to connect with you and continue building a stronger community together.   See you at the call!  

Users online (2,898)