Error when converting Lead to Opportunity in CRM 3.0
We just did several custom attributes and fields in the Lead and Opportunity forms.
Now, when we try to convert the lead to opportunity, we get the following error:
Server Error in '/' Application.
--------------------------------------------------------------------------------
The string was not recognized as a valid DateTime. There is a unknown word starting at index 3.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.FormatException: The string was not recognized as a valid DateTime. There is a unknown word starting at index 3.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Can you check the date settings of the user you're using to try and promote the Lead and compare it with the date settings of the CRM server itself? They could be out of whack which might be causing the issue.
So, when logged in as user -> Tools -> Options -> ?? How should I check date settings for user?
And for server -> Org Setting -> System Settings (which works now, thanks to you) -> Calendar?
I think I did make changes to the system settings, so this might make sense...
Other things I made changes to around the time this issue came up:
- Tried to install a cloning tool, which didn't work, so I undid all changes to config files.
- mapped all custom fields between leads and opportunities
Yes...The Tools-->Options--Formats Tab-->Current Format to check the user settings.
Administration-->System Settings-->Formats Tab-->Current Format to check the organisation setting.
The mapping could potentially be causing an issue as well if the settings are different. You may find that if the settings are the same the mapping will work fine but if they're different then there could be issues.
There are a lot of fields in the forms with dates that are mapped, so I guess we can do start removing them working backwards to find the source...
Also, not sure if this helps, but since I was messing with the web.config file, I am not able to open the web client on my computer, but it's still working on the other computers...
Excellent! I just hit 'Generate Mappings' which took us back to a time when we knew it was working.... Thankfully there were only 21 mappings we had to do manually, so this shouldn't take long to diagnose...
So, looks like it could be either:
- target field attribute was nvarchar, when source was datetime (or something to that effect)
or
- Source was system attribute and target is custom attribute?
Thought you might also be interested to know... I figured out the issue I was having with not being able to open the Web Client. Turns out my attempts were being thwarted by a pesky Google toolbar...
Microsoft Dynamics is a line of enterprise resource planning (ERP) and customer relationship management (CRM) software applications. Dynamics can be used with other Microsoft solutions, such as SharePoint, Yammer, Office 365, Azure and Outlook. Dynamics ERP comprises a group of enterprise-resource-planning products includes Dynamics AX (formerly Axapta), a multi-language, multi-currency enterprise software with business management features for financial, human resources, and operations management; Dynamics GP (formerly Great Plains Software); Dynamics NAV (formerly Navision) for financials, supply chain, and people; Dynamics SL (formerly Solomon IV)for project-driven organizations; Dynamics C5 (formerly Concorde C5) for manufacturing, supply chains, analytics and electronic commerce; and Dynamics CRM.
Can you check the date settings of the user you're using to try and promote the Lead and compare it with the date settings of the CRM server itself? They could be out of whack which might be causing the issue.
MH