It's possible to validate using multiple rules together. In this way you can enforce validation only in specific situations. Validation may need to occur only for specific users, at a specific stage in the process or based on the value of another related field. Using compound conditions allows for the development of a specific validation scheme that carefully controls the flow of data and ensures the intended process from users.
In Office 365 the Column Validation settings are accessed through the Infowise Design Screen instead of List Settings as shown in the video.
Infowise provides the ability to configure validation based on multiple rules taking into consideration the dynamic nature of user data and permissions. The flexibility of validation settings allows the process to be carefully controlled so that users don't provide bad data or incomplete data during the process.
9/12/2016 3:59 PM
3 comments [latest: 12/4/2017 2:08 AM]
[11/30/2017 11:00 PM]
Can this be done against a Dynamic Look up value? For example I have a list that looks up some information (unit number) from another list. As part of that list I also pull a value for the type of engine the unit number has. My validation rules don't seem to be working when using that 2nd value as the Conditional Validation. (IE - I shouldn't be able put diesel fuel into a gasoline engine).
[12/4/2017 2:08 AM]
Hi Ross - when it comes to validation, I recommend working within the context of the current list only. Well it may be possible to call for values in other lists using the $GetValue function for example, this adds complexity. It is easier to try to store related validation data in the list being validated. Create additional field(s) and pull the information into the related list records ahead of time so that your validation settings only need to reference field data in the current list. Lookup fields are also quite useful in this regard. It should be possible to create a list specifically for the purpose of reference by lookup fields. The easiest way to validate is to be sure to only give valid options in the first place!
Comments are not designed to replace support calls. If you have a specific issue with one of our products, please send an email to email@example.com
to open a support ticket.