Error creating tag binding - unhelpful error message

Ignition
1

I’m getting the following error in the client console whenever the client receives an update to the fpmi/client_tags resource. That is, whenever anyone holding an edit lock on fpmi/client_tags presses save in the designer.

ERROR [ProjectTag-ProjectUpdater] Error creating tag binding.
java.lang.RuntimeException: Type mismatch in operation 'DIVIDE': expected 'Number', found 'String'
	at com.inductiveautomation.ignition.common.expressions.AbstractExpression.typeMismatch(AbstractExpression.java:20)
	at com.inductiveautomation.ignition.common.expressions.ArithmeticExpression.<init>(ArithmeticExpression.java:33)
	at com.inductiveautomation.ignition.common.expressions.parsing.CUP$ELParser$actions.CUP$ELParser$do_action(ELParser.java:936)
	at com.inductiveautomation.ignition.common.expressions.parsing.ELParser.do_action(ELParser.java:323)
	at java_cup.runtime.lr_parser.parse(lr_parser.java:569)
	at com.inductiveautomation.ignition.common.expressions.parsing.ELParserHarness.parse(ELParserHarness.java:22)
	at com.inductiveautomation.factorypmi.application.sqltags.project.ProjectTag.createTagBinding(ProjectTag.java:83)
	at com.inductiveautomation.factorypmi.application.sqltags.project.ProjectTag.startBindingImpl(ProjectTag.java:117)
	at com.inductiveautomation.factorypmi.application.sqltags.project.ProjectTag.startBinding(ProjectTag.java:107)
	at com.inductiveautomation.factorypmi.application.sqltags.ClientTagFolder.startBinding(ClientTagFolder.java:152)
	at com.inductiveautomation.factorypmi.application.sqltags.project.ProjectTagManager.setRoot(ProjectTagManager.java:407)
	at com.inductiveautomation.factorypmi.application.FPMIApp.applyDiff(FPMIApp.java:546)
	at com.inductiveautomation.factorypmi.application.runtime.UpdateProjectPane$ApplyDiff.run(UpdateProjectPane.java:123)
	at com.inductiveautomation.ignition.client.launch.AbstractStepRunner.run(AbstractStepRunner.java:32)
	at java.lang.Thread.run(Thread.java:662)

It’s almost certainly a problem with one of my tags. However, the error message does not tell me which tag is causing the problem. Please can this be fixed?

Thanks.

2

Unfortunately there is no easy way to determine which tag is causing the issue right now. The logger has been changed for future versions to include the tag path in the message. The only thing you can really do right now is examine any Client Expression tags you may have to see if you can determine which one is causing the issue.

3

The log message have the tag path in it in the final release of 7.5.4.

Regards,

4

Excellent. Thanks Colby.