This action will calculate a summary of column values of selected items, located in any list of any site collection. You can use the calculated value to update a column of the current item or raise an error when the calculated value does not pass a predefined condition. For example, you can prevent reserving a conference room when there is already a reservation for the same time slot. 


Calculate summary

  1. Site – select a site from the current site collection. Use runtime value to specify site URL only known at run time.
  2. List – select a list from the selected site. Use runtime value to specify list title only known at run time.
  3. Items – enter at least one filter value for selecting target list items for applying the action. To select a single item use the ID column.
  4. Result – either save the value in the current item or evaluate condition to raise an error.
  5. Column – select a column in the source list to get the values from
  6. Operator - when Result is set to Update column, performs summary of values
  7. Column to update – when the result is set to Update, select a column from the current item to update
  8. Condition - appears when Result is set to Raise error. When the summary does not pass the condition, error is raised.
    1. Operation name – operation to perform on the values. You can count, sum, calculate an average; get the maximum and the minimum values. When Result is set to Raise error, you can also specify All to test each item for a positive result or Any to test any item for a positive result.
    2. Operator - depending on the value type of the column, you can use such operands as Equals, Contains, Greater than, Less than and so on.
    3. Comparison value - value to compare the calculation result to
  9. Error – enter error message to be shown when the value does not pass the condition. When setting your action to run synchronously, you can prevent the item from being created/saved if it raises an error.

 

 

Last modified: 3/17/2025 5:04 PM
6 comments[latest: 11/19/2019 9:42 AM]
Ca
Catherine
10/4/2019 11:09 AM
Could this work to limit class registration size? Example: Class A limit to 5, Class B limit to 10? Or is there a better way to do so in Infowise?
VG
Vladi Gubler Infowise
10/4/2019 2:27 PM
Yes, that is exactly what this is used for.
Ca
Catherine
10/7/2019 7:20 AM
Super. Do you have a step-by-step example? Searched the site without success.
VG
Vladi Gubler Infowise
10/7/2019 8:33 AM
You can start with this webinar: https://www.infowisesolutions.com/webinars/details/50
MV
Mikk Välja
11/19/2019 4:37 AM
Hi, im tring to achive exactly the same outcome described here, prevent reserving a room when there is already a reservation for the same time slot. Im following instructions here, but it seems that error is always raised, even when there is no previous reservations in the list. In your example the condition is "ID count equals 0" but i think it cant be right since 0 would indicate that no items were found that conflict with currently set dates, but query is searching for all items that do conflict. Do you have any turtorials where this concept is explained? An example of double room booking prevention would be much appreciated.
VG
Vladi Gubler Infowise
11/19/2019 9:42 AM
The condition is correct. It checks for the desired outcome, which is there are no existing items with overlapping dates. Otherwise, the error is raised.

Add your comment

Comments are not meant for support. If you experiencing an issue, please open a support request.
Microsoft partner logo
© 2005-2025 Infowise Solutions Ltd. All rights reserved.
Privacy | Cookie Policy | Accessibility | Cloud SLA