Because there is nothing like "Active field" when calling webservice, you cannot do that. Do not forget that the validation is called when you are updating whole record, there is no "active field" in this process, onvalidate is not called field by field when they are changed, but in batch when the Update is called and they are called in order of the fields on the page.
Yes i know the validate triggers on tables are fired i order of the fields on the page(good). But the onvalidate triggers on pages are now disabled in SP1 when calling from web service.
Then I have to change code, when upgrading from SP0 to SP1.
Really? i thought they were called in the order of how they're evaluated in the C# code! (it was just a mere assuption, as i've never had time to test it deeply :oops: : i'll start these days)
-Mirko-
"Never memorize what you can easily find in a book".....Or Mibuso My Blog
No, they could not be evaluated in this order, because the validation is on NAV side and the whole process is triggered with the one call to the Update method, which just pass some XML and there is no "order of assigning the fields"... ;-)
which just pass some XML and there is no "order of assigning the fields"... ;-)
...and because we're talking about a page webservice, I guess that the field order in the page determine what is the order of the fields to validate, isn't it? Great! we don't even need to tell the web guys how to order the fields evaluation! :thumbsup:
I hope to "de-noob" myself about webservices soon
Thanks for now!
-Mirko-
"Never memorize what you can easily find in a book".....Or Mibuso My Blog
Comments
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
Then I have to change code, when upgrading from SP0 to SP1.
"Never memorize what you can easily find in a book".....Or Mibuso
My Blog
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
I hope to "de-noob" myself about webservices soon
Thanks for now!
"Never memorize what you can easily find in a book".....Or Mibuso
My Blog
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.