Greetings, I hope this info keeps someone from pulling their hair out. Too late for me… Most have seen the 'Cannot coerce value" error, and it’s usually the result of something we’ve done. I’m not sure this falls into that category. I have a bunch of windows that are very similar… same component…

I can’t definitively answer, but it has something to do with the value being assigned to a boolean custom property within your template, and the initial value saved in the window was a non-null, non-boolean.

Yeah, I think I got that part figured out, but sure could not find a cause. I would have thought that subsequently saved edits of the screen would have fixed any issue with a non-boolean value. Perhaps I do not understand what you mean by “the initial value saved in the window”. All templates in q…

The same thing happened to me today on the window with many templates. When I first open the window I get over 500 errors… [templateError1] [templateError2] Duplicating the window doesn’t help. The only way to get reed of this errors is to manually edit every property tag binding on every templ…

It might be interesting to diff the xml of the broken window versus the xml of the good window.

Here are two .zip files with .xml: StatusBulky_broken.zip (96.2 KB) , StatusBulky_fixed.zip (94.9 KB) I can’t find anything usefull…

Hi Anton… I assumed this was a one-off event so I never posted back. The way I was able to resolve the issue was to duplicate the template, then do a find for the instance path of the original template and replace with the duplicated path. Then repeat the process of find/replace to change the ins…

Hello everyone I got a similar error which said I was trying to coerce a string into a number when mapping some numbers to strings, I had to delete the reference tag and create it again on the UDT with the same information. For me it was a mistake when the tag was created: I had it as an integer in…

Inductive Automation Forum

ClassCastException: Cannot coerce value 'java.lang.Object@

Ignition

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled