Hi, we are making use of customField properties for user profiles. We are storin

You will have to expose those fields in the user interface under the People tab so they don't get blanked out when there's an update.

This is achieved by editing <APPIAN_HOME>/runtime_ear|ear/suite.ear/web.war/personalization/userdetail.jsp. You will expose these fields in the same manner as the normal fields. The custom fields are named field01 - field10. You should use this for the property and value tags of your input.

Example:

<asi:input label="Site Location" type="text" property="field03" disabled="${!useraction_2}" value="${result.field03}" useTextBundle="false"/>

The most important part is the "value" attribute since this will guarantee the fields are re-saved when the profile is updated.

Thanks Eduardo, we did the changes and it solves our problem.

Eduardo is this an issue with cloud installations - do we need to update the userdetail.jsp if we want to maintain user ids through customfields?

Customizing the People tab is not a Cloud Compliant request. You can still use the custom fields but they will have to be updated via Process Model using the custom plug-in called "Update User Profile (Advanced) Plug-in" and you will have to avoid updating profiles though the People tab to prevent they are blanked out.

ok thanks, I'll follow this up through the bug tracking process if there isn't a supported work-around in the cloud