“Not In” \ “Does Not Have” Query in Dynamics CRM – By Cobalt

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.

The Problem:

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.

query1

Solution:

Use “Does Not Contain Data” clause for filtering Continue reading ““Not In” \ “Does Not Have” Query in Dynamics CRM – By Cobalt”

Advertisements

Send Bulk Emails and Track Stats Back to CRM with PowerMailChimp

MailChimp Integrations

Maintaining campaigns, marketing lists and sending emails to different marketing lists in bulk are usual processes in Marketing. Dynamics CRM provides a useful set of functionalities under Marketing.

MailChimp provides lot of web based features including Email designer, Email Template Creator, integration with different web applications, maintaining campaigns, create campaigns using mobile etc…
http://mailchimp.com/

MailChimp Integrations
MailChimp Integrations

PowerMailChimp connects Dynamics CRM and the MailChimp, simply it acts as MailChimp CRM Integration tool.

http://www.powerobjects.com/powerpacks/powermailchimp/

You can create marketing campaigns, maintain static or dynamic marketing lists to send offerings, newsletters, notices etc… from Dynamics CRM itself. Also MailChimp can be used to design your email templates or newsletter templates very easily and send those emails or  newsletters using your own templates in MailChimp. Statistics such as successful deliveries, opens, bounces and unsubscribes can be seen from the CRM itself.

Its simple,  watch following video in YouTube;

MailChimp integration with Microsoft Dynamics CRM 2015

Dynamics CRM 2015 Copy Price List

Having a large number of products under a price list means, there are large amount of price list items associating with them. Whenever a new price list is added to the CRM, price lists items are to be created even if the prices are same in that price list.

“Copy Price List” is to duplicate an existing price list with a new name, new start date and a new end date with its price lists items. If there are any changes to be done to any price list items users can do that manually while the other items remaining the same.

Source Code and the Managed Solution available in CODEPLEX

The solution is perfect when a system has large number of products with many price lists adding but price list items are getting rarely changes. This has packaged to work with CRM 2015 directly but using the source code that can be used with previous versions of CRM as well.

Go through the following the steps to install it and use it !

Continue reading “Dynamics CRM 2015 Copy Price List”

Connections VS Relationships in 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;