Hi,
While specifying Data for one of the multiline column in a ListInstance we wanted to specify New Line in the content.
This is how we specified


The result

Hope it helps..
Hi,
While specifying Data for one of the multiline column in a ListInstance we wanted to specify New Line in the content.
This is how we specified


The result

Hope it helps..
Hi,
Was facing this the above issue while trying to debug the code. The debugger was getting attached properly but it wasn’t showing values for the variables.
Unchecking the following option in the class library project properties fixed the issue

This helpful post.
Bye..
We got this error while importing the solution. This issue is caused by having an optionset with same name but different guid.
The solution is to identify the field and delete it from the org where we are importing.
select name from optionsetview where optionsetid = ‘c0864f8b-2c13-e411-93ed-000d3a800961’ (the 2nd guid)
The helpful post
Bye
In CRM 2013 Microsoft has introduced this new client context method called “getClientUrl”
This is the replacement to the previous method called “getServerUrl” that was present in CRM 2011.
This method was faulty because it always returns the server name in the URL as it is set up in the CRM deployment manager, irrespective of how the host url looks like.
this is issue in scenarios where users might have invoked CRM using the server IP address or fully qualified domain name etc.
because when in the java script we call getServerUrl it does not return the URL with the server name as it was used by the calling the host url, but that of what is stored in the server, which fails , in the situations where the server name is not accessible from the host machine but the IP or fully qualified name.
in order to correct this…
View original post 125 more words
Hi,
We were writing a LINQ query to get the contract record information by passing in the lawyer name. The lawyer is a lookup in the contract record.
So we were using contract.lawyerid.Name field of lookup in our where condition.
However we got the below error while doing so..

It seems like the LINQ Implementation for CRM doesn’t correctly interpret the lookup field’s name if we are using it in the where clause.
The solution was to do a join between the entities and then use the where condition against the lawyer entity username field itself.

Hope it helps..
Fixes some of the navigation issues in CRM 2013..
Gather round children Uncle Ben is going to tell you a story.
Once upon a time Microsoft updated it’s CRM version from CRM 2011 to CRM 2013 and during this process removed the popular left hand navigation and replaced it with a better looking but much harder to use new navigation. Highlights of the new navigation
Top menu disappearing just as you try to go to it (this has been fixed a bit in the latest rollup because it stays there longer)
impossible to find Advanced find button
a smaller command bar with only room for 5 items (bumped up to 7 in the latest release)
To speed this story up, Rockton Software commissioned a contest to see who could create the best solution to help the CRM 2013 navigation. CRM MVP’s from all the land flocked round to battle it in a winner takes all ($5000 reward). You…
View original post 340 more words