Type of Transformations

1. SCROSS: For defining Scross we can used below xml tags.

< MAINGRID> < /MAINGRID> -> < MainGrid> is starting tag and < /MainGrid> is ending tag.

< SCROSS> < /SCROSS> -> < SCROSS> is starting tag and < /SCROSS> is ending tag.

TARGET -> We can set index of defined complex views in view in this tag if complex view is not define then we can set 0 for this tag.

PIVOT -> Assigned field to transform as header. Like Descrip

IDFIELD -> We can set unique key field for idfield. Like EmployeeID

AGGCOL -> We can set field to transform below header respective assigned column in pivot like Descrip. i.e Dated

2. COCROSS:

< MAINGRID > < /MAINGRID > -> < MainGrid > is starting tag and < /MainGrid > is ending tag.

< COCROSS > < /COCROSS > -> < COCROSS> is starting tag and < /COCROSS> is ending tag.

IDFIELD -> We can set unique key field for idfield. Like EmployeeID

COPYDT -> we can set 0 in this tag

PIVOT -> Assigned field to transform as header. Like MaterialDept

AGGCOL -> We can set field to transform below header respective assigned column in pivot like MaterialDept. i.e IncentiveAmount

VIEW INDEX -> we can set 0, 1, 2 in this tag

PREFIX -> we can set text for display as prefix.

COLOR -> we can set colour for row using this tag.

3. ATTRIBUTIZE:

< MAINGRID > < /MAINGRID > -> < MainGrid > is starting tag and < /MainGrid > is ending tag.

< ATTRIBUTIZE > < /ATTRIBUTIZE > -> < ATTRIBUTIZE > is starting tag and < / ATTRIBUTIZE > is ending tag.

TARGET -> we can set index of defined complex views in view in this tag if complex view is not define then we can set 0 for this tag.

PIVOT -> Set starting fixed latter’s of columns to transform as header and respective values are showing below of respective columns. Like Attrib1Name, Attrib1Value, Attrib2Name, Attrib2Value, Attrib3Name, Attrib3Value.

View Output before Transformation

View Output after Transformation

4. SUMMARIZE:

< MAINGRID > < /MAINGRID > -> < MainGrid > is starting tag and < /MainGrid > is ending tag.

< SUMMARIZE> < /SUMMARIZE > -> < SUMMARIZE > is starting tag and </ SUMMARIZE > is ending tag.

TARGET -> we can set index of defined complex views in view in this tag if complex view is not define then we can set 0 for this tag.

SUMCOLS -> we can set columns for sum.

GROUPBYCOLS -> we can set columns for group.

5. SUMUPALL:

< TOTGRID > < /TOTGRID > -> < TOTGRID > is starting tag and </ TOTGRID > is ending tag.

< SUMUPALL > < /SUMUPALL > -> < SUMUPALL > is starting tag and </ SUMUPALL > is ending tag.

VIEWINDEX -> we can set view index under this tag like 0, 1, 2 etc..

AFTERCOL -> In this tag we can set column name where we have require sum of columns.

FORMAT -> Using this tag we can set format as per require for summary totals.

Complex ->User can link multiple views through a key field in this section.

DISPGRID-> We can set display grid between < DISPGRID>starting & < DISPGRID> ending tags.

e.g: <DISPGRID> 
     <VIEW KEY="ViewStore"/>  
     </DISPGRID>
	

MAINGRID -> We can define main grid using < MAINGRID >starting & < MAINGRID > ending tags.

e.g: <MAINGRID>    
     <VIEW KEY="ListAdvdemStore">    
     </MAINGRID>
	 

VIEW KEY -> User can set view for display grid.

e.g: <VIEW KEY="ListAdvdemStore">

MODROW -> We can applied user define conditions like where condition, hidecolums etc.

e.g: <MODROW>    
     <SQLWHERE2>BusinessEntityID= %idx% </SQLWHERE2>  
     <HIDECOLS>Name</HIDECOLS>
     </MODROW>
	 

SQLWHERE2-> We can applied where condition between < SQLWHERE> & < /SQLWHERE>.

e.g :< MODROW>    
     <SQLWHERE2>BusinessEntityID= %idx% </SQLWHERE2>  
     </MODROW>

HIDECOLS-> We can hide columns using < HIDECOLS> & < /HIDECOLS>.

e.g :< MODROW>    	
     <HIDECOLS>Name</HIDECOLS>
     </MODROW>
	
	

MAKEREL INSERTAT ->set default value 0.

BANDS ->User can combine all child’s view in this section.

FIELD ->Set idfield

CHILD ->Set child using give value 1, 2 etc.

Output

Join Transformations

1. Define Template->When we need to transform view’s data from two sql after merged in one row as per value of Primary KEY then we need to define primary and secondary sql for this key value should be same in both sql and other columns should be different in secondary.

Primary SQL-> we can define primary sql like this.

e.g: In this sql MainpartyID is KEY value.

Secondary SQL-> we can define secondary sql, in this sql value of primary key should be same and other columns should be different in secondary.

Note: {1} to be used for additional where conditions and {0} to be used for default.

2. Define Transform-> User can define join transformation like this.

MAINGRID -> we can define main grid using < MAINGRID >starting & < MAINGRID > ending tags. *e.g.: *

JOIN -> User can merge two sql using INDEX1 and INDEX2 with defining JOINTYPE INNER/LEFT etc.

*e.g.: *

KEY -> User can set key field of Primary SQL to transform of view’s data.

JOINTYPE -> User can set type of joins using this key field like inner, left join etc.

SCROSS -> User can applied transform operation like SCROSS

*e.g: *

IDFIELD -> IDField and Value of KEY tag should be same.

Output: