Upgrade from NAV 2016 CU5 to NAV 2016 CU14

jwilder

We have upgraded our executables only from NAV 2016 CU5 to NAV 2016 CU14 to get rid of some known bugs. Everything is working great except one of our integration's using some pages exposed through a web service has started to fail. The error says: Filter "Blocked" is invalid

We believe that the filter for boolean fields may have changed a little in regards to calling a page through a web service. Currently the 3rd party application is setting the value for Blocked = "false". Does anyone know if this has changed (from CU5 to CU14) to something like FALSE, No, 0 or something like that?

jwilder

I have found the answer to this. It is not that the value of a boolean has change slightly in web services as I was suspecting. It is that somewhere from NAV 2016 CU5 to NAV 2016 CU14 web services no longer accept filters that are invalid. Before it would basically skip a field/criteria that did not exist on the page. Now it throws an error if you try to filter on a field that does not exist on the page.

So in the end the Blocked field did not exist on my page that was being called through web services so the fix is to either add the Blocked field to the page or remove the filter field and criteria from the 3rd party integration calling the page.

jwilder

I have found the answer to this. It is not that the value of a boolean has change slightly in web services as I was suspecting. It is that somewhere from NAV 2016 CU5 to NAV 2016 CU14 web services no longer accept filters that are invalid. Before it would basically skip a field/criteria that did not exist on the page. Now it throws an error if you try to filter on a field that does not exist on the page.

So in the end the Blocked field did not exist on my page that was being called through web services so the fix is to either add the Blocked field to the page or remove the filter field and criteria from the 3rd party integration calling the page.