I’m running into a problem with external Interface data connections. I finally tracked it back to a rather nasty bug…
I set up an input field in HTML and linked it to refresh the Excelsius cell with read/write access. The JS works and the data fires off. If I am lookind Directly at the cell for updates it works well. If that cell then feeds into a calculation… “BOOM” it dies.
As a test I set up 2 fields. One links directly to the field that is being changed, while the other has a simple equation to copy the contents of that field and contact it with a string on each end. When I start the model with a default of 100 I get this in the 2 fields…
Direct field - ‘100’
Referenced field - ‘’
This is correct. Now, I change the value in the form and expect to see ‘200’ and ‘:200:’ respectively, but instead I get this…
Direct field - ‘200’
Referenced field - ‘::’
Something is killing the value or not recalculating it correctly in all the equations. Is there a way to force a refresh of the values/data? Seems like this makes the entire connection type almost useless for most interaction. Ideas/suggestions appreciated.
So I tried some other options. Any large number gives the result above. I then typed in i and got this…
‘1’
‘:true:’
If I type 0 I get
‘0’
‘:false:’
So if I try to display the results directly from the field it can see the full text/number, but if anything else tries to access it it seems to try to resolve it to a literal boolean so anything other than 0/1 is a blank string. I tried type casing in JS so I was sending a float, a number, etc instead of a string. I also set up the fields in excel so they had specific types associated with them. No luck either way. This looks like a definite bug in Xcelsius.
’