62 Monday, May 30, 2016 |
Msxrmtools Publisher
Publisher at Msxrmtools

Microsoft Dynamics CRM Spring '14 Overview of Unified Service Desk

Microsoft Dynamics CRM Working with Solutions

Order Management : Fields on the Order Form contd.

  • Shipping Information
    • Shipping Method: Shipping method for deliveries sent to this address.
    • Payment Terms: Payment terms to indicate when the customer needs to pay the total amount.
    • Freight Terms: Freight terms to make sure shipping charges are processed correctly.
  • Addresses
    • Bill to Address: Complete Bill To address.
    • Ship To: Whether the products included in the order should be shipped to the specified address or held until the customer calls with further pick-up or delivery instructions.
    • Ship To Address: Complete Ship To address.
  • Sales Information
    • Opportunity: Related opportunity linking the data for the order and opportunity for reporting and analytics.
    • Quote: Related quote linking order data and quote data for reporting and analytics.
    • Potential Customer: Customer account or contact providing a quick link to additional customer details, such as account information, activities, and opportunities.

CRM 2011 Overview - Microsoft Dynamics CRM 2011

This video provides a high level overview of the sales, marketing and service functionality in Microsoft Dynamics CRM 2011.

The overview includes Dashboards, Leads, Accounts, Contacts, Campaigns, Cases and KB Articles.

Microsoft Dynamics CRM 2013 for Tablets

Understanding Entity Change Tracking in Microsoft Dynamics CRM

In CRM integration projects, your business requirements often dictate that you should only retrieve those transaction records that have been recently created or modified in your source system since last integration. When your CRM system is the source, you would typically use CRM FetchXML query to pull data from the CRM system by comparing the record's modifiedon field, which is not a solution that is reliable enough and may not perform well when the source entity has a significant number of records.

To address this particular challenge, CRM Online 2015 Update 1 release introduced the Change Tracking feature, which offers a reliable and efficient way to track transactional data changes for CRM entities.

Turn on Change Tracking

In order to track data changes of a particular entity, you have to first turn on "Change Tracking" option for the entity. You would do so by going to the entity's customization page, and tick "Change Tracking" option under "Data Services" section.

Retrieve Changes

After Change Tracking has been enabled for the entity, you can use CRM SDK RetrieveEntityChangesRequest message to pull changes from CRM server. The following is a snippet that demonstrates how to pull changes from the CRM server.

 using (var service = new OrganizationService(crmConnection))
{
var request = new RetrieveEntityChangesRequest();

// Set which entity to get changes for.
request.EntityName = "account";
request.Columns = new ColumnSet("accountnumber", "name", "creditlimit");

// Set paging preferences.
request.PageInfo = new PagingInfo() { Count = 5000, PageNumber = 1 };

// Set change token returned from last pull.
request.DataVersion = changeToken; // set to null or remove this line to do an initial pull

// Get the changes.
var response = (RetrieveEntityChangesResponse)service.Execute(request);

// TODO: Process all the changed records (see the code snippet below)

// Save the token somewhere for future use
changeToken = response.EntityChanges.DataToken;
Console.WriteLine(changeToken);
}

Walk through Changes

After retrieving the changes, you will get two types of results. The first type of result is the newly added or updated records, and the second one is for the records that have been deleted since the last pull.

// Replace the TODO line in the above snippet with the following code
foreach (var change in response.EntityChanges.Changes)
{
if (change.Type == ChangeType.NewOrUpdated)
{
var changedItem = (NewOrUpdatedItem)change;
Entity newOrChangedEntity = changedItem.NewOrUpdatedEntity;
// TODO: Process new or updated entity record
}
else if (change.Type == ChangeType.RemoveOrDeleted)
{
var deleteditem = (RemovedOrDeletedItem)change;
EntityReference deletedEntityReference = deleteditem.RemovedItem;
// TODO: Process deleted entity records
}
}

Note that the returned NewOrChangedEntity is an instance of Entity class, while the RemovedItem (the deleted record) is an instance of EntityReference class.

Some Closing Notes

