Requirements are always crazy, suppose if you want to optionally disable or enable a field in BPF it is possible with XRM object model. The only change is the prefix which you need to add to your attribute's logical name
Xrm.Page.getControl("header_process_<field logical name>").setDisabled(bool);
It is not working when you move to the next BPF stage. The Field becomes editable.
ReplyDelete