64 Saturday, May 28, 2016 |
Msxrmtools Publisher
Publisher at Msxrmtools

Conditional Formatting in the Outlook CRM Client

Order Management : Order Status

  • Open
  • Fullfilled
  • Cancelled

CRM Rules! for Microsoft Dynamics CRM 2011: Intro Demo #1

Microsoft Dynamics CRM 2013 Customization New Features - Customizable Tool Tips

Form events in MS CRM?

  • OnLoad Event
    • The OnLoad event occurs after the form has loaded.
    • It cannot prevent the window from loading.
    • Use the OnLoad event to apply logic about how the form should be displayed, to set properties on fields, and interact with other page elements.
  • OnSave Event
    • The OnSave event occurs when:
    • The user clicks the Auto save button button in the lower right corner of the form, even when there is no changed data to be saved.
    • Code executes the Xrm.Page.data.entity.save method, even when there is no changed data to be saved.
    • The user navigates away from the form and there is unsaved data in the form.
    • With auto-save is enabled, 30 seconds after data has changed and there is unsaved data in the form.
    • Code executes the Xrm.Page.data.save method and there is unsaved data in the form.
    • Code executes the Xrm.Page.data.refresh method passing a true value as the first parameter and there is unsaved data in the form.
  • Field OnChange Event
    • The OnChange event occurs when:
    • The data in a form field has changed and focus is lost.
    • Radio buttons or check boxes clicked.
    • Calling Xrm.Page.data.entity attribute.fireOnChange method.
    • The OnChange event does not occur if the field is changed programmatically using the setValue method. If you want call attribute.fireOnChange method.
  • Tab TabStateChange Event
    • The TabStateChange event occurs when the DisplayState of the tab changes due to user interaction or when the setDisplayState method is applied in code.
    • Use this event when you wish to change the src property of an IFRAME within the tab.
    • If you set the IFrame src property in the OnLoad event for an IFRAME within a collapsed tab, the value will be overwritten when the tab is expanded.
  • IFRAME OnReadyStateComplete Event
    • The OnReadyStateComplete event indicates that the content of the IFRAME has loaded and can be accessed in code.
    • Use this event when referencing IFRAME controls within your scripts.
  • Lookup Control PreSearch Event
    • The lookup control has a PreSearch event that occurs just before the control launches a dialog to search for records.
    • There is no UI to set event handlers for this event.
    • You must use the addPreSearch and removePreSearch methods on the lookup control to add or remove event handlers for this event.
  • OnProcessStatusChange Event
    • This event occurs when the status of a process instance changes.
    • Use the Xrm.Page.data.process.addOnProcessStatusChange method to add event handlers for this event
    • and the Xrm.Page.data.process.removeOnProcessStatusChange method to remove them.
  • OnStageChange Event
    • This event occurs when the user clicks the Next Stage or Move to previous stage buttons in the user interface
    • or when a developer uses the Xrm.Page.data.process.moveNext or Xrm.Page.data.process.movePrevious methods.
    • You can’t cancel the stage change using code in a handler for this event.
  • OnStageSelected Event
    • This event occurs when a stage of a business process flow control is selected.
    • You can’t cancel the stage selection using code in a handler for this event.
  • Knowledge Base Search Control Events
    • The knowledge base search control can only be added to forms for organizations that has the knowledge management feature enabled. This control has two events (OnResultOpened and OnSelection) that developers can programmatically assign event handlers to.
  • Subgrid OnLoad event
    • Subgrids load asynchronously from the form so you can’t reliably get access to the data in the subgrid in the form OnLoad event. But you can set an event handler for the OnLoad event of the subgrid.
    • This event will occur each time the data in the grid is refreshed, this includes when users sort the columns of the grid.
  • Editable Grid Events
    • OnRecordSelect
      • The OnRecordSelect event occurs when a single row (record) is selected in the editable grid. This event won't occur if a user selects different cells in the same row, or selects multiple rows.
    • OnChange
      The OnChange event occurs when a value is changed in a cell in the editable grid and the cell loses focus. This event can also occur when an attribute value is updated using the setValue method.
    • OnSave
      • The OnSave event occurs before sending the updated information to the server, and when any of the following occurs:
        There is a change in the record selection.
        The user explicitly triggers a save operation using the editable grid’s save button.
        The user applies a sort, filter, group, pagination, or navigation operation from the editable grid while there are pending changes.

Microsoft Dynamics CRM Online - Mail Merge

This video will guide you through creating mail merge documents from Microsoft Dynamics CRM Online. First we create a mail merge template. Then we walk through how to create a Quick Campaign Email using mail merge. Finally, we show how to create mailing lables using mail merge.

Microsoft CRM 2011 -- Building a Dashboard

Dynamics CRM 2011 - Driving Sales Productivity

Demonstration of how Microsoft Dynamics CRM 2011 can be used to drive sales productivity.

Microsoft Dynamics CRM Online 2015 Update 1 - CRM SDK New Features

Microsoft Dynamics CRM 2011: Multiple Forms

Demonstration of how to add additional forms for entities in Dynamics CRM 2011
 
 

 

What is the difference plugin and workflow?

  1. Plugin is not intend to fire or execute logic while timeout or subscription with recursive.
  2. Plugin supports all most every message other than creation, status change, and assignment, attribute change and deletion.
  3. Plug-inis not bound by the features and logic patterns that the workflow editor supports.
  4. Elevations on privilege which the process is execute on behalf of another user but in workflow users they can create their own.
  5. We can’t stop plugin process execution like work flow stops using stop workflow step.
  6. We can’t execute plugin process either manually or on demand.
  7. Only developers can implement the plugin.
  8. Plugin support both offline, online and on-premise which means sandbox.
  9. Immediate effect on result.
  10. Needs a synchronous action to happen before or after an event occur.
  11. Can be triggering either child pipeline or parent pipeline.