# \[bug-13555\]DropHandler Exception

**URL:** <https://forum.inductiveautomation.com/t/bug-13555-drophandler-exception/24106>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [April 12, 2019, 5:44pm UTC](https://forum.inductiveautomation.com/t/bug-13555-drophandler-exception/24106 "2019-04-12T17:44:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![zacslade](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zacslade/32/3587_2.png) [@zacslade](https://forum.inductiveautomation.com/u/zacslade)\
**Post date:** [April 12, 2019, 5:44pm UTC](https://forum.inductiveautomation.com/t/bug-13555-drophandler-exception/24106/1 "2019-04-12T17:44:29Z")

</div>

Hi guys,

I have a pretty simple template -- just a circle that changes color based on a boolean value. The custom property for that value is called "State" and is the drop target.

If I drag a bool tag onto the screen, I can select my indicator template from the dropdown list, and it works. But if I put the indicator on the screen first, and then drop a tag onto it, I get the following error:

> Error during drop: class com.inductiveautomation.factorypmi.designer.beaninfo.TemplateHolderBeanInfo$TemplateTagDropHandler cannot be cast to class com.inductiveautomation.vision.api.designer.beans.TagDropHandler (com.inductiveautomation.factorypmi.designer.beaninfo.TemplateHolderBeanInfo$TemplateTagDropHandler and com.inductiveautomation.vision.api.designer.beans.TagDropHandler are in unnamed module of loader java.net.URLClassLoader @674ee5c7)

Any ideas what I might be doing wrong here? Is this a bug?

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [April 12, 2019, 6:09pm UTC](https://forum.inductiveautomation.com/t/bug-13555-drophandler-exception/24106/2 "2019-04-12T18:09:33Z")

</div>

Bug on our end - fix is already pending and should make it into one of the next few nightlies.
