I know I haven’t posted for a long time, but I’ve been REALLY busy.  These last few months, weeks, days have been hectic as I finished up projects at Microsoft preparing for my departure…

That’s right, I have left Microsoft.  I’m not going far; I’ll still be working on Microsoft CRM, just on the other side of the fence and with more skin in the game than ever before.  Aaron Elder and I (along with my wife Shannon who left a few months ago) have both decided to leave Microsoft to join Invoke Systems.  Aaron will be overseeing the development group as Director of Software Development and I will be serving as Chief Technology Officer.

Returning to Invoke Systems feels like a homecoming.  Invoke actually funded and spun-off iCommunicate which was purchased by Microsoft in April, 2001.  Aaron, Shannon and I all came to work at Microsoft through the acquisition.  We actually made up 50% of the development staff at iCommunicate!  But then again, we only had 10 employees when Microsoft acquired us.  We spent the last 3 ½ years developing features for Microsoft CRM and about a year ago I moved over to product management.  It felt like time for a move and working on the outside as an ISV definitely was #1 on our list.

I’ve basically spent the last year and a half of my career at Microsoft traveling the globe, working with ISV’s and speaking at conferences explaining WHY developing products on the Microsoft CRM platform for the application made good business sense.  Now it’s time to lead by example…

Jason B Hunt
Invoke Systems
Chief Technology Officer
jason.hunt@invokesystems.com

This posting is provided "AS IS" with no warranties, and confers no rights.

Late last night, someone posted a question to the microsoft.public.crm newsgroup regarding the fact that a new field they created in the Schema Manager wasn't showing up in the Advanced Find tool.

This is a pretty easy one... The simple answer is that once you add a custom attribute to an entity via the Schema Manager, you need to add that field to the form in the Form Editor and then save and publish it.

Now here's why:

In v1.x the XML generated by the Form Editor is used to publish a Search XML file for each entity that the Advanced Find tool uses to display the list of fields. This file gets built for each entity when you publish your customizations in the Deployment Manager. In this XML file we store the Display Name (set in the properties dialog of the attribute in the Form Editor) of the attribute; if it's a picklist we store all of the picklist values and the attribute's datatype. The Advanced Find tool then uses this information to show the list of fields and the appropriate criteria when you choose an attribute to filter on.

Sounds great, what if I only want the field to be searchable, but not on the form?

In this case you still need to add it to the form via the Form Editor, set the attribute's properties, and then remove it from the form when you're done. This won't modify the layout of the form, but behind the scenes, the properties you set will be added to the Properties XML the Form Editor controls. In v1.x, the only way to set the properties of attributes in Microsoft CRM is via the Form Editor. Once you publish your changes, the field will show up in Advanced Find, even though it is not on the form anymore. At this point, you'll also be able to add that field to Views.

If anyone shows interest, I might write up a description of the entire form publication process next time.

- Jason

This posting is provided "AS IS" with no warranties, and confers no rights.