Is anyone aware of a change to the 'contains' operator
toLower(outputs('Update_item')?['body/Transferee_x0020_Email'])
We have dozens of other Flows that could potentially be broken because of this change. This is not a question so much as a warning about the latest change. We had to but toLower on both sides of the condition to fix it
This was working for months until a couple days ago when contains was failing due to case sensitivity.
Accepted Solutions
I think I remember that those kinds of fields in Power Automate, when not using an expression, were case insensitive on both sides in the past when I tested. Not just for contains, but equals or anything else in the Condition. I also remember that comparisons between strings such as between two variables, etc. were case insensitive on both sides in the past when I tested and for all variations like "contains", "is equals to", etc.
However, when I tested recently, I noticed that they are now case sensitive at the moment.
Reason I might remember that in past the comparison was case insensitive was because I thought it was something to remember, as I had expected the comparison to be case sensitive. One time, when testing, I was surprised to find that comparisons like the ones you were doing in the condition, were case insensitive by default. For example, comparing SOMETHING to Something, actually returned true and not false to my surprise. Since the comparison was case insensitive I think it was something I made a note of in my mind as a "peculiar behavior" and something to remember about Power Automate. I believe I thought at the time this peculiarity might be there to make it easier on specific kinds of users of Power Automate and was there intentionally, but I noted it as a peculiarity nonetheless.
If the behavior was changed, it would now be operating the way I was expecting it to operate before. However, if a change was indeed made, I could understand your frustration about it relying on the specific behavior. I believe I might have had a habit of putting the toLower and trim type functions anyway all over the place as standard practice in cases where this would vary, despite knowing that the comparisons were case insensitive by default, sort of as if not really sure that they were suppose to be case insensitive in the first place the whole time. If there was actually a change, this habit of mine may have been very much warranted in that event.
I am not exactly sure if there was a change or when there was a change, however, you might be right that before this was case sensitive, I believe that it might have been like that before and you might be on to something here. I am not exactly sure so someone else may have to confirm, all I can say is I do get a case sensitive comparison by default when testing right now as in the below:
I also do not recall if the peculiarity might have been ONLY when using text in the condition clauses themselves with no expression- and not between Dynamic Content of two expression blocks. To my recollection, the above scenario was also case insensitive. However, in case, I also repeated the test with hard coded values in the conditions and made sure of no leading or trailing whitespace. I do get the same result now of "false" as in the above, and I believe in the past, this may have been considered to execute the "true" branch i.e. case insensitive:
I cannot confirm or deny that a change was made. The only thing I might be able to do, is that I relay the above to tell you that I think you might be on to something and some change has been made. I do not know if a change was made or how recent it was made, but it may be definitely something to make a note of in case.
I do not know for sure if anything in the above is true. It's possible there was no change at all or it worked the same before as it does now. I could not tell you for sure.
Case sensitivity is a hyper-specific behavior, but I can imagine many people may have relied on it thinking it was a "user convenience " thing - that is, assuming this is all even true in the first place that something has changed.
The correct course of action is probably to make the change you made on all the Flows which depend on the hyper-specific behavior.
In case this is impractical for you to do and you were relying on the case insensitivity, it is possible that you were not the only one who relied on it. In the case a change was in fact made, even if I had noted it as a peculiarity, if it affected a lot of people, maybe it is better to revert it. This of course all presumes there is any change of any kind in the first place.
I think I remember that those kinds of fields in Power Automate, when not using an expression, were case insensitive on both sides in the past when I tested. Not just for contains, but equals or anything else in the Condition. I also remember that comparisons between strings such as between two variables, etc. were case insensitive on both sides in the past when I tested and for all variations like "contains", "is equals to", etc.
However, when I tested recently, I noticed that they are now case sensitive at the moment.
Reason I might remember that in past the comparison was case insensitive was because I thought it was something to remember, as I had expected the comparison to be case sensitive. One time, when testing, I was surprised to find that comparisons like the ones you were doing in the condition, were case insensitive by default. For example, comparing SOMETHING to Something, actually returned true and not false to my surprise. Since the comparison was case insensitive I think it was something I made a note of in my mind as a "peculiar behavior" and something to remember about Power Automate. I believe I thought at the time this peculiarity might be there to make it easier on specific kinds of users of Power Automate and was there intentionally, but I noted it as a peculiarity nonetheless.
If the behavior was changed, it would now be operating the way I was expecting it to operate before. However, if a change was indeed made, I could understand your frustration about it relying on the specific behavior. I believe I might have had a habit of putting the toLower and trim type functions anyway all over the place as standard practice in cases where this would vary, despite knowing that the comparisons were case insensitive by default, sort of as if not really sure that they were suppose to be case insensitive in the first place the whole time. If there was actually a change, this habit of mine may have been very much warranted in that event.
I am not exactly sure if there was a change or when there was a change, however, you might be right that before this was case sensitive, I believe that it might have been like that before and you might be on to something here. I am not exactly sure so someone else may have to confirm, all I can say is I do get a case sensitive comparison by default when testing right now as in the below:
I also do not recall if the peculiarity might have been ONLY when using text in the condition clauses themselves with no expression- and not between Dynamic Content of two expression blocks. To my recollection, the above scenario was also case insensitive. However, in case, I also repeated the test with hard coded values in the conditions and made sure of no leading or trailing whitespace. I do get the same result now of "false" as in the above, and I believe in the past, this may have been considered to execute the "true" branch i.e. case insensitive:
I cannot confirm or deny that a change was made. The only thing I might be able to do, is that I relay the above to tell you that I think you might be on to something and some change has been made. I do not know if a change was made or how recent it was made, but it may be definitely something to make a note of in case.
I do not know for sure if anything in the above is true. It's possible there was no change at all or it worked the same before as it does now. I could not tell you for sure.
Case sensitivity is a hyper-specific behavior, but I can imagine many people may have relied on it thinking it was a "user convenience " thing - that is, assuming this is all even true in the first place that something has changed.
The correct course of action is probably to make the change you made on all the Flows which depend on the hyper-specific behavior.
In case this is impractical for you to do and you were relying on the case insensitivity, it is possible that you were not the only one who relied on it. In the case a change was in fact made, even if I had noted it as a peculiarity, if it affected a lot of people, maybe it is better to revert it. This of course all presumes there is any change of any kind in the first place.
Helpful resources
Dear Community Members, We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd. During this period, members will not be able to Kudo, Comment, or Reply to any posts. On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities. What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!
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** 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. Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24 17 @Anil_g 7 @ManishSolanki 13 @eetuRobo 5 @David_MA 10 @VishnuReddy1997 5 @SpongYe 9JhonatanOB19932 (tie) @Nived_Nambiar 8 @maltie 2 (tie) @PA-Noob 2 (tie) @LukeMcG 2 (tie) @tgut03 2 (tie) 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. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate @Deenuji 12@ManishSolanki 19 @Anil_g 10 @NathanAlvares24 17 @VishnuReddy1997 6 @Expiscornovus 10 @Tjan 5 @Nived_Nambiar 10 @eetuRobo 3 @SudeepGhatakNZ 8 Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22 Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2 Anil_g2 SharonS2
On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners. The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights. Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.
We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for. We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer. Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together. Here's to new beginnings and endless possibilities! If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport. To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages
