is the quick create form for contacts customizable? it only shows the first
and last name field. in the dutch language for example the first, middle name
and last name are all required fields.

The quick create form shows all attributes that are marked as business
required or business recommended. To achieve your goal, open the contact in
design mode, switch to the attributes view, select middlename and change the
required level to recommended. Save the attribute and publish the form. The
quick create form now should contain the middle name for input, but it's not
a required field.

--
Michael
http://www.stunnware.com/crm
----------------------------------------------------------
"manuel" <manuel@discussions.microsoft.com> schrieb im Newsbeitrag
news:70AD3238-40B9-4123-8FAB-1AC559FA2B64@microsoft.com...

Tnx!

"Michael Höhne" wrote:

I have used the 'recommended' status to add attributes to the quick create
form. Unfortunately CRM has not ordered them correctly ('street 1' follows
'city', which follows 'street 2' etc.). Is there any way to edit the quick
create form so it looks as expected?

"manuel" wrote:

Never used that much fields in a quick create form, so no, I don't know if
there is a way to order them.

--
Michael
http://www.stunnware.com/crm
----------------------------------------------------------
"Robert Turnbull" <RobertTurnbull@discussions.microsoft.com> schrieb im
Newsbeitrag news:5F0099A2-3644-4037-B1C8-AA87607CB5EA@microsoft.com...

Yeah, I have noticed this (my users have too). It apparently uses the
right-to-left order of the fields on the main form to generate the
quick create dialog. I wish it would use the tab order instead but I
can't find any way to make that happen.

Greg

The way I read about accomplishing the tab order you want involves creating a
separate section for each field in the main form, and then just hiding the
section header/divider lines so that it's not obvious each field is in a
different section.. then it will control better, according to section
divisions also

"gstat" wrote:

Quick Create forms also carry over dependant fields. So if you don't want to
confuse your users by having recommended fields on the original form, you can
create dependancies for the other fields you would like to see on the Quick
Create.

Could you please clarify what this means and how to make fied dependant.
I tried in non event dependanies tab... no luck.
-pertti

"Chris" wrote:

Hi Perttis - I too would like some info on how to create dependancies between
fields (i'm reasonably new to CRM 4.0 and am a non-programmer).

Thanks
Matt

"Perttis" wrote:

HI Matt,

To set dependancies between fields is not too difficult, just open the
form customization, double click to open up the field properties,
click on the Events tab, then click Edit to open the Event Detail
Properties, then click on the Dependencies tab and add the fields to
define the dependencies for a specifc field.

If it's just for the form dependency, after you open the form
customization, click on Form Properties, then click on Non-Event
Dependencies tab, then add the fields you would like to add.

Hope this helps.

Darren Liu, Microsoft CRM MVP
Crowe
http://www.crowecrm.com

On Jul 1, 10:50*pm, Matthew McMaster
<MatthewMcMas...@discussions.microsoft.com> wrote:

Hi Darren,

Thanks for the clear response, much appreciated. I can get to this part OK,
and select fields etc, but I guess where i'm coming from I don't know what
this actually ends up allowing me to do. ie i chose one field called 'vehicle
make' and followed your instructions to set a dependent field of 'warranty'.

But what has this actually accomplished? I'm afraid I dont know if this
means, that warranty MUST be filled in if vehicle make is filled in, vice
versa, or something totally different.

What I actually want to happen is that if field 'Warranty' has a certain
value, then that means other fields become mandatory. Maybe what I want is
something different to what dependencies does, but in saying that, what does
the dependencies function actually do?

(PS i did try CRM help, but apart from steps, there little 'why' as opposed
to plenty of 'how'

"Darren Liu" wrote: