M
Meryk
Guest
Hi Siraj, Yes I am seeing this behavior with a lookup field rendered as a piclklist (a one relationship). So when I disable this field using rbf_setFieldDisabled() it is both emptied and disabled. I also have another lookup field rendered as a selector (a many relationship), and rbf_setFieldDisabled only disables the field without emptying it. Not sure if this is related to how the lookup is rendered (picklist or selector) or to the type of the relationship (one or many). Also we are on a QC page. Thanks, Meryem
Continue reading...
Continue reading...