Add AutoNumber functionality to Microsoft CRM

We have had many clients request the automatic generation of unique identification numbers for various entities in Microsoft CRM. For example, automatically generating and entering an account number for the Account entity or an opportunity number for the Opportunity entity.

Depending on the convention used and the complexity (e.g., sequential number, date-based number, etc.), the solution typically involves one of the following options:

• Manual generation and entry (inefficient)


• Custom JScript (not appropriate for more complex requirements)


• Custom Callout/Plugin (requires .NET developer and may be too costly to develop and maintain)


• Free (and unsupported) solutions from ISVs (not necessarily appropriate for production deployments since they are unsupported)

Well, I finally have another option: a paid (and supported) solution from an ISV.

This solution is inexpensive and appropriate for a production deployment of Microsoft CRM.

AutoNumber from CRM Innovation is a perfect option for the vast majority of situations I've come across, with only a couple of complex situations requiring something more advanced.

The pricing is VERY reasonable. Note that all prices are absolute prices and not per-user prices.

Up to 49 users: $295
50 - 199 users: $495
200 -499 users: $695
500 - 999 users: $1,295
1000+ users: $1,995

Note that maintenance, support and upgrades are all included for the first year, and 20% annually thereafter.

Support is via email, although it can be escalated if necessary.

I tested AutoNumber in my CRM 4.0 VPC image on the opportunity entity and it worked beautifully. The documentation made installation and configuration very easy and quick.

Some of the customizable options are:

• Prefix


• Suffix


• Increment or decrement


• Starting values


• Lengths and leading zeroes

AutoNumber can be configured for both system and custom entities.

AutoNumber will work even when records are imported using the built-in import utility or third-party import tools such as Scribe Insight.

A particularly helpful feature is the Backfill utility that enables assigning unique numbers to existing records. Ideally, you would run this utility after implementing AutoNumber in a Microsoft CRM deployment that includes records that were created prior to implementing AutoNumber, but before you start creating new records.

It's obvious that AutoNumber was designed based on real user requirements. As a result, it provides real value.

If you have a need for automatically generating unique identifiers for Microsoft CRM 4.0, then I highly recommend that you check out AutoNumber. More information on features, FAQs, and screenshots and videos are on the website.

Let me know your experiences and thoughts if you try it out.

How to correct Microsoft Dynamics CRM 4.0 user record if Active Directory domain logon changes

Issue:
We had a client using Microsoft Dynamics CRM 4.0 who created a new user in Active Directory, and then created the user record in CRM.

They then realized that the user's last name was misspelled, including the domain logon, which was in the format of first name initial and last name.

They corrected the spelling in Active Directory. They then attempted to update the user record in CRM by updating the domain logon field. The updated information is pulled in from AD. However, when they attempt to save the record, they receive a dialog box with the following message:

"You are attempting to create a user with a domain logon that is already used by another user. Select another domain logon and try again."

Resolution:
The solution is to modify the CRM user record to use a domain logon that is NOT currently used for a CRM user. Once the record is saved, you can then modify it again to pull the correct domain logon from Active Directory.