Changes to out of the box Querystring Param Names

While upgradation from MSCRM 3.0 to 4.0, one of the common error we find is the changes in the names of the query string params.
In MSCRM 3.0, the name of the query string for id of the record is "oId" and for typename it is "oTypeName". Where as in MSCRM 4.0, the name of the query string for id of the record is "Id" and for type name it is "TypeName".

"oId" in MSCRM 3.0 is changed to "Id" in MSCRM 4.0.
"oTypename" in MSCRM 3.0 is chnaged to "Typename" in MSCRM 4.0.

All the custom code. which reads these query strings might require a changes to query string param names. 

Comments

Post a Comment

Popular posts from this blog

The famous Vanilla story --

This is a weird but true  story ...  A complaint was received by the Pontiac Division of General Motors:  This is the second time I have written you, and I don't blame you for not answering me, because I kind of sounded crazy, but it is a fact that we have a tradition in our family of ice cream for dessert after dinner each night. But the kind of ice cream varies so, every night, after we've eaten, the whole family votes on which kind of ice cream we should have and I drive down to the store to get it.  It's also a fact that I recently purchased a new Pontiac and since then my trips to the store have created a problem. You see, every time I buy  vanilla ice cream, when I start back from the store my car won't start. If I get any other kind of ice cream, the car starts just fine.  I want you to know I'm serious about this question, no matter how silly it sounds: 'What is there about a Pontiac that makes it not start when I get vanilla ice cream, an
Read more

Convert fetchXML to SQL Query in MSCRM 4.0

If for some sane reasons if fetchxml needs to be converted to a SQL Query in MSCRM 4.0, it is possible. It actually requires the below DLL's which are avilable in the folder Server\setup Microsoft.Crm.dll, Microsoft.Crm.Platform.Server.dll and Microsoft.Crm.Reporting.dll The code looks as below : Microsoft.Crm.BusinessEntities.ExecutionContext myContext = new Microsoft.Crm.BusinessEntities. ExecutionContext (OrganizationId from the context); myContext.OnBeginRequest(UserId, false); Microsoft.Crm.Reporting.ReportQueryBuilder myreportQueryBuilderObj = new ReportQueryBuilder(); string Query = myreportQueryBuilderObj.BuildReportQuery(fetchXml, myContext); The query will be returned as string. The Query is not readable but it works, -:)
Read more

Grid Refresh Failed.

When user clicks on the columns which are of type "picklist" in an assocaited view, an error message will be thrown "Grid Refresh failed". The reason for this issues is the data corruption. All the values in picklist should have corresponding values in the stringmap table. If there are records with picklist values for which there is no corresponding values in the string map table, then the generic error will be shown. The grid will show "Grid Refresh failed.". In our case we have cleaned up the data to correct this problem. The way to find out all these records is,,, 1. Go to Advanced find. 2. Select the entity for which this error occurs. (For Ex: Account). 3. Select the column which is of type "picklist". 4. Select the operator as "Does not Equal". 5. In the pop up for selecting the picklist values choose all the values. 6. Click on Find. This query gives all the records which does not have valid picklist values in them. Updat
Read more