https://www.infopathdev.com:443/forums/45.aspxenCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/14302.aspxSat, 18 Feb 2006 09:13:43 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:14302Agni Jonnalagadda0https://www.infopathdev.com:443/forums/thread/14302.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=45&PostID=14302Hi Sam, <br />Welcome to the Forum!<br />I think View switch happens only after the control is passed to the InfoPath.<br />Call XDocument.SetNamedNodeProperty in "OnSwitchView()" event, then it should work.<br /><br /><br />Agni<br />INFOPATHdev Indiahttps://www.infopathdev.com:443/forums/thread/12778.aspxFri, 17 Feb 2006 22:10:05 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:12778Sam Bogart0https://www.infopathdev.com:443/forums/thread/12778.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=45&PostID=12778I have a number of functions that use the XDocument.SetNamedNodeProperty method to switch the active row on a view that uses the master-detail layout. If the code is switching <b>to</b> that view, then calling the XDocument.SetNamedNodeProperty method, everything is fine.<br /><br />However ... if the user is already on one of the master-detail views, the XDocument.SetNamedNodeProperty method does <b>not</b> work at all. I verified this by calling the XDocument.GetNamedNodeProperty, and it always returns 1!<br /><br />I've tried putting a call to XDocument.View.ForceUpdate() in, but this does not appear to help at all.<br /><br />I tried adding a call to XDocument.View.SwitchView at the beginning of the function, but I ran into the limitation that there can only be one switchview call in a single business logic block.<br /><br />Any ideas would be appreciated.