Today I want to talk about Fiddler2 and how to use it for resolving Integration Errors.
Pretty often during integration we are receiving completely un-meaningful or confusing errors, so resolving them become a really nightmare. Here is the good example:
Nice and short video overview about new V2(FP7) Connector features was posted by MSFT Team on their Connector Blog recently.
In This overview Chris show us
- how to use Map Filtering
- what does mean new CRM 2011 Adapter setting and how to use it
- How to use Connector with SL2011
- Changes in Licensing (very good possibility for Customers with integration CRM – Custom Software)
In one of my first Integration project Customer said that he don’t wan’t to sync blocked Items with CRM Prodicts.
Sure, why not. I checked Connector Manual, not found any specific about this case and simple exclude Blocked Items from Integration process using Codeunit 5150.
That was my mistake … because after Go-Live they start to experience issue with blocking Items.
If you doing implementation for Dynamics NAV Connector and using for design you development environment, probably you already have some difficulties to transfer designed maps into your Production Connector.
If you will save into file map created in your Dev Connector and try to create this map from file in Production Connector, you would receive next error message: “ Object reference not set to an instance of an object.”
The issue with custom CRM Entities. Each Custom Entity has unique Metadata ID and when you include your entity in Integration, Connnector add “EntityMetadataId” property into Object Adapted:
And this MetadataId unique per any CRM Organization.
So, here I want to give you one of the methods to decrease headache during update process from Development to Production or Test environments.
CASE 1: Creating Production Integration from Development Connector
Yesterday was released new Featured Pack 7 Connector version.
You can read about release on Team Blog:
Setup and Install Documentation available for public:
http://www.microsoft.com/download/en/details.aspx?id=10381
Installation files can be downloaded from Partner Source site:
Some major new features was included in this release, such as Source filtering or Connecting to CRM with IFD mode.
So, lets read updated documentation, Install new version and … Good Luck with testing.
Welcome to WordPress. This is your first post. Edit or delete it, then start blogging!
New Featured Pack 6 for NAV Connector was released.
You can download it from PartnerSource: Dynamics NAV Connector Featured Pack 6 Release
At first look they changed integration for Currencies : instead sych Currencies with existing Rates, they sync Currencies Codes which Connector can meet during Customers synchonisation.
Will try to play more with this release later but I really expected much more from this release … All my customers pretty stable with their currencies and enough sync currency list at the beginnig and not touch anymore.
Have no idea what I can offer clients from this release that he will agree to spend some money for this upgrade …
Yesterday I did initial synchronization from NAV to CRM for 20000 Customers and got next error:
“There is an error in XML document (1, 700)”
SYMPTOMS:
When you open NAV Connector you get error message “Object reference not set to an instance of an object“ and Connector cannot be open.
This usually happen when you try to create new map from file or copy map from another Integration and it’s failed.
SYMPTOMS:
If you have UTC – n Time Zone for your users, then after sync they can see wrong Date in CRM.
For Example:
NAV to CRM Sales Order synchronization:
NAV Sales Line Requested Delivery Date = 08/24/2011
Connector Map for Sales Order Line:
CRM Requested Delivery Date=If(LessThan(Sales Order LinesSales Order LineRequested Delivery Date, Date(1900, 1, 1)), Date(1900, 1, 1), Sales Order LinesSales Order LineRequested Delivery Date)
User Time Zone setup in CRM:
After sync you will have in CRM Requested Delivery Date = 08/23/2011
RESOLUTION:
Math is very simple:
(NAV)08/24/2011 00:00:00 – 5Hours(User Time Zone) = (CRM)(08/23/2011)
To resolve it we need to modify Mapping logic in Connector – add hours to NAV Date:
CRM Requested Delivery Date = If(LessThan(Sales Order LinesSales Order LineRequested Delivery Date, Date(1900, 1, 1)), Date(1900, 1, 1), AddHours(Sales Order LinesSales Order LineRequested Delivery Date,6))
As result of this mapping we have:
(NAV)08/24/2011 06:00:00 – 5Hours(User Time Zone) = (CRM)(08/24/2011)
I added only 6 hours to my date because all my users have -5 Hours Time Zone. You should probably put different number which will work for you.
Please NOTE: You cannot just copy mapping formula from here to your map, you have to retype it manually. The reason of this – function LessThan. Connector Team decided create two functions with the same name, one for Dates one Decimals. As result, you cannot just type this function, you must choose it from list. Pretty annoying but this is reality …
[UPDATE]
According MSFT Team, here is the out of box Connector function “GetUtcTime” which allow to avoid issue above.
So, date mapping should looks a bit different:
CRM Requested Delivery Date = If(LessThan(Sales Order LinesSales Order LineRequested Delivery Date, Date(1900, 1, 1)), Date(1900, 1,1), GetUtcTime(Sales Order LinesSales Order LineRequested Delivery Date))