# AbstractVisionPanel not storing custom properties

**URL:** <https://forum.inductiveautomation.com/t/abstractvisionpanel-not-storing-custom-properties/8514>\
**Category:** Module Development\
**Created:** [June 3, 2014, 4:51pm UTC](https://forum.inductiveautomation.com/t/abstractvisionpanel-not-storing-custom-properties/8514 "2014-06-03T16:51:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![chi](https://avatars.discourse-cdn.com/v4/letter/c/0ea827/32.png) [@chi](https://forum.inductiveautomation.com/u/chi)\
**Post date:** [June 3, 2014, 4:51pm UTC](https://forum.inductiveautomation.com/t/abstractvisionpanel-not-storing-custom-properties/8514/1 "2014-06-03T16:51:33Z")

</div>

I have a component that extends AbstractVisionPanel. Recently (with Ignition 7.6.6) i noticed that this component does not store custom properties any more. Custom properties can be added and edited, but the next time the containing window is opened, they are gone.  
I am not sure when this funtionality was lost, but am quite sure it worked in 7.5.

Has there been any changes to the API i am not aware of?

A bit more info:  
After some debugging, it looks like the custom properties are not serialized when the window is saved. In a debugger i can see that AbstractVisionPanel#setDynamicProps is called and the field dynamicProps is assigned, but after reloading the window dynamicProps is null again.

---

<div class="post-metadata">

**Author:** ![chi](https://avatars.discourse-cdn.com/v4/letter/c/0ea827/32.png) [@chi](https://forum.inductiveautomation.com/u/chi)\
**Post date:** [June 3, 2014, 8:26pm UTC](https://forum.inductiveautomation.com/t/abstractvisionpanel-not-storing-custom-properties/8514/2 "2014-06-03T20:26:52Z")

</div>

Ok, here’s the solution:

To serialize the dynamic properties, the field has to be added to the BeanInfo. I guess this happened in CommonBeanInfo in previous API versions.

```auto
addProp("dynamicProps", "Dynamic Properties", "", HIDDEN_MASK);
```

Maybe this line should be added to the API’s component example (HelloWorldComponentBeanInfo), to help others to avoid this problem.