There are a few things that you should be aware when using this feature:

  • The "Change Tracking" option is an entity-level setting. It has to be enabled for the entity before you can use RetrieveEntityChangesRequest to pull data. If the option is not enabled, and you try to use this feature, you will get an error message telling you "Entity: account isn't enabled for change tracking" where account can be any entity name that you are working with.
  • Due to the fact that the "Change Tracking" option works at entity level, you would need to keep track of the change token for each entity individually. There is no organization level tracking token.
  • There is one special situation that you should watch out for. Suppose there is a newly added record after last pull and it was deleted before the new pull, you will get the record in the Delete result set, which you may not have knowledge about it.
  • In the case that you have selected to return a lookup field, the field's Name property is not returned.
  • When change collection has more records than the page size that you have specified, you would have to page through the change collection.
  • Based on my preliminary testing, it appears that CRM keeps multiple token versions, which is really nice. However, I imagine keeping too many versions on the server side would not make sense as each version would consume a certain amount of database space. There must be a limit in terms of how many versions are kept on the CRM server side. It could be either a time-based limit (say 90 days probably, which could still be a lot of change versions if I keep pulling from the server every 30 seconds) or a number-based limit. This is something that has yet to be confirmed.
  • When you retrieve changes using this feature, you will get the records in their current status, the old values before the change are not returned.
  • The user account needs to have organization level read (or so-called "Root Read") privileges for the concerned entity in order to uses RetrieveEntityChangesRequest to retrieve changes.
  • More details about this feature can be found at the CRM SDK documentation page: Use change tracking to synchronize data with external systems.

Disassociate Records in Dynamics CRM - Late Bound

Following example demonstrates how to disassociate record in dynamics crm

public static void DisassociateContactsToAccount(EntityReference contact, EntityReference account, IOrganizationService service) {

// Creating EntityReferenceCollection for the Contact
EntityReferenceCollection relatedEntities = new EntityReferenceCollection();

// Add the related entity contact
relatedEntities.Add(contact);

// Add the Account Contact relationship schema name
Relationship relationship = new Relationship("contact_customer_accounts");

// Disassociate the contact record to Account
service.Disassociate(account.LogicalName, account.Id, relationship, relatedEntities);

}

Product Catalog : Write-in Products

Write-In products are intended for products or services not currently in the product catalog.

Examples:

  • Miscellaneous charges or fees
  • Credits. To enter a credit, add a Write-In line item with a negative number in the Price Per Unit field and a value of 1 in the Quantify field.

Apple Leak Confirms 'All Glass' New iPhone

Last month the world’s most accurate Apple AAPL tipster revealed the company is working on a radical ‘all glass’ new iPhone. The news was met with cynicism and excitement in equal measure, and now a major Apple supplier has confirmed it…

Speaking at its annual shareholder meeting Allen Horng, chairman and chief executive of long time iPhone chassis maker Catcher Technology , said Apple will make its 2017 iPhone using a glass casing.

Breaking down the radical shift, Horng said using a glass chassis would prove expensive and that Catcher requires “advanced processing technology” to pull it off. He also explained that the chassis would need to be reinforced by a metal frame.

The move is expected to go far beyond Apple’s previous glass backed iPhone 4 and iPhone 4S and rival Samsung’s recent Galaxy S and Note lines by using a single piece of glass for the whole exterior. Pull that off and Apple would certainly have a smartphone that looked like no other.

But it isn’t all good news.

Horng said that “As far as I know, only one [iPhone] model will adopt glass casing next year” and, given the range’s pricing, that would suggest the iPhone 8 Plus (Apple is expected to skip the iPhone 7S moniker for the iPhone’s 10th anniversary) or even the hotly rumoured iPhone Pro.
source:Forbes

Microsoft Dynamics CRM Online 2015 Update 1 - Yammer Integration New Features

Creating Custom Entities - Microsoft Dynamics CRM 2011

This video provides an overview of how to extend Dynamics CRM 2011 to include additional functionality or business processes.

In this overview we show how you can add a custom entity to track Samples that you want to send out to customers.

Color Grid for Dynamics 365

Color Form for Dynamics 365