tracker issue : CF-3842778

select a category, or use search below
(searches all categories and all time range)
Title:

spreadsheet functions: numeric boolean values in formatting attributes are not interpreted correctly.

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): / ext-user (Piyush Kumar Nayak)

Created: 10/24/2014

Components: Document Management, Office Integration

Versions: 11.0

Failure Type: Incorrect w/Workaround

Found In Build/Fixed In Build: 291742 / CF11 Update5

Priority/Frequency: Major / Unknown

Locale/System: English / Windows 7 64-bit

Vote Count: 0

Listed in the version 11.0.05.293506 Issues Fixed doc
Problem:
spreadsheet functions: numeric boolean values in formatting attributes are not interpreted correctly.

Method:
<cfscript>
 	ssobj = spreadsheetNew('sheet-test-txtwrap', false);
 	spreadsheetSetColumnWidth(ssobj, 3, 15);  //limit the col. width to effect textwrap.
	spreadsheetAddRow(ssobj,'Merchant#chr(13)##chr(10)# ID, Merchant#chr(13)##chr(10)# Name, Return Customer Conversion Rate');
	//spreadsheetFormatCell(ssobj, {textwrap=1}, 1, 3);
	//spreadsheetFormatCellRange(ssobj, {textwrap=true, bold=true, italic=true, color='red'}, 1, 1, 1, 3);
	//spreadsheetFormatColumns(ssobj, {textwrap=1, bold=true, italic=true, color='green'}, "1-3");

	//spreadsheetFormatRow(ssobj, {textwrap=true, bold=true, italic=true, color='blue'}, 1); 
	spreadsheetFormatRow(ssobj, {textwrap=1, bold=1, italic=1, color='red'}, 1); 
	spreadsheetWrite(ssobj, "#expandPath("./")#testtextwrap.xls", true);
</cfscript> 

Result:
bug verified on CF 10,0,14,291717 and CF 11 HF3 b.291742 / Win 7x64
observed with both xls and xlsx.

Expected:
The formatting should be effected for all accepted values of a boolean param in CF, including 0 and 1.

Workaround:

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3842778

External Customer Info:
External Company:  
External Customer Name:  
External Customer Email:

Attachments:

Comments:

The fix for this bug is available in the pre-release build of ColdFusion 11 Update 5
Comment by CFwatson U.
10492 | February 20, 2015 09:24:32 AM GMT
Verified this is fixed in CF11 Update 5 (build 11,0,05,293506). Thanks!, -Aaron
Comment by External U.
10493 | September 05, 2015 01:02:10 AM GMT