Create assignments - workOrderIdField & locationField

[nart-t]

Create assignments - workOrderIdField & locationField

[ming800]

Same issue here, my workOrderId is a string data. Thanks for the tip.

In addition, the dispatcherId should be a integer instead of string. After adding the int() in line 78, it work fine now.

Thanks for the great tool!

Ming

[ming800]

Why is the locationField required?
Location field is very useful for many situations. The XY or Lat/Lon are just numbers. It is difficult for none GIS/geographer person to reference the numbers to a location in real world. We use the tool for water utility work orders. The location field is used to store a FacilityID, such as ID/Ma,e for a pump station or valve, an accountNumber for meter repair, or a address for new service installation.

Ming

[ming800]

After reading the codes, realize that the dispatcherID is intended for a string name of the dispatcher. The code will looking for the oid for the matching name.

Ming

[crai3162]

@nart-t thanks for your comments on the scripts:

1. this was an oversight in the script; WorkOrderID can be either int or string; we'll get this clarified.
2. @ming800 provided a great reply on why we require locationField to be set; in the case where you only need to use X/Y coordinates. you can enter those as the locationField, that is what the Workforce web app does when the reverse geocode does not return an address.

@ming800 thanks for the comment on the dispatcherID, will also make sure we update the scripts for this as well.

[apulverizer]

The scripts have been updated so that it does not cast workOrderId to an integer and so that it does cast dispatcherId to integer.

I'm closing this as it should be solved, but feel free to re-open if these changes did not address your issue.