Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Like this presentation? Why not share!

Crm 4.0 customizations basics

on

  • 3,368 views

 

Statistics

Views

Total Views
3,368
Views on SlideShare
3,368
Embed Views
0

Actions

Likes
0
Downloads
15
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Crm 4.0 customizations basics Crm 4.0 customizations basics Presentation Transcript

  • CUSTOMIZATION BASICS
  • The terms "Table" and "Column" (or "Field") are oftentimes used in reference to data that is processed within business applications. However, because Microsoft Dynamics CRM's foundation is built upon the use of XML, the following terms are used:
    • Entity instead of Table
    • Attribute instead of Column or Field
  • SQL Limitations
    Custom attributes that are added to an entity are stored in an extension table for that entity. Although a Microsoft SQL Server table is reserved for entity extensions on each entity, the number of attributes you can add to the table is not infinite. Microsoft SQL Server allows up to 1024 columns per table and the amount of data stored in any row cannot exceed 8060 bytes.
  • Security Role(s)
    Settings > Admin > Users > Select User > Roles >
    Allow user(s) to Create, Read, Write, Delete, Append, Append To, Assign, Share
  • Editing an entity:
    From the web client: (User enabled security)
    Navigate to Settings > Custom Entities > Select the entity to edit: (Lead) > More Actions > Edit
    General:
    • Allow Duplicate Detection
    • Offline Availability
    • Select where the entity is displayed
  • Editing an entity:
    Forms and Views:
    • Form – “The main application form.”
    • Entity home page.
    • Multiple Views – be sure to change all that apply.
    • Standard view
    • My view
    • Advanced Find
    • Preview – use prior to publishing and re-arranging.
  • Editing an entity:
    Forms and Views:
    • Form – “The main application form.”
    • Entity home page.
    • Add a Tab
    • Add a Section
    • Add Field
    • Add an IFRAME
    • (Share point)
    • Re-arrange
  • Add a field:
    Create a new Attribute/field:
    Add an existing field:
    • Attributes > New >
    • Display Name
    (set prefix of “new”)
    • Requirement Level
    • Searchable
    • Type:
    • Format
    • Max. Length
    • IME Mode
    • Description
  • Adding a Attribute/Field
    Type:
    • nvachar: Text. You must specify the type of text: Text, Text area, E-mail, URL, or Ticker Symbol, and the maximum length. Text attributes are limited to 4000 characters
    • picklist: Drop-down list. You must specify the values to show in the list, and the default value.A Picklist attribute is different from a Lookup attribute. A Lookup attribute is displayed when a relationship attribute is added to the entity form.Picklist attributes do not allow text input.
    • bit: Bit. An attribute with only two possible values. You must specify the two values and the default value.
    • int: Integer. You must specify the format of the field, and the minimum and maximum values.
    • float: Float. A number field that includes decimal places. Decimal places are supported between 0 and 5 digits after the decimal.
    • money: Money. You must specify the number of decimal places to display, and the minimum and maximum values. Decimal places are supported between 0 and 4 digits after the decimal
    • ntext: Memo. You must specify the maximum length. Attributes of the ntext type are limited to 5000 characters
    • Datetime:date / time
  • Deleting an Attribute:
    Because of the built-in dependencies between attributes for each entity, the system has the following guidelines in place that control which attributes can be deleted:
    • Only custom attributes can be deleted.
    • System attributes cannot be deleted.
    • If a custom attribute that you want to delete has been published on the entity's form, you must remove the attribute from the form and publish the form before you can delete the attribute.
    • The attribute must be removed from any reports that contain the attribute.
  • E-Learning:
    http://dynamics.microsoftelearning.com/eLearning/courseDetail.aspx?courseId=85871
    Customer Source
  • Workflow Introduction:
  • To view changes:
    In order for Microsoft Dynamics CRM to access the entity, you must exit the web application and launch it again before you can access the entity.
    Don’t Forget To Publish.