Hi All, I am trying to create a simple way for my committee to vote, by having a sub-item for each exec (Pres, VicePres, Treas, Sec, etc) where they indicate their Approve, Decline or Abstain a request. Then I use a formula sub-item column to output a 1 if the vote is to approve.
In the main item row I use another formula to sum the votes in sub-items and if >3 output “Approved” else “Not Approved”. I want to use this to trigger an automation to send some notifications. With a committee of 7 I only need 4 votes from the voting exec to approve something.
Make sense? I guess there are better ways of doing this and I would like to hear it - probably not by adding marketplace apps - but the standard voting is not precise enough for my purposes.
I think the screen grabs will explain what i’m doing better.
The problem is that when I have 4 Approved votes it is returning “Not Approved”, which seems strange… If I change the formula to “<3” it shows Approved - why am I getting an inverse result here?
So, after lots of playing around with this it appears that the AI thinks the same way I do about what I want to achieve, it just knows the syntax already. But it doesn’t look like Monday can do the calculation that I want.
Rolling up a total from a column or row in sub-items, especially a formula one doesn’t appear to work. It may be able to “count” the rows but not sum the values it seems.
So I’m a bit stuck with this approach to getting approvals from my committee.
I’ll keep looking and check the marketplace further.\
This is an interesting approach to voting I’ve not considered! I think the issue may be coming from the {Subitems#Vote}. When I tried using that variable it returned the names of the subitems instead of the votes. I was able to get it to work as expected by showing a summary of the subitem formula column on the parent item, and using that summary column in the parent formula.
I got this method of voting working beautifully using Formula Automations.
Everyone is assigned a sub-item row to vote as an automation on a status change (validated and ready for exec voting), they are notified and come in to make their decision. The voting status is initially set to “Awaiting decision” and the options are “Approved”, “Declined”, “Abstain”. When the status changes a column called VoteVal is set to 1 only if choice is “Approved”, all other choices yield a “0”. When the status is changed a date/time stamp is added and then the forumula tests when VoteVal>3 (majority) and the main row status is changed to “Approved” and on we go.