Taming the Elusive “Calculated Column” – Logic – Part 8
The Bigger “Truth” (table)
Now that we’ve looked at how to trace down the logic of an “OR” function and that of an “AND” function, we’re going to merge the two in order to be able to test for multiple conditions together.
The approach we need to take is based on what we already know:
- In order for an employee to be able to receive a paycheck, the must be in the system – in other words, they must be an “Employee”.
- In addition to being an “Employee”, they must also have committed some sort of hours – either through the accumulation of “Regular Hours” (actually working), or through the usage or redemption of “Vacation” or “Sick Leave”.
Notice the specific wording I’ve used in the above list – “…must be and Employee”, “In addition…”, “…either through…or…or…”
I wrote these two items in a specific manner to illustrate that by using plain English to describe the conditions, we can do half the work for ourselves.
Based on these items and how they’re written, we can immediately begin to see what we’ll need to design in our “Truth Table” in order to account for each possible scenario.
In the first item, since I stated that they “must be an Employee”, that would suggest the usage of an “AND” function since in the “AND”, the values must all be “TRUE” regardless of how many there are.
In the second item, it starts out with “In addition to being an Employee” – this would make whatever of the three conditions listed in this item as the second part of the “AND”, and also would suggest that we have three options in which to choose from to pair up with the first half of the “AND” (kind’ve sounds like an “OR” doesn’t it?).
So, we basically just need to list out each of the four pieces of our criteria within the “Truth Table” to give us a set of test data based on the results of the “TRUE/FALSE” values.
In our “Truth Table”, following the exact same model we’ve been using, create your 5 columns (4 conditions and 1 result).

Examining the table, we should see very clearly, that no matter what form of hours was looked at, if they weren’t and employee, the result was always “FALSE”. Along with this, as long as they were indeed an employee, the only time the value resulted in “FALSE” was when there weren’t any hours of any kind. So, it would make sense by this table that any employee who has committed some form of hours (through working, vacation, or sick leave) will get issued a paycheck.
Next time we’ll begin modeling our formula.
- Dessie
Dessie Lunsford
Points-of-Sharing
- Taming the Elusive "Calculated Column"
- EndUserSharePoint.com: Taming the Elusive "Calculated Column" - Customizing a Task List
- EndUserSharePoint.com: Taming the Elusive “Calculated Column” - Customizing a Task List (Part II)
- EndUserSharePoint.com: Taming the Elusive “Calculated Column” - Customizing a Task List (Part III)
- EndUserSharePoint.com: Taming the Elusive “Calculated Column” - Customizing a Task List (Part IV)
- EndUserSharePoint.com: Taming the Elusive “Calculated Column” - Text and Data
- EndUserSharePoint.com: Taming the Elusive "Calculated Column" - Customizing a Contacts List (Part I)
- EndUserSharePoint.com: Taming the Elusive "Calculated Column" - Customizing a Contacts List (Part II-I)
- EndUserSharePoint.com: Taming the Elusive “Calculated Column” - Customizing a Contacts List (Part II-II)
- EndUserSharePoint.com: Taming the Elusive “Calculated Column” - Customizing a Contacts List (Part II-III)
- EndUserSharePoint.com: Taming the Elusive “Calculated Column” – Text and Data (Part III)
- EndUserSharePoint.com: Taming the Elusive “Calculated Column” – Text and Data (Part IV)
- EndUserSharePoint.com: Taming the Elusive “Calculated Column” – Text and Data (Part V)
- EndUserSharePoint.com: Taming the Elusive “Calculated Column” – Text and Data (Part VI)
- Taming the Elusive “Calculated Column” – Lookup and Reference
- Taming the Elusive “Calculated Column” - Logic
- Taming the Elusive “Calculated Column” - Logic - Part 1
- Taming the Elusive “Calculated Column” - Logic - Part 2
- Taming the Elusive “Calculated Column” - Logic - Part 3
- Taming the Elusive “Calculated Column” - Logic - Part 4
- Taming the Elusive “Calculated Column” - Logic - Part 5
- Taming the Elusive “Calculated Column” - Logic - Part 7
- Taming the Elusive “Calculated Column” - Logic - Part 6
- Taming the Elusive “Calculated Column” - Logic - Part 8
- Taming the Elusive “Calculated Column” - Logic - Part 9
- Taming the Elusive “Calculated Column” - Logic - Part 10
- Taming the Elusive “Calculated Column” - Date and Time - Part 1
- Taming the Elusive “Calculated Column” - Date and Time - Part 2
- Taming the Elusive “Calculated Column” - Date and Time - Part 3
- Taming the Elusive “Calculated Column” - Date and Time - Part 4
- Taming the Elusive “Calculated Column” - Referencing Multiple Lines of Text Column
- Taming the Elusive “Calculated Column” – Date and Time – Part 5
- Taming the Elusive “Calculated Column” – Date and Time – Part 6
- Taming the Elusive “Calculated Column” – Date and Time – Part 7
- Taming the Elusive "Calculated Column" - Referencing a Multiple Lines of Text Column With Append Text: Part 1
- Taming the Elusive "Calculated Column" - Referencing a Multiple Lines of Text Column With Append Text: Part 2
- Taming the Elusive "Calculated Column" - Referencing a Multiple Lines of Text Column With Append Text: Part 3