Matt
Fri Mar 17 10:22:53 CST 2006
Ronald,
You are right. The thing that got me was the fact they have the 2nd tab on
the entity screen that shows the primary attribute. From there, you can not
change anything after the entity is created, but from the attribute form
itself, yu can.
--
Matt Parks
MVP - Microsoft CRM
"Ronald Lemmen" <RonaldL@-REMOVETHIS-avanade.com> wrote in message
news:5FE31C84-D2DC-437B-9C59-372D27237749@microsoft.com...
Hi Cindy and Matt,
I've just discovered that within the vpc which you can download from
Microsoft, this is enabled by default. You can change the requirement level
even after creating the entity. I've checked this with Rob Bakkers, he's
also
able to do this in the Dutch version of CRM.
I can remember that I wasn't able to do this as well some time ago, but that
might have been with EAP or TAP versions.
What version are you using? What's the build number?
--
Ronald Lemmen
Avanade Netherlands
http://ronaldlemmen.blogspot.com/
"Matt Parks" wrote:
> when you craete the entity, you can change this attribute to not be
> required
> prior to saving the new entity.
>
> --
>
> Matt Parks
> MVP - Microsoft CRM
>
>
> "Cindy Mikeworth" <CindyMikeworth@newsgroups.nospam> wrote in message
> news:%23yay3lWSGHA.4956@TK2MSFTNGP09.phx.gbl...
> I'm having some difficulties wrapping my head around the required primary
> attribute of a new entity.
>
> I am trying to create a software module entity that has a parental
> relationship with an account, and can do a lookup into the products table.
> In the simpliest sense, those are the only two fields that I need.
> However,
> the system is forcing me to create, use and enter a third piece of data
> which is the primary attribute of the entity.
>
> Is there some way that I can suppress or at least hide this additional
> field? Is there a purpose for this field that I am not seeing?
>
> Thoughts appreciated.
>
>
>
>