I just attended a webcast for Scribe partners to learn more about Scribe 6.5. This is an important release and includes many new features and enhancements.
I recommend you attend the webcast scheduled for next week. Details are below.
In addition, you can download a release overview document at http://www.scribesoftware.com/Products/Docs/ScribeInsight6.5ReleaseOverview.pdf.
Webcast: Scribe 6.5 Product Launch – Thursday, April 16 @ 11am – 12pm EST
Insight 6.5 is a major release which includes an extensive list of features that have been requested by Scribe partners and customers. The new release also includes significant new functionality targeted at enterprise accounts. These are:
- Failover/Disaster Recovery
- Web Services Adapter
- Support for 64-bit Windows Server 2008
Scribe Presenters for the webcast will be:
Bob Sturim - Vice President, Products
John Gravely - Vice President, Marketing and Product Marketing
Lou Antonucci - Director, Sales
Please register at the following registration URL: https://www.livemeeting.com/lrs/8001615779/Registration.aspx?pageName=8nlw1x85309wfbns
Thursday, April 9, 2009
Thursday, March 19, 2009
Migrate from Salesforce.com to Microsoft CRM Using Scribe Insight
Are you using Salesforce.com and want to replace it with Microsoft Dynamics CRM, but you're not sure how you are going to migrate all your data?
Have no fear! Scribe Insight is here!
I know, I know. That's cheesy. But the fact is that Scribe Insight is an extremely valuable tool.
Scribe Insight is a product from Scribe Software that is used to migrate data from one database to another, or to integrate systems. Learn more here: http://www.scribesoftware.com/microsoft-dynamics-crm.asp.
As an example, a project I'm working on involves migrating the following objects from Salesforce.com to Microsoft CRM:
Scribe connects directly to both the Salesforce.com and Microsoft CRM databases, so there is no extracting of data into a staging database, no CSV or text files, and no Excel files. The data is extracted from Salesforce.com, transformed, and loaded into Microsoft CRM in one step with no human intervention.
While some of the fields are direct mappings with no transformations, other data must be transformed to some degree. For example, a text field in Salesforce.com might be mapped to a picklist in Microsoft CRM, which stores a number in the database rather than the actual text. Or a field might be a picklist in Salesforce.com, but a lookup to a custom entity in Microsoft CRM. Or a 255-character text field for the address in Salesforce.com must be split into three 50-character fields (line1, line2, and line3) in Microsoft CRM. Scribe Insight handles all of these situations, and many more.
Normally, moving data from Salesforce.com to Microsoft CRM can be a pain, but Scribe Insight and the adapters for Salesforce.com and Microsoft CRM make the process relatively painless. As a result we are able to migrate thousands of records within minutes or hours.
Typically, we migrate selected data into Microsoft CRM, validate the data, make changes to the data mappings, if necessary, and then continue migrating additional data. Once all data has been validated and the users have completed their testing and training, we'll delete all the test migration data from Microsoft CRM and run all the migration processes one last time at cutover. This process works very well.
While many people consider data migration a "technical" task, you don't want to delegate this to the technical people unless they have a complete understanding of the data that is in Salesforce.com: what it represents and how it is used. And I do mean complete. Somebody who understands what every field represents and how it should be mapped to Microsoft CRM MUST be involved.
This project will be going live next week. Thanks to Scribe Insight, the data migration has been a complete success.
Have no fear! Scribe Insight is here!
I know, I know. That's cheesy. But the fact is that Scribe Insight is an extremely valuable tool.
Scribe Insight is a product from Scribe Software that is used to migrate data from one database to another, or to integrate systems. Learn more here: http://www.scribesoftware.com/microsoft-dynamics-crm.asp.
As an example, a project I'm working on involves migrating the following objects from Salesforce.com to Microsoft CRM:
- Leads
- Accounts
- Contacts
- Opportunities
- Events
- Tasks
- Notes
Scribe connects directly to both the Salesforce.com and Microsoft CRM databases, so there is no extracting of data into a staging database, no CSV or text files, and no Excel files. The data is extracted from Salesforce.com, transformed, and loaded into Microsoft CRM in one step with no human intervention.
While some of the fields are direct mappings with no transformations, other data must be transformed to some degree. For example, a text field in Salesforce.com might be mapped to a picklist in Microsoft CRM, which stores a number in the database rather than the actual text. Or a field might be a picklist in Salesforce.com, but a lookup to a custom entity in Microsoft CRM. Or a 255-character text field for the address in Salesforce.com must be split into three 50-character fields (line1, line2, and line3) in Microsoft CRM. Scribe Insight handles all of these situations, and many more.
Normally, moving data from Salesforce.com to Microsoft CRM can be a pain, but Scribe Insight and the adapters for Salesforce.com and Microsoft CRM make the process relatively painless. As a result we are able to migrate thousands of records within minutes or hours.
Typically, we migrate selected data into Microsoft CRM, validate the data, make changes to the data mappings, if necessary, and then continue migrating additional data. Once all data has been validated and the users have completed their testing and training, we'll delete all the test migration data from Microsoft CRM and run all the migration processes one last time at cutover. This process works very well.
While many people consider data migration a "technical" task, you don't want to delegate this to the technical people unless they have a complete understanding of the data that is in Salesforce.com: what it represents and how it is used. And I do mean complete. Somebody who understands what every field represents and how it should be mapped to Microsoft CRM MUST be involved.
This project will be going live next week. Thanks to Scribe Insight, the data migration has been a complete success.
Monday, March 2, 2009
Scribe Insight Level 2 Training
I attended a 2-day course last week for Scribe Insight Level 2 Training, and it was very helpful. Even though I was already certified, the Level 2 training covered materials in more depth and detail, providing me with a much stronger understanding of how Scribe Insight works and how to install and configure it.
For example, I now have a complete understanding of how the queue-based integration processes work, and when to implement them (hint: this technique alone will help reduce the length of a daily integration from 10 hours to less than 2).
If you're interested in developing your Scribe skills, then learn more on the Scribe site:
For example, I now have a complete understanding of how the queue-based integration processes work, and when to implement them (hint: this technique alone will help reduce the length of a daily integration from 10 hours to less than 2).
If you're interested in developing your Scribe skills, then learn more on the Scribe site:
Wednesday, January 28, 2009
Navint and Tribridge Merge!
Big news at Navint! Effective last week, Navint merged with the 2008 Microsoft Dynamics Partner of the Year, Tribridge (http://www.tribridge.com), and we are now known as Tribridge.
Read the news release to learn more (Two U.S.-based IT Services Firms to Combine in Merger of Equals):
What does this mean for you, the client? It means that you now have even MORE resources at your disposal, including experts in all Microsoft Dynamics products, SharePoint, Business Intelligence, Infrastructure, Security, and Managed Services.
From an operations and relationship perspective, nothing changes for you. You will have the same Relationship Manager and you will work with the same people. As we continue to integrate the organizations, you will be notified of any changes that impact you.
In the meantime, if you have any questions, please contact your Relationship Manager or other contact at Navint.
Read the news release to learn more (Two U.S.-based IT Services Firms to Combine in Merger of Equals):
What does this mean for you, the client? It means that you now have even MORE resources at your disposal, including experts in all Microsoft Dynamics products, SharePoint, Business Intelligence, Infrastructure, Security, and Managed Services.
From an operations and relationship perspective, nothing changes for you. You will have the same Relationship Manager and you will work with the same people. As we continue to integrate the organizations, you will be notified of any changes that impact you.
In the meantime, if you have any questions, please contact your Relationship Manager or other contact at Navint.
Monday, January 12, 2009
Update to post
In my post dated 12/10/2008 titled "How to correct Microsoft Dynamics CRM 4.0 user record if Active Directory domain logon changes", I documented the procedure to correct the logon for a user in CRM.
Well, I came across kb article 930853 that discusses this in more detail. Hope it helps.
Well, I came across kb article 930853 that discusses this in more detail. Hope it helps.
Saturday, December 13, 2008
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:
Well, I finally have another option: a paid (and supported) solution from an ISV.
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.
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.
Wednesday, December 10, 2008
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.
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.
Subscribe to:
Posts (Atom)
