Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel
panelIconIdatlassian-info
panelIcon:info:
bgColor#EAE6FF

This page addresses some common questions about form completion versus form submission times in CommCare.

Table of Contents

A Note About Dates and Times

Dates and Times can be a little confusing, because there are so many of them.  However, by knowing which times are defined where, you can actually use this plethora of data to do some solid debugging:

  • See how long a form took to fill out

  • See if the time on the phone is set incorrectly

  • See the time between when the form was finished and when the server received it, indicating potential network, GPRS or recharge issues

Here are parameters that are set on the server (ie, the server creates this time, which can usually be trusted):

  • server_modified_on - the last time the case was modified (good to compare to date_modified, which is set on the phone) 

  • received_on - time the form is received by the server 

Here are parameters that are set on the phone (ie, the phone sets the time):

  • timeStart - time phone records that a form is started

  • timeEnd - time phone records that a form is finished 

  • date_modified - last time the case was modified 

What is the difference between Form Completion and Form Submission?

...

How to handle project spaces with multiple countries

  • Each web user on the project may set their own perferred timezone that overrides the project timezone when they're looking at reports. If the same user wanted to see India data in IST and South America data in the correct South American timezone, then they would have to change their own preferred timezone override between looking at one location's data and looking at the other. If there are certain people who only look at India data or only look at South America data then this could be helpful for them

  • When you export data to excel, date/times will always be in UTC / +00:00 timezone / "zulu time", regardless of the project's timezone. It was decided to do this for exactly this reason: if you have different timezones at play, then as much as a pain as it is, it's still much easier if everything is consistently reported in this standard time than if it's unclear which timezone a particular date/time is in.