Changes in 1001c86: Updated 10.0 Style tab (markdown)

				Guides/ReportDesign/10.0-Style-tab.md
			
          @@ -90,6 +90,13 @@ The analysis grid VG style will initially start with every expandable row collap

           The white area contains all the columns that were not checked as "VG" in the report designer. Here, the columns were the count of the orders for that visual group, how many total units are on the order, and the unit price of each item. You can modify the behavior of the VG aggregate functions on the [[Advanced box|http://wiki.izenda.us/Guides/ReportDesign/4.0-fields-tab#4.8-Advanced-Field-Settings-Button]] of the fields tab by changing the **subtotal function**.

          +*Note*: Analysis Grid has some requirements.

          +1. You must have at least two fields selected as Visual Groups - Analysis Grid constructs a hierarchy, and you cannot have a hierarchy of one.

          +2. You must have at least one field selected as an aggregate. Once a hierarchy has been built, the grid must have something to display.

          +3. Best practice is for all of the visually grouped fields to be placed at the top of the field order stack.

          +

          +Please see [[this page|http://wiki.izenda.us/Guides/ReportDesign/16.0-Analysis-Grid]] for more information. 

          +

           ###VG Hierarchy

           The VG hierarchy style will create a flat hierarchical representation of the data using the visual group fields as containers. But instead of displaying each level of the hierarchy below the container field's value, it displays it to the right. It also displays all levels expanded by default instead of collapsed by default. You can expand or collapse containers like with the analysis grid.

...	...	@@ -90,6 +90,13 @@ The analysis grid VG style will initially start with every expandable row collap
90	90
91	91	The white area contains all the columns that were not checked as "VG" in the report designer. Here, the columns were the count of the orders for that visual group, how many total units are on the order, and the unit price of each item. You can modify the behavior of the VG aggregate functions on the [[Advanced box\|http://wiki.izenda.us/Guides/ReportDesign/4.0-fields-tab#4.8-Advanced-Field-Settings-Button]] of the fields tab by changing the subtotal function.
92	92
	93	+Note: Analysis Grid has some requirements.
	94	+1. You must have at least two fields selected as Visual Groups - Analysis Grid constructs a hierarchy, and you cannot have a hierarchy of one.
	95	+2. You must have at least one field selected as an aggregate. Once a hierarchy has been built, the grid must have something to display.
	96	+3. Best practice is for all of the visually grouped fields to be placed at the top of the field order stack.
	97	+
	98	+Please see [[this page\|http://wiki.izenda.us/Guides/ReportDesign/16.0-Analysis-Grid]] for more information.
	99	+
93	100	###VG Hierarchy
94	101
95	102	The VG hierarchy style will create a flat hierarchical representation of the data using the visual group fields as containers. But instead of displaying each level of the hierarchy below the container field's value, it displays it to the right. It also displays all levels expanded by default instead of collapsed by default. You can expand or collapse containers like with the analysis grid.