Any way to do this up front? Thus in OnLoad? Reason I ask this is because I have a few customfields which are not advised/required (blue/red fields). The QuickCreate only takes these fields and because I'm doing some OnChange-scripts on non-advised/non-required fields, the QuickCreate form throws errors. Example: Account --> FirstContact --> click Lookup-button --> then disable the 'New'

I was that far :) IF I put a restriction on the QuickCreate form by using equals to type5, then how do I block the entire possibility for the current user to bring up the form? If that's not possible, then how do I only hide the 'new'-button (because that has the same result in the end)? I can't find the name of this button. "uMar Khan" <imumar@gmail.com> schreef in bericht news

Same here. I'm running the English version with UR1. "Michael Höhne" wrote: I was able to reproduce it on the English (ENU) version. Exact same behavior, the OK never gets enabled again. -- Michael Höhne, Microsoft Dynamics CRM MVP Web: http://www.stunnware.com/crm2 Feed: http://www.stunnware.com/crm2/atom.aspx Custom Lookup Dialog: http://www.stunnware.com/crm2/

Hi Ilker, Thanks for taking the time to share your experience with us. I have tested your behaviour but I cannot reproduce it. Might there be any javascript code on one of the fields or on the page onload? Also, have you applied any hotfixes/update rollups? Kind regards, -- Ronald Lemmen - MSCRM MVP Avanade Netherlands http://www.ronaldlemmen.com/ "ilker tiryaki" wrote: