In article ,
=?Utf-8?B?TG9naXN0aWNzIE1hc3RlcnM=?= wrote:
I want to produce an e-mail from a task (a bit like a task update) but want
to show all my user defined fields?

There is a fairly easy way to do this, but it is intricate.

First, I assume that your existing task form is a custom task form, published
to the Org Forms Library, and that all your user defined fields are defined in
that form. I will call this the SForm, for Source Form.

2nd. Add a button to the SForm definition, and a custom action to it, which
is the creation of an email message using your custom form called DForm, for
Destination Form. In the code behind the button kick off the custom action.

3rd. You now create the Destination Form: Start with a blank message form,
or pre-address it and add some canned message you want to use, then go into
design mode on this form, drag your UDFs onto your form. But the critical
trick here is not to drag them from the category of UDF in the Folder, but
from the SForm category, which will also appear in the list of categories.
Add what ever else you want, need, and can't do without (leave out the kitchen
sink), and publish it to the Org Forms Library, using the name you assigned to
it in the custom Action you defined in the SForm.

4th. Check it out. Open an instance of the SForm, put data in your custom
UDFs, click the magic button, the DForm should appear, with all the UDFs
auto-populated with the values from the instance of the SForm.

The very critical trick is to drag the UDFs onto the DForm from the category
of the SForm, not the category of UDFs in the Folder. This is the only way to
get the auto-population of the fields to work. If you drag the UDFs from the
Folder category, then you have to put code in the button click event to copy
the desired values from the SForm to the DForm, which you shouldn't have to
do.

Hollis D. Paul [MVP - Outlook]
Mukilteo, WA USA