Bring your code 2 life

Via browser or my REST Client app I was not able to upload files with sizes greater than 300KB. After some research I found out that some coworder mistakenly changed the web.config in a wrong manner. He set the value maxallowedcontentlength for the requestfiltering section to around 300KB. Luckily, SharePoint Health is smart to find this kind of errors. Resetting the line in the web.config helped: The requestLimits element has a maxAllowedContentLength attribute and its value is set to 2147483647. => according to Microsoft MSDN.

Recently I tried to get some custom REST Services for SharePoint working but had the Problem that my DateTime and Guid properties or parameters always gave me back empty values or even the error Bad Request. Then I found out that the string representation of an empty Guid or even null value must be the Guid.Empty value '00000000-0000-0000-0000-000000000000' otherwise you might get a Bad Request or some strange behavior. Even worse was the transfer of an empty date parameter or property. I thought it will be good enough to have like this string representation for an empty date field "". Or even most common schemas like "2010-5-5" and so would not work and always give back a Bad Request message. Then after trying to post back a date value from my WCF REST Service to the client I found out that the expected format looks something like this: "\/Date(946645200000+1100)\/" After some research I now know that this is due to how .NET converts the ...

Today I tried to re-provision the CRM 4.0 MUI after an UR21 Upgrade coming from UR10. Sadly, every time trying to provision the language I retrieved an error. Turning on the error log this allowed me to find the real problem that I was facing here: Violation of PRIMARY KEY constraint 'XPKLocalizedLabel'. Cannot insert duplicate key in object 'MetadataSchema.LocalizedLabel'. The error occured while trying to execute the follwoing SQL Statement: INSERT INTO LocalizedLabel ( LocalizedLabelId, LanguageId, ObjectId, ObjectColumnName, Label, InProduction, CustomizationLevel ) VALUES ( '0bd8a218-2341-1033-898a-0007e9e17ebd', 1033, '0ad8a218-2341-db11-898a-0007e9e17ebd', 'DisplayName', 'Preferred Customer', 1, System ) checking on web search I found this page: http://msdn.microsoft.com/en-us/library/ee704626.aspx The page specifies the following allowed values for the CustomizationLevel column: Value Description 0 Indi...

Today I tried to migrate a custom CRM 4.0 SQL report to the a CRM 2013 SQL report. In the report designer I hit the preview button and received the following error: TITLE: Microsoft SQL Server Report Designer ------------------------------ An error occurred while executing the query. An insufficient number of arguments were supplied for the procedure or function dbo.fn_GetLocalizedLabel. OK, this means the SQL function "fn_GetLocalizedLabel" in CRM 4.0 used to have one parameter less than in CRM 2011 or CRM 2013. After comparing the paramter signatures with the SQL database version I found this definition: function [ dbo ].[ fn_GetLocalizedLabel ] (     @ ObjectId uniqueidentifier ,     @ ColumnName nvarchar ( 255 ),     @ LabelTypeCode int ,     @ LanguageCode int ) returns nvarchar ( 255 ) as begin     declare @ LocalizedLabel      nvarchar ( 255 )   ...