CRM 2011 – Using Dialogs and Dialog gotchas

I read a good blog entry by Gareth Tucker about Dialog gotchas.  Dialogs are a fantastic addition to CRM 2011 and a really powerful way to interact with the user, get values and respond.

There is a couple of quirks with Dialogs

Dialogs – You can’t save dates or bits

I have written a blog post – Dialogs can’t store dates, which basically tells you can’t stores Dates, bits or lookups.  I do love dialogs and they are a great improvement it just seems the functionality needs a bit of polishing.

if you want to learn about CRM 2011 – dialogs, here are some links

Video – how to create dialogs

Dialogs – using variables

there is also a couple of good dialog entries here Dialogs Part 1 and Dialogs Part 2

Gareth has also written a good blog entry on Dialogs here

anyway here are the gotchas from Gareth’s blog entry

  1. If your Dialog has branching logic make sure you don’t use the Responses from those branches in any later actions after the branching as those Response values will not be available in those scenarios when the user branches the other way, and CRM doesn’t like that.   To get around this make use of Variables within your Dialog.  Initialise a Variable at the start of your Dialog, update it within your branch and then you can happily refer to the Variable later in the script.
  2. Beware of placing actions such as creating records and sending emails in amongst Pages of your Dialog, they’re better placed at the end of your script firing only after the user has clicked Finish in the Dialog.  Reason for this is the Dialog UI happily allows users to navigate backwards and forwards within the Dialog.  If you have a record creating firing between pages 4 and 5 of your script that record creation will happen not only the first time the user progresses to page 5 but if they hit previous, go back to page 4 and then progress on to page 5 again then yeap you guessed it you will get another record created

4 thoughts on “CRM 2011 – Using Dialogs and Dialog gotchas

  1. Paul Jones May 16, 2012 / 12:37 pm

    how do you select the current user in a dialogue?


    • Eric June 28, 2012 / 10:38 pm

      would like to know too.


  2. Mona August 27, 2012 / 11:22 am

    To get current user in dialog process I use workaround. If we create new record inside dialog and leave “onwerid” field empty than dialog sets this automatically to current user (who runs dialog). Then we can use this “ownerid’ in other operations. If our dialog has no ‘create’ operation we can create new Entity sth like “Current user” entity which we will use to check current user inside dialogs (starting them with create new “current user” record and ending with deactivate “current user” and using delete plugin on “update” message of “current user”). It’s also comfortable to use variable “current user” and set it to our current user after creating test record (of “current user” entity). Thanks to it we can get all attributes from current user record (like email, address, etc.). Is it Ok? What you think..?


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.