https://www.infopathdev.com:443/forums/41.aspxIf you're not sure where to ask your question, ask it here. If necessary, our moderators will make sure it gets classified in the correct board.enCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/82603.aspxWed, 12 Sep 2012 22:15:36 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:82603DC Forms0https://www.infopathdev.com:443/forums/thread/82603.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=82603<p>Rules are run when the form is opened to determine which view is displayed. I could go through and add the same conditions to the validation rules that I use to determine what views are displayed, but it would easier to use separate forms.</p>https://www.infopathdev.com:443/forums/thread/82597.aspxWed, 12 Sep 2012 21:22:14 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:82597Hilary Stoupa0https://www.infopathdev.com:443/forums/thread/82597.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=82597<p>Validation rules are specific to the field - not the view. Thus, you may need a way to know when field 2 is required and add custom validation to the field that takes that into account. You can track view switches with qRules - not sure if you will know what view your user will be in? Or do they click a button or something to get to the second view?</p> <p>In InfoPath, a view is simply a way of displaying data - validation cares only about the data (XML), not the view or controls. Does that make sense?</p>https://www.infopathdev.com:443/forums/thread/82595.aspxWed, 12 Sep 2012 20:59:58 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:82595DC Forms0https://www.infopathdev.com:443/forums/thread/82595.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=82595<p>My form has some simple business logic that determines what view is displayed to users. Depending on the business logic, and hence the view, some fields are displayed and required. I thought that the validation rules were exclusive to the view, but it appears they cross views. I am unsure, because I have seen a behavior where rules appear exclusive to the view in which they are applied. (InfoPath 2010)</p><p>This causes a problem because a field that is required on one view but not a second one prevents the form from being submitted using the second view.</p><p>View A</p><ul><li>Field 1 is displayed and required using a validation rule (the field properties <em>Cannot be blank</em> attribute is unchecked)</li><li>Field 2 is not displayed (because it is&nbsp;not required and not relevant)</li></ul><p>View B</p><ul><li>Field 1 is displayed and required using a validation rule</li><li>Field 2 is displayed and required using a validation rule</li></ul><p>Issue: View A cannot be submitted because no value has been entered for Field 2</p><p>Is this possible, or do I need separate forms?</p>