InfoPath Dev

Thanks for your quick reply. Nice idea - although I'm not entirely sure if you're being sarcastic with the last comment on K2. ;) I'm not actually using the task pane, instead I'm using a button on my form that when set to 'Submit' action works fine for submitting to K2 - as long as you don't want OnSubmitRequest() to run. Since posting, I've ...

I'm integrating my InfoPath form with a K2.net workflow and I'm having difficulty with the OnSubmitRequest() event handler. Prior to integration with K2.net, it doesn't matter if I set a button to a 'Submit' action, or to 'Rules and Custom Code' and call thisXDocument.Submit() within the button's event handler, either way OnSubmitRequest() is ...

I've solved the problem. It lay in using '= true' in the expression - if I remove this and set the expression to be: xdExtension:OtherApplicationSelected() then the validation works fine.

D'oh! Thanks, Franck. I had a nagging doubt the answer was obvious. :)

I've written an OnSubmitRequest() function to check if data for all the required fields has been supplied. Within the function I've called MessageBox to display an error if the validation fails. However I still receive the standard message: ''InfoPath cannot submit the form. The onSubmitRequest event handler returned a value indicating that the ...

Patrick, I've set up the conditional formatting as described above, using a xdExtension function, and it works fine. The problem comes when I try to use the same expression in a Data Validation clause. I placed a break point in function I'm calling with xdExtension and I tested that the return value was set to the correct value - although ...

Thanks again to both of you. I will have a play with both ideas and see what happens. Cheers, David.

Okay, thanks for the feedback - I was slowly going nuts trying to work out why it wasn't working. I'll try to figure out another way of achieving my goal.

I got the following recommendation from Microsoft: Clear the ''cannot be blank'' checkbox for the field on view ''B''. Create an item in your data source to contain the name of the current view and use the OnSwitchView event handler to update the field name when the view changes (C# code): thisXDocument.DOM.selectSingleNode( ...

...well so I thought. Using an xdExtension function works just fine on the Conditional Formatting clause, however using the same expression in a Data Validation clause behaves erratically. Are there any issues with using an xdExtension function within the Data Validation condition?