Based on our logic for Custom fields, when the user fills in a Custom field with some value, it is automatically being moved to the top of the form. This is the expected behavior.
The order of the Custom fields in the form as it was set up in the Piano dashboard is reflected accordingly if all Custom fields are empty or all Custom fields have any value filled in. More information about creating Custom fields and forms is available here.
The current logic for the sort order of Custom fields is as follows:
-
Display completed custom fields where the user entered a value/action
-
Sort the completed custom fields by the order that the publisher set for the custom fields form
-
Incomplete fields should be sorted in the same way
Piano also allows you to render a custom field separately from the custom fields group. To do this, you will need to insert snippet into the appropriate line with the field's name in this template.
In case the custom fields have a tooltip, the above workaround will cause not to display it. To fix this, you can remove the check for the tooltip type and have it show the tooltip. Outside of the context of the custom-fields object, that check is failing to locate the relevant custom field.
So for example:
<div class="control-label-icon" showForTooltipType="InfoIcon" [fieldName]="field.field_name">
Becomes:
<div class="control-label-icon">