How LiveCycle Designer ES converts Microsoft InfoPath objectsLiveCycle Designer ES preserves the layout when converting a Microsoft InfoPath file. However, you may need to do some manual repositioning of objects afterward to make the form look as good as possible.The table identifies the key objects in an InfoPath form and indicates how LiveCycle Designer ES treats them when they are imported.
Text boxes, including rich text boxes, are converted to text fields.Drop-down list boxes are converted to drop-down list boxes. Values are included only if the control is filled manually.Date picker controls are converted to Date/Time fields unless the data type for the date picker in InfoPath is set to “Text (String)”. In this case, it is converted to a Text field. A group of option buttons may not be converted to a single radio button group.Padding properties of check boxes and radio buttons For bulleted lists, the text only is converted to text. If the InfoPath form has been designed based on a schema, the schema is imported and binding is done automatically in LiveCycle Designer ES. Scrolling regions are converted to subforms. Repeating sections are converted to repeating subforms in a form. Add and delete buttons are provided to add or delete the instance of the section when filling the form. Only one instance of any optional or repeating sections is converted Repeating tables are converted to repeating tables in a form. Add and delete buttons are provided to add or delete the instance of the section when filling the form. Only the visible rows in a repeating table are converted.Rows that have been merged vertically are converted to subforms in a positioned layout. Text is converted to text. Any highlight color is converted to background color.