• Not enough characters in the name or a phone number. The names of monitoring units, unit groups and users must consist of at least 4 characters. Other objects like places, geofences, drivers, report templates, etc. can have names from one character in length.
  

• Excessive number of characters (more than 50) in names of monitoring units, unit groups and users.
  

• Letters in numeric fields (phone numbers, sensor values, radius, fuel consumption and trip detector settings, etc.)
  

• Forbidden characters:
  
  • double quotation marks ''
    
  • curly brackets { }
    
  • the backslash \
    

• Partly forbidden characters:
  
  • spaces are not allowed at the beginning and at the end of editable fields (however, they are allowed at the middle);
    
  • comma cannot be used in numeric fields as a separator (to introduce fractional numbers use a period as a separator).
    
  • in report templates (column names, table titles, and statistics fields) you cannot use comma, colon, or & symbol.
    

Using angle brackets ('>' and '<') is allowed but not recommended as, in some cases, they are automatically replaced with '&gt;' and '&lt;'.

If any entry in a dialog is not valid, it is impossible to save changes or create an object, because the OK button becomes inactive. There can also be the Incorrect entry alert when trying to save incorrect data.

Phone numbers must be entered in an international format and contain all the necessary codes (country code, communication statement or city code, and then the phone number itself). Brackets, spaces and hyphens are not allowed. The only symbol that can be used for entering phone numbers is plus (+) which, if necessary, is typed at the beginning of the number. Examples: +959798798346, +959265756788.

E-mail addresses must be in the format user name — the 'at' sign (@) — domain name (support@gtrack.com.mm). E-mails can contain letters of Latin alphabet, as well as dots (.), hyphens (-) and underscores (_). Example: .