Anyone know of a way to cause an unused field to not be shown in the
list of fields you can filter on when doing an advanced find?

Also, CustomerTypeCode shows up on the list when doing a find on
Company but not on Contact, even though it's a valid field on both -
Any idea how to add that back?

As well as i know the fields in list will appear as long as they are at
the attributes of entities. If you remove them from their then you
would not be able to find them in the list.

Aami

I just have the same problem with Contact.Customertypecode not available in
Advanced find.

Did you received solutions on this problem ?

If I find something, I will let you know.
--
Sylvain


"Mr Dave" wrote:

I am having the same problem. I had planned to use contact.customertypecode
as an advanced search filter criteria, but this field is not available in
advanced searches. The field is available for advanced searched for
account.customertypecode.

I tried exporting the contact entity, editing the XML, reimporting and
publishing the change, but it still would not show up as a valid attribute to
use in contact advanced searches.

I ran the CRM Metadata Browser http://<crmserver>/sdk/list.aspx, and it
shows that the customertypecode attribute is available to use for account
advanced searches, but not for contacts.

Is this a Microsoft CRM 3.0 "feature"? Is there any way to fix this problem?

Don

"Sylvain Trilogia" wrote:

Don,
did you find a solution? I have the same trouble with accounts and the
businesstypecode attribute, which are not showing up in advanced find...
Please let me know.
Thanks, Nikolas

"dwh78759" wrote:

I never found a fix or workaround to this problem. I did find a post in the
MBS CRM Deployment forum that suggested a workaround, but it did not work for
the customertypecode.

Here is the workaround they proposed.
++++++++++++++
However, there is a known issue that some of the base CRM fields are not
showing up in the advanced find. accountclassificationcode is one of those
fields.

"Patrick" <Patrick@discussions.microsoft.comwrote in message
news:1200F691-8CDD-4E57-831E-638FAF8905E3@microsoft.com...

Not all fields are marked ValidForAdvancedFind.
You can try to change this, but this requires some work.
If you export the entity you have this problem with (using Settings ïƒ*
Customization ïƒ* Export Customizations) and open the exported xml file in a
text editor (notepad). If you go through this file you will find a
sections
named <attributesthis contains an entry for each attribute like this:
<attribute PhysicalName="AccountId">
<Type>primarykey</Type>
<IsNullable>0</IsNullable>
<ValidForCreateApi>1</ValidForCreateApi>
<ValidForReadApi>1</ValidForReadApi>
<IsPKAttribute>1</IsPKAttribute>

<DisplayMask>ValidForAdvancedFind|RequiredForGrid< /DisplayMask>
<Description>Unique identifier of the account. </Description>
</attribute>

The property <DisplayMaskdetermines where the field will show up.
If you have a property which does not have the ValidForAdvancedFind this
property won't show up in the advanced find list. What you can do is add
this (make sure you have a | between each item) then import the altered xml
file.
Note: For some reason CRM does not allow certain properties to be changed
for certain fields, which means that even if you make alterations there is
no garantee the CRM will accept the changed value.

Patrick Verbeeten (MCSD)
Lead Developer
Aviva IT www.aviva-it.nl


"Nikolas" wrote:

Thanks Don! I was hoping that Microsoft will provide a fix for that or at
least a statement when we can expect a fix. Seems to be not important enough
to Microsoft! I posted another message asking specific for that – but also no
response. Do they ignore me or better this problem?
Nikolas


"dwh78759" wrote: