There is a timing issue with setCanEdit when the formItem should fetch missing values.
If the formItem requires to fetch the missing display value of a record value, from the optionDataSource. It will display a loading value message in the textitem (if configured). This option disables the formItem so it can't be edited by the user, this is all cool and nice. But if you set the formItem to canEdit=false using setCanEdit(false) during this fetch, it does not work because the last known canEdit is overwritten again with the remembered canEdit (_explicitCanEdit) when the response of the display value returns.
@See:
ISC_Forms@24748
ISC_Forms@24791
If the formItem requires to fetch the missing display value of a record value, from the optionDataSource. It will display a loading value message in the textitem (if configured). This option disables the formItem so it can't be edited by the user, this is all cool and nice. But if you set the formItem to canEdit=false using setCanEdit(false) during this fetch, it does not work because the last known canEdit is overwritten again with the remembered canEdit (_explicitCanEdit) when the response of the display value returns.
@See:
ISC_Forms@24748
ISC_Forms@24791