Hi Shidin, thanks for your response. Right now, for us the only way a user can create an opportunity is through a sub grid we have on our account form. We override the add new + click on this grid and force it to open the main form, and also pre-fill the account into the parentaccountid field for the user. When the user saves, CRM is saving the parentaccountid to the customerid automatically. We aren't manually filling it. So that functionality is out of the box it appears. The issue is that when the user also fills out the parentcontactid, then clears it, CRM also clears the customerid automatically. So it's the change of the contact that clears the customerid. Currently I put a workflow in place that when the parentcontactid changes, I check if the customerid is null, and if it is null I fill it with the parentaccountid. This is fairly close to what you suggested. I was hoping there was a way to break the link, so that CRM would not auto-clear the customerid when the parentcontactid is changed, so I wouldn't need to have a workflow. Your explanation of how the customerid maps to both parentaccountid and parentcontactid is interesting. It seems to indicate the intended use of the fields is to expose customerid, prefilter (if desired) it down to just accounts or contacts and let it fill the other fields. And then hide the field you don't want to use. So the only use of the 2 named fields is to determine if an acocunt or contact was selected. So then would the intended use be for us be to prefilter the customerid to accounts only, and then create a custom contact field that is not associated with the customerid? Then no extra steps would be needed? thanks!
↧