tracker issue : CF-3043160

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

Bug 85963:(Watson Migration Closure)There's a bug in spreadsheetAddRows() in that with an array, one must specify the row/column values

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Fabrice Reynolds / Fabrice Reynolds (Fabrice Reynolds)

Created: 01/21/2011

Components: Document Management, Office Integration

Versions: 9.0.1

Failure Type: Unspecified

Found In Build/Fixed In Build: 9,0,1,274733 /

Priority/Frequency: Major / Unknown

Locale/System: English / Platforms All

Vote Count: 3

Listed in the version 2016.0.0.297996 Issues Fixed doc
Verification notes: verified_fixed on May 18, 2018 using build 2016.0.01.298513
Related Bugs:
CF-3923995 - Similar to


Problem:

There's a bug in spreadsheetAddRows() in that with an array, one must specify the row/column values.The returned value if you do not specify the row/column is:An exception occurred while calling the function addRow.java.lang.IllegalArgumentException: Invalid row number (-1) outside allowable range (0..65535)This is presumably returned from a sub function call. Not only is the message missleading but this means that you cannot use arrays with spreadsheetAddRows() without specifying a row and column.
Method:

<cfscript>    arr = ["one", "two", "three", "four"];     sX = spreadsheetNew("spreadsheetAddRowsWithArray");    spreadsheetAddRows(sX, arr);  //  error will trigger here</cfscript>
Result:

An exception occurred while calling the function addRow.java.lang.IllegalArgumentException: Invalid row number (-1) outside allowable range (0..65535)

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

Watson Bug ID:	3043160

Keywords:
HF8


External Customer Info:
External Company:  
External Customer Name: Fabrice Reynolds
External Customer Email: 085B0AD044CDED9A9920157F
External Test Config: 01/21/2011

Attachments:

Comments:

Hi Adobe, I've verified this is fixed in CF2016 Update 1 (build 2016.0.01.298513). Thanks!, -Aaron
Comment by Aaron N.
27867 | May 18, 2018 06:36:19 AM GMT