Importing Data Minutely:

The interface pulls data based on the doForms Date_Created field.  This is the time the form was saved ON THE DEVICE.  If the interface is set to run minutely (see Automated Import Configuration) data can be missed if the user Saves the Form and then at a later time Sends the data. 

Example: 

1.User enters data at 12:53:39 and saves the data (but does not send it).  The interface runs at 12:54 and retrieves data since the last time it ran (12:53), since this data is not on the doForms server yet, the data is not imported. 

2. User at 1:05, sends the form to the server.  The Date_Created is set to 12:53:39.  The interface runs at 1:06 and retrieves data since the last time it ran (1:05).  The data is not imported because the Date_Created is less than 1:05. 

You therefore MUST set the "Constant to Add to Start Date Each Time Import Runs" (see Automated Import Configuration for how to set) to a negative number such as -120.  This setting subtracts the number of minutes specified from the last time the interface is run and data is imported for that data range.  So, at 1:06 the interface would run for 11:05 to 1:06 and the data would be imported. 

Errors Returned from Hach's Web Service Library

Any error conditions from doForms Web Service should now propagate back to the interface as shown below:

Above we see a message from doForms:

Status code 504 - exceeded doForms daily quota limit.  According to the doForms documentation: "Limits on Data Record Reads: The limit is currently set to 50 times the number of mobile units in you account per day. So as an example, if you have 30 mobile units in your account, you can read 50X30=1500 records per day. "  The limit is per form.  A record is defined as all the data for a submitted form:

The daily limit resets at midnight Greenwich Mean Time (GMT/UTC). There are a couple options for customers having this problem:

1. Contact doForms support to increase their quota limit.
2. Increase the number of mobile devices.
3. Have multiple forms for the day (i.e., one form for midnight to 4 AM, one for 4 AM to 8 AM, etc.)

Any error conditions from Hach Web Service Library propagate back to the interface with the Status Code = 'Hach-Form ID' and the Form ID number, as shown below:

Above we see the Hach message Date field not found on doForms form or there was no value in the Date field. See doForms Viewer for information on finding the Form name for a Form ID.

HINT: The doForms form must have a datetime field called Date and make this field 'Required in mobile app' so that it will always have a value.   

Hach WIMS Web Service Tool

This tool allows you to view what is coming from the doForms Web Service

See doForms Viewer for more information.