web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Notify different users...
Power Automate
Unanswered

Notify different users based on their data

(0) ShareShare
ReportReport
Posted on by 71

Hi Community,

I am having a table with 3 columns (Category, Product, Revenue)

Everyday, the responsible of each cateogry has to be notified only by products where revenue equals to a specific amount (ex 1000000)

I have created the following flow but I am still confused whether I am taking the right actions

datalearner_0-1634906710301.png

 

Any suggestion or help would be appreciated. 

 

 

Categories:
I have the same question (0)
  • eliotcole Profile Picture
    4,390 Moderator on at

    Hi, @datalearner , you do not need that condition in your Apply to each flow, because your ODATA Filter query will mean that you already only have those results.

     

    What you might want to consider is to avoid the Apply to each running errors when it has nothing to feed off of.

     

    To do that you would place it in a condition 'Yes' branch, with the condition only running to yes if the number of items in List rows present in a table is greater than 0.

     

    So in the left side of the condition you would use this expression (it might not be /value, but I think it is) :

     

    length(outputs('List_rows_present_in_a_table')?['body/value'])

     

    Then in the right you'd just place the number 0.

  • datalearner Profile Picture
    71 on at

    Hi @eliotcole 

    Since I have filtered the table using the filter query, don't you think it will help avoiding the error case and focus only on rows concerned by the Apply on each row action ?

    In this sample I specified the value, in case I wanted to calculate a value such if revenue - cost > 1000000 where cost could be a fourth column,  would it be solved by Filter query as well ?

     

    Thank you. 

  • eliotcole Profile Picture
    4,390 Moderator on at

    Thanks for the reply, @datalearner !

     

    Regarding your first question, as the flow is currently set up, there will be no errors, because the condition and the filter are doing the exact same thing, so the condition is essentially pointless. That's good, it's an extra action that we can remove. 👍

     

    I'm not sure that I wholly understand your second question, though. However I will try.

     

    If you are already using the ODATA filter to only retrieve rows where the Revenue is 1000000, that will limit what you can do with the data here. For example, if that is already there and you also wish to calculate a value on revenue - cost being over 1000000, that will be logically impossible, I think. Because the initial revenue would need to be greater than 1000000, and the only revenues that you have are exactly 1000000.

     

    Further Suggestions

    I would suggest that in order to get better data, and better access to the data, you either:

    1. More Columns - Add more columns to the table in excel.
    2. Go SharePoint - Move the whole set of data to a SharePoint list (or Microsoft List).

     

    More Columns

    If there is nothing stopping you from editing the original table, then you should add all the data that you might need to work with there.

     

    This will enable you to pass completed information into the flow, and will reduce your flow actions. It will also enable you to visualise the logic more simply in the flow.

     

    If the table itself is sacred, but the workbook can allow additional worksheets, then add another worksheet that has a new table that updating from the original, where you can have all the extra columns that you wish. Then simply run the flow from the new table.

     

    Go SharePoint

    Alternatively, if you consider using a list for this data, then you might find that it is a LOT more flexible in terms of how the information is accessed and manipulated, in addition to making adding extra columns of data, and exporting information to other formats (even Excel!) easily. 🙂

  • datalearner Profile Picture
    71 on at

    Hi @eliotcole 

    I do appreciate your time and I will try clarifying my previous message.

    The initial flow checks for each row whether the product's revenue equals to 1000000, instead, I want to check for each row whether Product's Revenue-1000000 > 0 without calculating that value in an extra column as long as the datasource must only have 3 columns (Category | Product | Revenue).

     

    Thank you in advance. 

  • OliverR-82 Profile Picture
    621 on at

    @datalearner wrote:

    The initial flow checks for each row whether the product's revenue equals to 1000000, instead, I want to check for each row whether Product's Revenue-1000000 > 0 without calculating that value in an extra column as long as the datasource must only have 3 columns (Category | Product | Revenue).


    Hi @datalearner , if I understand correctly that means you want to check if the field Revenue is larger than 1000000 instead of equal to 1000000? Because that's what your calculation would indicate; if you subtract 1000000 from Revenue, is the outcome greater than 0?

     

    If that is the filter you want to apply, then you would just change your OData filter to:

     

    Revenue gt 1000000

     

    Unless I misunderstood your question, of course 🙂

  • datalearner Profile Picture
    71 on at

    Hi @OliverR-82 

    I summarized the scenarios I have by that example Revenue-1000000 > 0  because on the ground I will have to check whether  Revenue-1000000 = 50000 and  Revenue-1000000 = 500000

     

    Thank you in advance.

     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Power Automate

#1
David_MA Profile Picture

David_MA 262 Super User 2026 Season 1

#2
Haque Profile Picture

Haque 227

#3
Expiscornovus Profile Picture

Expiscornovus 225 Most Valuable Professional

Last 30 days Overall leaderboard