Skip to main content
Fields are usually detected via their names, but not all fields on the documents have names. For example, the field that contains the recipe name has no name of its own, so detecting it needs a different approach. One approach is to tell FlexiLayout Studio that the recipe name is the object closest to the form’s heading. On test image 6, however, the closest field is Recipe #:. You can sometimes specify additional search constraints that help FlexiLayout Studio distinguish between two fields, but here it is difficult, because the recipe name and the Recipe #: field sit very close together and have similar structures:
  • The name Recipe #: and the field itself are on the same level, and the field may contain the same characters used in the recipe name.
  • The recipe name is not always longer than the name Recipe #: and its field.
Pre-recognition, however, consistently detects the name Recipe #: on all the test images. You can therefore tell FlexiLayout Studio to look for Recipe #: first. It then looks for the recipe name as the object closest to the document heading that is not Recipe #:, which it has already detected.