1. #CRMUGSummit | #INreno15 #CRMUGSummit RELATIONSHIPS - HOW MANY PARENTS CAN YOU HANDLE? Glen Wolinsky, Miller & Martin PLLC

2. #CRMUGSummit | #INreno15  Law firm founded in 1867 in Chattanooga, TN  More than 250 employees – 130+ Attorneys – 50+ Practice areas  Three Locations – Chattanooga, TN – Nashville, TN – Atlanta, GA 2 INTRODUCTIONS

3. #CRMUGSummit | #INreno15  With Miller & Martin since 1999  Lead Applications Developer  BIO: – 2 years of Microsoft Dynamics CRM experince in administration and development – 18+ years of development experience including VB.Net, ASP.Net, HTML, SQL, SSIS, SSRS, Javascript, and RPGII (dating myself) – Develop and maintain centralized practice management systems and integration systems linking to other products 3 INTRODUCTIONS – A BIT ABOUT ME

4. #CRMUGSummit | #INreno15  Data – Show the setup configuration for a shared child entity. – Handle form display differences for standard & Quick Create forms depending on the parent. – Handle required-field issues with the parent reference on forms.  Child Reassignment – Demonstrate the use of workflow to reassign/move the child record to a new parent. OUR OBJECTIVES

5. #CRMUGSummit | #INreno15  Matter Intake – Two parent entities Matter Matter Intake – One child entity Party: a person, business or legal entity involved in a matter.  Party info is gathered on the Matter Intake and then moved to Matter when Matter is created. 5 BUSINESS NEEDS DEFINED Party Matter Intake Matter Intake

6. #CRMUGSummit | #INreno15 MATTER INTAKE WITH MATTER PARTIES DEMONSTRATION

7. #CRMUGSummit | #INreno15

8. Enable Quick Create Form By configuring the entity to Allow quick create and setting the Field Requirement to Business Required, you instruct the system to use the Quick Create form when adding record from a sub-grid.

9. #CRMUGSummit | #INreno15

10. Standard Form Setup Using the basic form setup with no modification shows BOTH parent reference fields on the form. While the current parent is filled automatically, the unused parent can be confusing and even dangerous for the user. BOTH parent fields are required! However, since the Matter has not yet been created, the system will not allow you to save the record -- even with a valid parental Matter Intake.

11. #CRMUGSummit | #INreno15 Partial Solution By making BOTH parent fields READ-ONLY, CRM mercifully ignores the REQUIRED setting and allows you to save the record. This is our preferred setting for parent fields as it prevents the user from changing either parent field to an invalid value rendering this Party record meaningless at best. Since CRM takes care of properly assigning the parent based on the context of the add request, this is the safest method for data integrity. The only thing is that the blank Matter field will almost certainly generate a Help Desk call as it’s blank; marked as required; but locked to where the user cannot access it.

12. #CRMUGSummit | #INreno15 Best Solution Since Quick Create forms do not allow Business Rules, you have to use Javascript to adjust the form for clarity. This routine that runs on the PageLoad event will hide whichever parent field is NOT valid for the current usage. In other words, if this Party is created for the Matter Intake parent, then the Matter parent field will be hidden.

13. #CRMUGSummit | #INreno15 The Result Now, we have a nice, clean form for the user that won’t cause any confusion.

14. #CRMUGSummit | #INreno15

16. Final Processing Now we run the workflow that creates the new Matter from the Matter Intake and relocates the Matter Party records.

17. #CRMUGSummit | #INreno15

18. New Matter The new Matter has been created from our workflow and the Matter Parties have been moved from the Matter Intake record.

19. #CRMUGSummit | #INreno15 What Became of the Matter Intake Record? Since we want to keep a history of all our Matter Intake activity, we: 1.Deactivate the Matter Intake record, 2.As we move the Party records to the Matter, I “rollup” the text of each party into a multi-line textbox on the Matter Intake form. This provides a history without duplicating the Party records in the system.

20. #CRMUGSummit | #INreno15 QUESTIONS 20

21. #CRMUGSummit | #INreno15  Glen Wolinsky – Email: gwolinsky@millermartin.comgwolinsky@millermartin.com – LinkedIn: www.linkedin.com/in/glenwolinskywww.linkedin.com/in/glenwolinsky – Twitter: @glenwol1  Please fill out your survey.  Contribute! – CRM User Group: www.crmug.comwww.crmug.com  Need Form Tasks in your workflow? Don’t miss my next session! – DEV11 – Workflows: Gathering Form Info And Visual Status 21 THANK YOU!