Asked by:
Whole number field formatted as timezone in CRM 2013 SP1UR1 gives error on saving

Question
-
Hi,
I added a whole number field formatted as time zone to the appointment form and when I save the record I get an error saying
Crm Exception: Message: An unexpected error occurred., ErrorCode: -2147220970, InnerException: System.InvalidCastException: Unable to cast object of type 'Microsoft.Xrm.Sdk.OptionSetValue' to type 'System.IConvertible'.
This error is coming from the timezone field and only happens when I have data in the field. Has anyone seen this?
Thanks
Rickard Norström Developer CRM-Konsulterna
http://www.crmkonsulterna.se
Swedish Dynamics CRM Forum: http://www.crmforum.se
My Blog: http://rickardnorstrom.blogspot.seFriday, February 13, 2015 1:39 PM
All replies
-
there are some plugins attached on create/update of appointment?
My blog: www.crmanswers.net - Rockstar 365 Profile
Friday, February 13, 2015 2:28 PM -
Thanks for helping Guido!
There are, but those are not connected to the field which I just added. The thing only crashes when there's data in the field too so I don't think it's the plugin.
I've run some tests too and on appointment the Update is a sub action of reschedule that seems to be the main operation for some reason.
Regards
Rickard Norström Developer CRM-Konsulterna
http://www.crmkonsulterna.se
Swedish Dynamics CRM Forum: http://www.crmforum.se
My Blog: http://rickardnorstrom.blogspot.seFriday, February 13, 2015 2:35 PM -
More info, the error occurs on pipeline stage 30 of the Book or Reschedule message and the same thing happens in CRM 2015. I've started a thread on connect with URL https://connect.microsoft.com/dynamicssuggestions/feedback/details/1128206/crm-2013-sp1ur1-cant-handle-the-timezone-field
This must be rather new because I've tried it in CRM 2011 UR late and it did not occur there, I haven't tried CRM 2013 RTM though so I can't say if it's a CRM 2013 or a CRM 2013 SP1UR1 issue.
BTW, the 2015 org was a complete vanilla so I've pretty much ruled out custom code as a culprit :)
Rickard Norström Developer CRM-Konsulterna
http://www.crmkonsulterna.se
Swedish Dynamics CRM Forum: http://www.crmforum.se
My Blog: http://rickardnorstrom.blogspot.seFriday, February 13, 2015 3:57 PM -
More info after a bit of testing. This might be isolated to the appointment entity, which is one of the entities that really need a time zone of course. I can have time zone fields on account, contact, task and custom entities, which are the ones I've tried so far.
Please vote on the connect issue posted above so this will be fixed.
Regards
Rickard Norström Developer CRM-Konsulterna
http://www.crmkonsulterna.se
Swedish Dynamics CRM Forum: http://www.crmforum.se
My Blog: http://rickardnorstrom.blogspot.seMonday, February 16, 2015 7:15 AM -
upvoted on connect. Thanks for reporting your tests
My blog: www.crmanswers.net - Rockstar 365 Profile
Monday, February 16, 2015 7:25 AM