RootComponent types in solution.xml file in Dynamics CRM 365/2016

In Microsoft Dynamic CRM 2016/365 are you as confused as me when looking at the solution.xml from the solution export? looking at the xml and trying to decode what RootComponent type means what is always a painful experience. This table should simplify things and tell you what Type number relates to what component.

Type	Description
1	Entity
2	Attribute
3	Relationship
4	Attribute Picklist Value
5	Attribute Lookup Value
6	View Attribute
7	Localized Label
8	Relationship Extra Condition
9	Option Set
10	Entity Relationship
11	Entity Relationship Role
12	Entity Relationship Relationships
13	Managed Property
20	Role
21	Role Privilege
22	Display String
23	Display String Map
24	Form
25	Organization
26	Saved Query
29	Workflow
31	Report
32	Report Entity
33	Report Category
34	Report Visibility
35	Attachment
36	Email Template
37	Contract Template
38	KB Article Template
39	Mail Merge Template
44	Duplicate Rule
45	Duplicate Rule Condition
46	Entity Map
47	Attribute Map
48	Ribbon Command
49	Ribbon Context Group
50	Ribbon Customization
52	Ribbon Rule
53	Ribbon Tab To Command Map
55	Ribbon Diff
59	Saved Query Visualization
60	System Form
61	Web Resource
62	Site Map
63	Connection Role
70	Field Security Profile
71	Field Permission
90	Plugin Type
91	Plugin Assembly
92	SDK Message Processing Step
93	SDK Message Processing Step Image
95	Service Endpoint

Improved Custom ‘Export Button’ on Crystal Reports for Visual Studio

Crystal report works great when the export feature is used to export reports to PDF and word, but the one real drawback is the ‘Export to Excel’ feature. No matter how well you in designing the crystal report, the export to excel output is always skewed. It is the way Crystal Report runtime engine maps the objects and places them in excel cells based on the (x,y) position of the original Crystal Objects in the .RPT file.

I did not like how the default export feature was working on crystal reports and also wanted new features like:

1. More uniform export to excel feature with less dummy rows and columns and more visually appealing output.   
2. Restrict the number of export features to only Excel, PDF and Microsoft word and remove all the unnecessary list of export options that the system provides.
3.  Control over Export file fonts, regardless of what font the Crystal report was developed on.
4. A friendly option in the ‘Export Successful ‘message box for users to click on a link which opens the export file for them without going to the folder where the report was exported.
5. Fixed width of rows for uniformity.

So let’s begin the process on steps:

Step 1: Assumptions

• You are using Visual Studio 2005 or higher.
• Crystal Report viewer is hosted in a windows form ‘ReportViewer.cs’
• The example is for the report being exported to excel but it can be used for export to other formats

Step 2: Load data to the report via XML or Memory Stream

 private ReportDocument myReport = null;  
 private void ReportViewer_Load(object sender, EventArgs e)   
 {  
    myReport = new ReportDocument();  
    myData = new DataSet();  
    try   
    {  
      switch (_inputType)   
      {  
         case DataInputType.ByteArray:  
            myData.ReadXml(new System.IO.MemoryStream(_reportData));  
            break;  
         case DataInputType.MemoryStream:  
            stream.Seek(0, SeekOrigin.Begin);  
            myData.ReadXml(_stream);  
            break;  
      }  
      //Load RPT file  
      myReport.Load(reportPath + _RPTName);  
      myReport.SetDataSource(myData);  
      crystalReportViewer1.ShowFirstPage();  
      crystalReportViewer1.ShowGroupTreeButton = true;  
      crystalReportViewer1.ReportSource = myReport;  
    }  
   catch (Exception ex)   
    {  
        ErrorHandler.PublishError(false, "Error displaying report.", ex, true, true);  
    }  
 }  

Step 3: Hide the default export button and add our custom clone on the same place

 //Loop through all the controls in the crystal viewer, Strip the default export button and put a custom export button, Items [0] being the first button which happens to be the export button.  
       
 foreach (Control control in crystalReportViewer1.Controls)   
 {  
    if (control is System.Windows.Forms.ToolStrip)  
    {  
      //Remove Default Export Button, items[0]  
      ToolStripItem tsOriginalItem = ((ToolStrip) control).Items [0];  
      ((ToolStrip) control).Items.RemoveAt(0);  
   
       //Add a clone of Custom Button  
       ToolStripItem tsNewItem = ((ToolStrip) control).Items.Add("");  
        
      //Give this button the same tag,image and tooltip text so it looks and smells like the default export button  
      tsNewItem.ToolTipText = tsOriginalItem.ToolTipText;  
      tsNewItem.Tag = tsOriginalItem.Tag;  
      tsNewItem.Image = tsOriginalItem.Image;  
   
      ((ToolStrip) control).Items.Insert(0, tsNewItem);  
          
      //Write new click event for the new export button  
      tsNewItem.Click += new EventHandler(tsNewItem_Click);  
    }  
 }  
   

Step 4: Define your own custom save file dialogue window when the export button in step 3 is clicked.

ObjectScript Cheat Sheet for Ensemble [Cache]

Action	Code	Alternative way
Call a class method	##class(package.class).method(arguments)	set variable = ##class(package.class).method(arguments)
Call an instance method	do oref.method(arguments)	set variable = oref.method(arguments)
Create a new object	set oref = ##class(package.class).%New()
Open an existing object	set oref = ##class(package.class).%OpenId(id)
Save an object	set status = oref.%Save()
Validate an object without saving	set status = oref.%ValidateObject()
Validate a property without saving	set status = ##class(package.class).PropertyIsValid(oref.Property)
Delete an existing object	set status = ##class(package.class).%DeleteId(id)
Link two objects	set oref1.property = oref2
Clone an object	set clonedOref = oref.%ConstructClone()
Start the SQL shell	do $system.SQL.Shell()	>>go >> SELECTMODE = DISPLAY
Test a class query	do ##class(%ResultSet).RunQuery(class, query)
Create a new standalone array	set arrayOref=##class(%ArrayOfDataTypes).%New()
Insert an element into an array	do oref.arrayProperty.SetAt(value,key)	do arrayOref.SetAt(value,key)
Display an element of an array	do oref.arrayProperty.GetAt(key)	do oref.arrayProperty.GetAt(key)
Display the size of an array	do oref.arrayProperty.Count()	write arrayOref.Count()
Date conversion (external à internal)	set variable = $zdh(“mm/dd/yyyy”)
Date conversion (internal à external)	set variable = $zd(internalDate, format)
Time conversion (external à internal)	set variable = $zth(“hh:mm:ss”)
Time conversion (internal à external)	set variable = $zt(internalTime, format)
Display internal date/time string	write $system.SYS.Horolog()	write $horolog
Display UTC date/time string	write $system.SYS.TimeStamp()
Check if variable exists	write $data(variable)
Return value of variable, or "" if undefined	write $get(variable)
For Loop Syntax	For ControlVariable = StartValue:IncrementAmount:EndValue