FileMaker Go: Optimizing Data Entry – FileMaker Today

With FileMaker Go an iOS device offers a superb platform for efficiently entering data on the go. It is easy, however, to overlook behavioral differences between desktop and IOS platforms.

So whether you are converting an existing solution or creating a new solution for specific use on an iOS device, you should be aware of these factors and ensure that data entry processes are as streamlined as possible.

• 
  Try to avoid using radio buttons, as there is no way to deselect an option so that no options are selected.
• 
  Inserting values into a field from an index is not possible.
• 
  Be aware that drop down lists automatically activates the iOS keyboard while pop-up menus do not.
• 
  Asian languages: sideways text and Furigana are not supported.
• 
  The auto-complete functionality using existing values is not supported.
• 
  Calendars will highlight todays date but will not commit this value until it is modified and re-selected. An appraisal as to whether a default date is set via a script trigger may well be worth consideration.
• 
  Do not use mixing text styles in a text field. FileMaker Go may not display all text formatting if there are mixed text styles or paragraph styles in one text object. Editing a text field in FileMaker Go reverts all styles in a given field to plain text.
• 
  You are only able edit about 64K of text at a time. The amount of text that you can edit changes as the text editor tries to keep the truncation point at a word break location.
• 
  Input method editors (IMEs) will not work in text fields that have script triggers set up to catch keystrokes.

These factors should all be wrapped up in a design package that is complimentary to iOS use. Ensuring that layouts, field sizes, fonts, etc. are conducive to ease of use is essential too.

– See more at: http://www.linearchat.co.uk/2013/11/filemaker-go-optimising-data-entry/#sthash.FbxDj314.dpuf

With FileMaker Go an iOS device offers a superb platform for efficiently entering data on the go. It is easy, however, to overlook behavioral differences between desktop and IOS platforms.

So whether you are converting an existing solution or creating a new solution for specific use on an iOS device, you should be aware of these factors and ensure that data entry processes are as streamlined as possible.

• 
  Try to avoid using radio buttons, as there is no way to deselect an option so that no options are selected.
• 
  Inserting values into a field from an index is not possible.
• 
  Be aware that drop down lists automatically activates the iOS keyboard while pop-up menus do not.
• 
  Asian languages: sideways text and Furigana are not supported.
• 
  The auto-complete functionality using existing values is not supported.
• 
  Calendars will highlight todays date but will not commit this value until it is modified and re-selected. An appraisal as to whether a default date is set via a script trigger may well be worth consideration.
• 
  Do not use mixing text styles in a text field. FileMaker Go may not display all text formatting if there are mixed text styles or paragraph styles in one text object. Editing a text field in FileMaker Go reverts all styles in a given field to plain text.
• 
  You are only able edit about 64K of text at a time. The amount of text that you can edit changes as the text editor tries to keep the truncation point at a word break location.
• 
  Input method editors (IMEs) will not work in text fields that have script triggers set up to catch keystrokes.

These factors should all be wrapped up in a design package that is complimentary to iOS use. Ensuring that layouts, field sizes, fonts, etc. are conducive to ease of use is essential too.

– See more at: http://www.linearchat.co.uk/2013/11/filemaker-go-optimising-data-entry/#sthash.FbxDj314.dpuf