cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
MrtnM
Post Patron
Post Patron

Why does this condition always go to false?

Building a Flow to add an subscriber to a Mailchimp list. Since the options in the Mailchimp connector are quite basic, I must use a condition to check if an email address is already in the list (because if it is already on the list when I try to add the address, the Flow will show an error).

 

But my condition always goes to false, and I can't understand why.

 

The images show a test Flow using the functionality I want to use. 

fdgsfgdefsgdesfg.png

 

Condition goes to false.

fdsfsdf.png

The Outputs of "Compose Body of Show list members" contains over 3 000 000 characters, but there really is a "gmail" in there somewhere. 

sadsad.png

1 ACCEPTED SOLUTION

Accepted Solutions
srApps
Resolver IV
Resolver IV

When you look at the output of that Compose, what does the very beginning of it look like? Does it start like this:

{
  "users": [
    {
If so, you can change the expression to get "inside" the object.
join(outputs('Compose_Body_of_Show_list_members')?['users'], ',')

View solution in original post

14 REPLIES 14
srApps
Resolver IV
Resolver IV

Think it is resulting in false because it is comparing an array of objects to a string. Does it work if on the left side of the condition you use the join expression:

join(outputs('Compose_Body_of_Show_list_members'), ',')

Thanks! You mean like this?

MrtnM_0-1670399657230.png

Unfortunately, this results in:

"Unable to process template language expressions for action 'Condition' at line '0' and column '0': 'The template language function 'join' expects its first parameter to be an array. The provided value is of type 'Object'. Please see https://aka.ms/logicexpressions#join for usage details.'."

 

So, I guess that means it wasn't an array, but an object, andd that I either will have to make left side of condition into an array before joining, or turn the right side into an object ...?

srApps
Resolver IV
Resolver IV

When you look at the output of that Compose, what does the very beginning of it look like? Does it start like this:

{
  "users": [
    {
If so, you can change the expression to get "inside" the object.
join(outputs('Compose_Body_of_Show_list_members')?['users'], ',')

3 million characters - that's a lot of data.

 

You could always convert your object(s) to a large string by wrapping it into a string expression. So, you would end up checking to see if your 3-million-character string contained the email.

string(outputs('Compose_Body_of_Show_list_members'))

 

Alternatively, as @srApps mentioned, if you had an array within your object that contained user data then you could extract out just the email addresses into an array, then the Condition would work as expected (condition: does the array of email addresses contain the email address).

 


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

I like how there are multiple ways to do it. I just don't think of the simplest way to do it sometimes 😁

That's why I love these forums - I see so many variations of solutions that help me learn every day.

 

In hindsight, I think my suggestion converting everything to a large string is not the best solution. There will still be cases where it will fail. Example: if there was an email called wildbill@gmail, and the check was to see if there was an email called bill@gmail it would return true but doesn't actually contain that exact email.

 

Definitely better to see if array of user data, extract the emails to array, and check if the array contains the exact email.


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

The string should still have the " " characters around the email (it looks like it outputs JSON) so the right side of the condition could have "person@email.com" as what to look for. So I think that should still work as a string.

That did the trick 👍

 

Outputs starts with 

{"members":[{

so the expression 

join(outputs('Compose_Body_of_Show_list_members')?['members'], ',')
works like a charm.
Thanks!
 

 

MrtnM_0-1670427146064.png

 

MrtnM
Post Patron
Post Patron

Solution found by @srApps , kudos to @grantjenkins for ideas and inspiration 😁 

MrtnM
Post Patron
Post Patron

Well ... so I used this in a real life scenario, and of course it didn't work. I post this just for future reference.

 

The "Show list members" Mailchimp action only gets the first (=oldest) 1000 objects in the list, even if you ask it to get a higher number. Reference: MailChimp - Connectors | Microsoft Learn This is plaiun stupid, since there may be a lot more members on a Mailchimp list.

In your Show list members action can you go into Settings and see if it has an option for Pagination. If so, turn it on and add the total number of items you want to return, and it would return the items in batches until it gets all the items, or the number of items you set. If it doesn't have this option, then it might just be a hard limit.

 

See example for the SharePoint Get items action.

grantjenkins_0-1670489632145.png

 


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

Thanks, but no, sadly not possible 😕

 

From https://learn.microsoft.com/en-us/connectors/mailchimp/#show-list-members:

MrtnM_0-1670491225613.png

 

And Settings:

MrtnM_1-1670491277035.png

 

srApps
Resolver IV
Resolver IV

Offset appears to be their way of pagination. Depending on how many "list members" you have you could add additional actions, the 2nd one having an offset of 1000 and maximum results of 1000. If you have a ton of list members it may be better to use a loop with a variable for the offset that increments by 1000 each loop until body?['members'] is empty. It would also be better if that connector allowed you to select which fields to include (like their API allows) so you only get the email address instead of all the other properties of each member.

O, why didn't I think of that (embarrassed). It works 🙂

 

And yes, it certainly would be nice to get just the email addresses. Right now, my Flow needs to look through 7 488 471 characters.

 

Nddmnlös.png

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

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!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

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  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

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.    

Updates to Transitions in the Power Platform Communities

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

Users online (2,129)