☰

Updated Changing Data Precision (markdown)

IzendaPeterCho committed 2015-04-17 16:20:09 -0400 commit f34badf96975ec77fb42249e2a634dd632e3057f

				FAQ/Questions/Changing-Data-Precision.md
			
          @@ -7,7 +7,7 @@ How can I change default data precision setting?

           When Izenda loads a report that uses a stored procedure, it creates a temporary table to store the values. For string, it creates NVARCHAR(MAX) columns and for numeric fields a DECIMAL(18,6). Therefore, if any field with greater precision such as NUMERIC(22,8) is used, the report then fails with a conversion error as below because it cannot fit the NUMERIC(22,8) value into a DECIMAL(18,6) column.

          -[![Izenda Core Integration Video](/Home/izenda_intro_video.png)](https://www.youtube.com/watch?v=4E0npCxLi4o)

          +[![Test](/Home/Conversion.jpg)]

           The hard-code default setting, DECIMAL(18,6) can be easily modified by adding below setting code to the Driver (within InitializeReporting() method) .

...	...	@@ -7,7 +7,7 @@ How can I change default data precision setting?
7	7
8	8	When Izenda loads a report that uses a stored procedure, it creates a temporary table to store the values. For string, it creates NVARCHAR(MAX) columns and for numeric fields a DECIMAL(18,6). Therefore, if any field with greater precision such as NUMERIC(22,8) is used, the report then fails with a conversion error as below because it cannot fit the NUMERIC(22,8) value into a DECIMAL(18,6) column.
9	9
10		-[![Izenda Core Integration Video](/Home/izenda_intro_video.png)](https://www.youtube.com/watch?v=4E0npCxLi4o)
	10	+[![Test](/Home/Conversion.jpg)]
11	11
12	12	The hard-code default setting, DECIMAL(18,6) can be easily modified by adding below setting code to the Driver (within InitializeReporting() method) .
13	13