Rory, We are having some of the same issues. I have created a couple of work arounds but have not finished them. To get around the textinput you will need to use modiffy the FieldInspector for each text field using the esri:StringField such as: <esri:FieldInspector id="MH_DipNFI"
featureLayer="{layerName}"
fieldName="DipN"
label="Dip N">
<esri:editor>
<fx:Component>
<esri:StringField width="100"/>
</fx:Component>
</esri:editor>
</esri:FieldInspector>Another way I am working on is to use callout buttons or callouts to create new popup lists using renderers. http://forums.arcgis.com/threads/75295-FieldInspector-custom-callout-mobile?p=267024#post267024Still working on how to get the data back to the database using custom renderers. A good place to look for some ideas is the following samples:http://resources.arcgis.com/en/help/flex-api/samples/index.html#/Attribute_Inspector_edit/01nq000000...http://resources.arcgis.com/en/help/flex-api/samples/index.html#/Custom_FieldInspector/01nq0000007p0...http://resources.arcgis.com/en/help/flex-api/samples/index.html#/Custom_FieldInspector/01nq0000007p0...And some information from this post is helpful:http://forums.arcgis.com/threads/19995-Easiest-way-to-customize-AttributeInspector-associated-with-a...
