I have a CRM 2011 form with multiple control instances of the same lookup field. Each of these instances is included in a different section. Only one section is visible on form load, depending on a category data field, by applying the setVisible attribute appropriately on the sections in the onLoad javascript function.
In this situation, every time I change the visible lookup field, all the other lookup controls, which have the same control attribute, are also getting updated automatically, even if they are disabled and not visible. And this is causing a long delay when selecting a lookup value in the lookup field.
What I want is to only update the visible lookup control, and not the other ‘not visible’ lookup controls, in order to avoid the slow performance.
Is there any efficient way to do this?
You can create a “fake” lookup, using html or silverlight webresource, when you setting lookup value, you only set the webresource, and then when you save the record, use plugin or onsave javascript to set the real lookup value; When display the webresource, retrieve the lookup value and display on the webresource base on the section visible or invisible.
My question is, why not put the lookup in another section which is always visible? If some sections don’t need that lookup, then you just make the lookup section invisible.