We are upgrading Coldfusion from 9 to 11. This worked in 9 just fine, but running into errors in 11. My cfgrid declaration is as follows:
<cfgrid name="cfPagingGridName" autowidth="yes" rowHeaders="no" format="html" height="165" width="675" style="border:none;"
selectcolor="##C6D6EB" striperowcolor="##EEF3F9" striperows="yes" selectOnLoad="false" bgcolor="##FFFFFF" pageSize="1000"
// Get Nominee Grid Data
var nomineeGrid = ColdFusion.Grid.getGridObject("cfPagingGridName");
var mydata = nomineeGrid.getStore();
The specific error I'm getting is "Unable to get property 'getStore' of undefined or null reference. The real problem occurs with the getGridObject line. It never defines the variable nomineeGrid. I'm able to look at this in 2 environments, one using CF 11 and the other using CF 9 . Stepping through the code, CF 9 correctly defines the nomineeGrid variable, but CF 11 does not. My code uses this in many places so any help with this issue would be appreciated.
Further debugging efforts have uncovered that this only seems to be an issue in Internet Explorer 11, but not Firefox or Chrome.
I had an answer on her about turning off compatibility mode, and it works. However, upon further debugging (because I can't let things go), I found out that the problem is with the boolean column. It can't resolve a boolean. I can convert the bit that is returned from sql server to yes/no or true/false, and it still won't recognize it. I can change the type on the column to string, and it will print out the value of that field. Was boolean deprecated within cfgrid?
<cfgridcolumn name="representative" type="boolean" header="Grp Rep" select="no" headerMenu="no" width="55">
The boolean type is still there. This could be an issue with IE11 as there are a number of issue with CFGrid and IE11.
IT could also be a similar issue to this: - Bug#3792163 - CFGRID getGridObject no longer defined
I would suggest posting a bug if you are unable to resolve - https://bugbase.adobe.com/index.cfm?event=newBug
Yes, the boolean type is still there and supported in Chrome and Firefox. It's even supported in IE 11 if you don't have compatibility mode turned on, but unfortunately in my case, it has to stay on because other parts of the application are old (we intend to upgrade over time, but it will take a while). I may submit a bug, but there may only be a small subset of people this may affect. I appreciate that you took your time out to reply to my issue..