SharePoint List to Multiple Corresponding Channels in Teams.

[Edo1]

Hi,

Previously, I posted a thread on identifying specific content on SharePoint List and then send messages to the respective Channels in Teams where the specific content was identified. Here is the link: https://powerusers.microsoft.com/t5/Building-Flows/Filter-SharePoint-List-to-Specific-Teams-Channel/... . It has since been resolved and the flow is working fine after I inserted int() into Switch thank to @krootz .

Here is the image of the connection that worked: 

The flow above works and assumes that there will only be a single data under the 'Year' column. However this time round, I have multiple data under the 'Year' column like the following:

1. There are multiple Years in the column: 

2. Based on Switch function, when 6, 7 and 8 appear in the SharePoint List, I want it to send messages in Channels 6, 7 and 8. Something like this: 

 However, it's not able to do so and I get the following error: 

In essence, this is what I would like flow to do:

Based on the SharePoint list under Year column, if there are multiple numbers appearing, the flow should send messages to each corresponding Channels in Teams. 

Appreciate advice on how to go about it. 

Thanks! 

[fchopo]

Hello @Edo1 

Before the switch action, you should add an "apply to each" condition, selecting the array item. In this way, it will evaluate all the items in the array, and post messages in each of the channels:

Hope it helps!

Ferran

[Edo1]

Hi @fchopo ,

Thank you for the help. 

I've inserted Initialise Variable before 'Apply to Each'. I've also Inserted 'Apply to Each' as you suggested and then placed the Switch function under it. However, it failed. 

Here's a look at the flow: 

1. The parallel branch is because it is sent to a separate independent channel.

I should also mention that for Year column, there is the possibility for combinations based on the range of 11 individual numbers (1 to 11). Thus, it could be only 6, 7 and 8. Or 1 and 10.  That's why I had to upload a second image to show the output  for 'Apply to Each'.

When I ran the flow, I received the following error: 

Might I add, previously, for the Switch function, I included a Terminate Default action if there is no matching value. but with Apply to Each, I had to remove it. 

Appreciate your continued assistance! 

[fchopo]

Hello @Edo1 

I don't know the reason why when then input value is 6, the flow doesn't go to the "case 6" branch. Could you share what value do you have in each case branch?

Regards,

Ferran

[Edo1]

Hi @fchopo 

Sure. 

Here is a look at the overall flow:

1. 

 Then the branches:

 There are 11 Channels in total. All of them follows the same format.

Thanks!

[fchopo]

Hello @Edo1 

I did a test on my side and it's working on the following way:

 For each year iteration, the switch branches work accordingly.

Please, could you initialize the Year variable like I did (without carriage returns after the "," for each element)?

Hope it helps!

Ferran

[Edo1]

Hi @fchopo 

Thanks. 

Quite a beginner here, what do you mean by carriage return? Does it mean that I should not put it in lines but just merely on a single line [1,2,3]? 

I followed what you did:

However, I'm still getting the error. When I look closer, I realise the error starts on Case 1 and then it stops there. Here is the error:

Here is the column that it is supposed to read: 

Appreciate your help! 

[fchopo · Accepted solution]

Hello @Edo1 

The column suposed to read store the numbers in string format: ["8","6","7"]. I did a test on my side an get the same result as yours, since it is comparing a string value against an integer value. Therefore, I convert those string values to integer ones using the expression 

int(items('apply_to_each'))

Hope it helps!

Ferran

[Edo1]

@fchopo  Thanks for the help. 

My apologies for not getting back yet. Things has been busy on my end with several matters, and I've yet to test it out. Realise that I might need to start it from scratch using a new Form and SharePoint list as I made some changes there as well. For now, I will mark it as the solution. If there's anything further, I will tag you and reply to this thread. 

Thanks again!