Anyone else having problems with flows connected to SP lists or similar.
I have a very simple flow just to locate the problem.
Before I save the flow: (notice the Title column in the condition)
The advanced condition shows : @contains(item()?['Title'], 'test')
Is this correct? Im used to seeing triggerBody() and not Item()?
Anyway the flow is not working.
Am I missing something basic? I tried to replace item with triggerBody.
Any yes the list have an item that has a title containing test. 🙂
In the example given, and since the output from Sharepoint Get Items is an array... will the "Condition" block apply to each array item? Or do we need to use "Filter array" instead, and apply "Filter array output" as the input for "Apply To Each"?
BTW, the bug also happens with Array Filter; i.e. when you implement Recurrence trigger+Sharepoint Get Items+Array Filter.
Yes, this should be fix now.
There was a problem with conditions for multi values which returned from GetItems Action.
The condition should be wrap inside for each.
You should see this flow instead.
(but if you still the old one, would you mind to try to recreate a new one ?)
Hmm seems to be adding a second for each as soon as I select a SP field to be added in either subject or body. And therefore not able to save it. If I drag the condition outside the first for each container, the flow is not taking into account the condition. It runs the action against all items/or none, regardless of the condition? Made a new flow. @kkurni
Check out the on demand sessions that are available now!
ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.
See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.