Solved
Issue in Bin functionality
We have issues with data provided by Bin. All technicians are unable to rely on the city provided on the order they are given. When receiving an order FSM does a look-up on Bing Maps which returns an incorrect city for the postal code. Can you please let us know if this is a known bug? If so, if there are any workarounds we can perform?
Best answer by Dhanushki Pahathkumbure
This could be a bug in Bing Map. Please drop us a case with further details so we will direct this to our RnD team and seek for their inputs. The address policy in FSM is coded to use bing, unless the dedicated business rule tells it to use google instead.When the app param "USE_BING_ADDRESS is set to Y, address policy will replace address information in the address record with data from Bing.
Setting the param to N stops that behavior. The policy will still get the geoposition data from Bing, but will use the address, city, state/prov/, zip/post information as entered by the user. Hence as a workaround if this issue is hitting lot of mishaps, we could recommend keeping app_param USE_BING_ADDRESS set to N. So, then you can manually edit the wrong address settings on tasks without having Bing map overriding address fields.
View originalSetting the param to N stops that behavior. The policy will still get the geoposition data from Bing, but will use the address, city, state/prov/, zip/post information as entered by the user. Hence as a workaround if this issue is hitting lot of mishaps, we could recommend keeping app_param USE_BING_ADDRESS set to N. So, then you can manually edit the wrong address settings on tasks without having Bing map overriding address fields.
+15This could be a bug in Bing Map. Please drop us a case with further details so we will direct this to our RnD team and seek for their inputs. The address policy in FSM is coded to use bing, unless the dedicated business rule tells it to use google instead.When the app param "USE_BING_ADDRESS is set to Y, address policy will replace address information in the address record with data from Bing.
Setting the param to N stops that behavior. The policy will still get the geoposition data from Bing, but will use the address, city, state/prov/, zip/post information as entered by the user. Hence as a workaround if this issue is hitting lot of mishaps, we could recommend keeping app_param USE_BING_ADDRESS set to N. So, then you can manually edit the wrong address settings on tasks without having Bing map overriding address fields.
Setting the param to N stops that behavior. The policy will still get the geoposition data from Bing, but will use the address, city, state/prov/, zip/post information as entered by the user. Hence as a workaround if this issue is hitting lot of mishaps, we could recommend keeping app_param USE_BING_ADDRESS set to N. So, then you can manually edit the wrong address settings on tasks without having Bing map overriding address fields.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.