In Dynamics CRM Advanced Find, Querries can be built for various conditions \ for various filter criteria. But, “Not In” type queries cannot be built and it doesn’t work with OOTB querying. Cobalt has a cool feature which allows users to make “Not In” \ “Does Not Have” types of queries in Advanced Find and for Views.
One Account can have many Cases. Dynamics CRM can display all the “Accounts which has Cases” in Advanced Find\Views. But, Dynamics CRM cannot display all the “Accounts which has no Cases” using Advanced Find\Views.
Use “Does Not Contain Data” clause for filtering Continue reading ““Not In” \ “Does Not Have” Query in Dynamics CRM – By Cobalt”
This is to introduce you Salesforce Marketing Cloud Connector for Dynamics CRM and to give you a brief description on the purpose of using it and to explain advantages of combining Salesforce Marketing Cloud and Dynamics CRM for Marketing purposes. Following navigation item shows after the connector installation in Dynamics CRM.
What is Salesforce Marketing Cloud?
Marketing cloud is a digital marketing platform to reach each individual customer in different ways by delivering the right message at right time in a very personalized way in the process of marketing. Interaction can be created through Emails, Social media, Mobile and Web for marketing campaigns in different techniques such as surveys, promotions, questionnaires, advertising and many more techniques. Continue reading “Salesforce Marketing Cloud Connector for Dynamics CRM”
Relationships are one the strengths in CRM and it was there from its beginning and Connections introduced with CRM 2011. Recently I had to decide whether the use CRM connections or relationships to implement a feature in CRM and I found pros and cons of using each as solutions. Also I have given my ideas according to my experience with them.
My personal preference is goes to Relationships as it is steady and it clearly expresses the association type among entities. Relationships can be directly seen from each entity with its type even in the forms and it can be easily used in reports and in views. Mostly the relationships are decided at the time of designing the CRM solution and the code (e.g. proxy class) has to be generated to use it in plugins and custom workflows when you are using early bind method. Also if any entity is related to many other entities for different functionalities, there is a possibility of having empty values in CRM records\forms. in that case developers has some more work to hide them or handle blanks in each lookup.
With connections the user can use the association between two records only when needed. But there should be an additional step to be taken, that is relationship role. Also when any connection is retrieved developer has to get the relationship role first. Connections are very useful when the relationship between two entities are rarely used and specially when a scenario having a many to many associations as in a network.
I found a good thread on this initiated by Dinesh and click here to open it;
With CRM 2013, some important features have been released under Client API. Most of them are good solutions to very practical scenarios that CRM developers faced in past releases. This is an attempt to present the official video and to summarize SDK features for the reference.
The video can be found in the following link as well.
Following table summarizes New SDK features under CRM 2013.
Continue reading “CRM 2013 SDK New Features – Client API”
CRM On-Premises version has been released recently by Microsoft Dynamics and you will find all the updates and downloads from following link.
Here’s the very first screen I got after installing and configuring my newest CRM 2013 application.