# \[BUG\]Template Property, Template Instance Custom Prop Share Name

**URL:** <https://forum.inductiveautomation.com/t/bug-template-property-template-instance-custom-prop-share-name/89127>\
**Category:** Ignition\
**Tags:** vision, ignition81\
**Created:** [April 19, 2024, 4:56pm UTC](https://forum.inductiveautomation.com/t/bug-template-property-template-instance-custom-prop-share-name/89127 "2024-04-19T16:56:41Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![amarks](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amarks/32/45610_2.png) [@amarks](https://forum.inductiveautomation.com/u/amarks)\
**Post date:** [April 19, 2024, 4:56pm UTC](https://forum.inductiveautomation.com/t/bug-template-property-template-instance-custom-prop-share-name/89127/1 "2024-04-19T16:56:41Z")

</div>

I have a template with the parameter "position" and I'm also able to create a custom property "position" but the reference to both of these properties in an expression is the same, so I have no idea which one it's going to grab. This should probably not be allowed.

\*\*Edit: I think this was a side effect of adding a parameter to a template, an instance of which already had a custom property with the same name. I cannot add a custom prop with the same name if the parameter already exists. I doubt that there's anything that IA can do about that situation because of the order that things were done. So, more of a PSA.