tracker issue : CF-3662240

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

SpreadsheetMergeCells Corrupts Spreadsheet Under Specific Conditions

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Florian Koch / Florian Koch (FlorianKoch)

Created: 11/11/2013

Components: Document Management, Office Integration

Versions: 9.0.1

Failure Type: Data Corruption

Found In Build/Fixed In Build: 9.0.1 / 289063

Priority/Frequency: Critical / Some users will encounter

Locale/System: English / Windows 7

Vote Count: 0

Problem Description:
Use of SpreadsheetMergeCells results in corrupt spreadsheet output under certain specific conditions: format is XLSX, sheet is second or subsequent, sheet contains at least two rows with text.

Steps to Reproduce:
<cfscript>
	sheet1 = SpreadsheetNew("testsheet1", true);
</cfscript>
<cfspreadsheet action="write" filename="c:\temp\test.xlsx" name="sheet1" sheetname="Sheet 1" overwrite="true"/>
<cfscript>
	sheet2 = SpreadsheetNew("testsheet2", true);
	SpreadsheetSetCellValue(sheet2, "text", 1, 1);
	SpreadsheetSetCellValue(sheet2, "text", 2, 2);
	SpreadsheetMergeCells(sheet2, 1, 1, 3, 4);
</cfscript>
<cfspreadsheet action="update" filename="c:\temp\test.xlsx" name="sheet2" sheetname="Sheet 2"/>

Actual Result:
Corrupt speadsheet file, containing multiple duplicate mergeCell tags in the underlying OOXML.

Expected Result:
Valid spreadsheet file.

Any Workarounds:
Selecting the legacy XLS format, or avoiding the specific (but fairly common) conditions described above, or postprocessing the spreadsheet file to remove invalid OOXML.

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

Watson Bug ID:	3662240

External Customer Info:
External Company:  
External Customer Name: FlorianKoch
External Customer Email:  
External Test Config: My Hardware and Environment details:

Observed in multiple environments

Attachments:

  1. November 12, 2013 00:00:00: 1_mergeBug.cfm

Comments:

fixed in the next major version of CF.
Comment by Piyush K.
14016 | March 13, 2014 05:22:46 AM GMT