Tech Support > Microsoft Windows > Windows CRM > Protecting fields from owner deletion
Protecting fields from owner deletion
Posted by Phifunk on September 22nd, 2004


folks,

I have a custom field on the lead screen
called "campaign_code" which a user enters a number into.
This field is mapped to the opportunity screen and should
be read only at that point. If I set deletion for
opportunity's to no for that user, will it prevent him
from altering information ported over from the original
lead?

We want to avoid reps changing infomration after the fact.

thanks in advance.

Posted by MattNC on September 22nd, 2004


Phifunk:
If you remove the Delete privilege for the Opportunity object for a
particular security role, this will only prevent the users from deleting the
Opportunity itself. You could remove the Write privilege if they don't need
to add any further information to the Opportunity. There is no supported way
to make a particular field read-only.

"Phifunk" wrote:

Posted by phifunk on September 22nd, 2004


any plans for the future? This would be handy

Posted by kat on September 23rd, 2004


I have similar GAPs that were filled by mapping the
information to an opportunity field that is not displayed
on the form. You could also map to a displayed field...

Also, if I need an audit trail for picklist field changes,
I trigger an onchange event to write the picklist value
and date\time to a memo field not viewable to the users.
It is a very clunky workaround, and one that I'm hoping
CRM 2.0 will make obsolete.

Good luck!


Similar Posts