# Template Naming Convention Causing Issues

**URL:** <https://forum.inductiveautomation.com/t/template-naming-convention-causing-issues/75014>\
**Category:** Ignition\
**Tags:** ignition81, vision\
**Created:** [June 14, 2023, 12:32pm UTC](https://forum.inductiveautomation.com/t/template-naming-convention-causing-issues/75014 "2023-06-14T12:32:07Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![David\_Duquette](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@David\_Duquette](https://forum.inductiveautomation.com/u/David_Duquette)\
**Post date:** [June 14, 2023, 12:32pm UTC](https://forum.inductiveautomation.com/t/template-naming-convention-causing-issues/75014/1 "2023-06-14T12:32:07Z")

</div>

Hello,

This is more an observation that might want to be addressed.

I was creating a new template and I used a period in the name 'T.C. Display'. Looking back at this, probably not the best idea, but here we are. After doing so made some internal properties and when attempting to bind to those properties I was receiving an error 'Unable to find component for path: 'T.C. Display.propertyName'. Looking back, I can see why this caused an issue, but if any special character such as the period are going to cause an issue it might be a good idea to prevent it from being used in naming conventions.

---

<div class="post-metadata">

**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\
**Post date:** [June 14, 2023, 12:47pm UTC](https://forum.inductiveautomation.com/t/template-naming-convention-causing-issues/75014/2 "2023-06-14T12:47:20Z")

</div>

> [@David\_Duquette](#):
>
> Unable to find component for path: 'T.C. Display.propertyName'.

I don’t think you’re having the issue that you believe you are, or you’ve made a typo.

I doubt very much that you’re component is named `'T.C. Display.propertyName'` the `.propertyName shouldn’t be there`

---

<div class="post-metadata">

**Author:** ![David\_Duquette](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@David\_Duquette](https://forum.inductiveautomation.com/u/David_Duquette)\
**Post date:** [June 14, 2023, 1:43pm UTC](https://forum.inductiveautomation.com/t/template-naming-convention-causing-issues/75014/3 "2023-06-14T13:43:53Z")

</div>

I tested this few times, with different templates. If there is a period in the name of the template, I was not able to bind anything to the internal properties of the template. I was receiving an error 'Unable to find component for path: T.C. Display.tag\_path' ( the property name = tag\_path)  
I simply change the name of the template, remove the periods and everything works as it should.  
property binding = TC Display.tag\_path

---

<div class="post-metadata">

**Author:** ![pascal.fragnoud](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pascal.fragnoud/32/24728_2.png) [@pascal.fragnoud](https://forum.inductiveautomation.com/u/pascal.fragnoud)\
**Post date:** [June 14, 2023, 2:11pm UTC](https://forum.inductiveautomation.com/t/template-naming-convention-causing-issues/75014/4 "2023-06-14T14:11:19Z")

</div>

I think that's just the path, and in this case it's looking for a component named `T`.

@David_Duquette I'd stick to alpha characters + '\_' and maybe '-'.  
I stay clear of everything else, including spaces.