After upgrading to CRM 2013, we wanted to hide the quick create form from the end users. This can be done through the entity customization’s Data Services section

Bye.
After upgrading to CRM 2013, we wanted to hide the quick create form from the end users. This can be done through the entity customization’s Data Services section

Bye.
Nice post !
Seriously. Where have the radio buttons gone for “Two Options” type bit fields in CRM 2013?!
View original post 307 more words
Recently we upgraded our CRM 2011 solution to CRM 2013.
After upgrade labels for few of the attributes were not displaying properly.

Changing the section’s width for the label area resolved this.

After publishing the change à

Helpful post :-
http://www.powerobjects.com/blog/2014/03/05/adjusting-crm-2013-field-label-sizes/
Bye.
Hi,
We were using the below function in CRM 2011 for disabling all the fields in the form.
function makeAllAttributesReadOnly() {
var attributes = Xrm.Page.data.entity.attributes.get();
for (var i in attributes) {
var myattribute = Xrm.Page.data.entity.attributes.get(attributes[i].getName());
var myname = myattribute.getName();
Xrm.Page.getControl(myname).setDisabled(true);
}
}
However this function in CRM 2013 was giving us setDisabled field is undefined JavaScript error.
As it turned out it was because of the StateCode (Status) field in CRM 2013.

Modifying the above code to leave this particular field resolved the issue.
function makeAllAttributesReadOnly() {
var attributes = Xrm.Page.data.entity.attributes.get();
for (var i in attributes) {
var myattribute = Xrm.Page.data.entity.attributes.get(attributes[i].getName());
var myname = myattribute.getName();
if(myname == "statecode")
{
return;
}
Xrm.Page.getControl(myname).setDisabled(true);
}
}
Hope it helps.
Hi, after importing our CRM 2011 solution into CRM 2013 org, we faced one strange issue in one of the attributes.
As we can see below the text box (ellipsis) was missing for Client Alias 3 attribute.

Opening the form for customization, and checking the field details didn’t reveal anything different.

Then we gave it a try by moving the Owner Field (not visible by default) to bottom of that section beneath Client Alias 3 field and published the customization.

Strangely enough the text box start appearing for the Client Alias 3 field.

Still wondering what would be the possible reason behind this issue.
Bye.
Recently we had a requirement to add checkboxes in our mail merge templates. There are two options of adding checkboxes one is adding them as a symbol if we want user to check them after taking print out or if we want them to be clickable inside the word document itself using content control.
Check this helpful post
Hope it helps.