MSCRM 2013 Image Data Types SDk

• You can access images via a URL. The URL of the image is a read only value available via the SDK off of the Image as an absolute address. Image URLs behave in a similar fashion to Web Resources and Attachments. The primary difference is that images are returned as binary data and Web Resources and Attachments are returned as base-64 encoded MIME types.
• ImageAttributeMetadata is being added to the MetadataService class. This class inherits from AttributeMetadata and represents the metadata for an attribute of type Image

• Images can be returned as part of FetchXML queries or RetrieveMultiple calls. There will be an option to return binary data, URL, or both.
• Binary data must be requested explicitly. A query that specifies “All” fields would only return the image URL. This accounts for the scenario where a user inadvertently queries all fields on an entity with a large number of images.
• Microsoft Dynamics CRM for Outlook does not have direct support for images in CRM 2013 so images will not be synced. Image fields would be ignored in query results and offline view filters.

MSCRM 2013 Image Data type Storage

• On upload via the web application or SDK, images are validated, resized, and stored as a common binary data format in the CRM database.
• Regardless of upload format, all images are all formatted to JPG on create or update. On average, this puts most images at about 5k at max.
•  The uploaded image is always resized to the minimum size necessary to support CRM 2013 and a smaller sized copy with the same aspect ratio as the original gets stored to the database.
• The bounding box in CRM 2013 is hardcoded for all image fields: 144pixels x 144pixels. This value will be stored in attribute metadata as Height and Width

MSCRM 2013 Image Data Type Data Modeling

• The display name can be set for images but SchemaName is always “entityImage” for any image-enabled entities and cannot be changed. 
• The image data type is not searchable. 
• A PrimaryImageAttribute metadata has been added to the entity. 
• Only a single image attribute can be defined per OOB/custom entities. This helps keep storage in check especially for CRM online customers. 
• PrimaryImageAttribute is set by default to the single “entityimage” attribute when it gets added to a custom entity. This is used to determine what image should be displayed in the header of the form. Note, that the grid does not display these images since that would require a smaller icon. 
•  If there are no image attributes on the specific entity OR the system customizer has selected not to display any image for the entity, the PrimaryImageAttribute value would be set to [None]. 

MSCRM 2013 Image Data Type

In CRM 2011, images are stored in notes as MIME encoded text. As a result, images get converted to a displayable format for every read and no pre-cached thumbnails exist. In CRM 2013, images are being introduced as a first class data type. You can now add images as a field, capture/store images and improve query operations on images.

You can capture and maintain images for User Profile, Contacts and Leads, and Account logos.

Data Modelling

·         Image data type as a field type to the application customization experience.

·         Support for only one Image field per entity.

Storage

·         Image stored as binary data in the CRM database.

·         Resize images server-side to conserve storage space and improve performance.

    § Original image uploaded not saved.

SDK

·         CRUD Operations

   § Support standard CRUD operations of Images the same as any other CRM data type.

   § Reference images via URL- ability to include URL and binary data in a RetrieveMultiple or   FetchXML call. 

MSCRM 2011 Customizable Tooltips

In CRM 2011, tool tips are minimal and typically repeat the display name attribute of the field. These type of tool tips are useful for unlabeled UI, however most form fields have labels assigned to them and users need more information when entering or selecting data. Explanatory tooltips provide helpful text to address known user questions, explain terminology or concepts, and help end-users make good decisions to stay on task.

In CRM 2013, custom tooltips aim to improve the user experience by:

•  Providing information on how to use and complete forms, right on the page.
• Allowing organizations to display their business-specific information and processes to their users right in the CRM forms.

The system customizers can update tool tips when they are customizing an entity or entity attribute. The following points are to be noted:

Attribute Tool Tips
You can display entity attribute “Description” as tool tips on fields, buttons, etc. on existing forms for customizable entities. This will work against OOB and custom attributes.

Form Tool Tips
You can define tool tips to be displayed and the browser determines how the tool tip is displayed and for how long it would get displayed.

Rewritten Descriptions for Use as Tooltips – Refresh Forms
Specifically for Refresh Forms: All descriptions that can be displayed on the forms have now been rewritten for use as customizable tooltips.

Standard Customization Path
You can customize these tool tips simply by editing Description via the Settings > Customization UI> Form editor or field editor.