# \[BUG-6988\]Embedded View "Template" Instance Behavior

**URL:** <https://forum.inductiveautomation.com/t/bug-6988-embedded-view-template-instance-behavior/68170>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [January 3, 2023, 3:18pm UTC](https://forum.inductiveautomation.com/t/bug-6988-embedded-view-template-instance-behavior/68170 "2023-01-03T15:18:16Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [January 20, 2023, 6:04pm UTC](https://forum.inductiveautomation.com/t/bug-6988-embedded-view-template-instance-behavior/68170/13 "2023-01-20T18:04:51Z")

</div>

To get an SVG to work in the current version, you need to not have duplicate svgs where their definition contains any reference to a hard-coded `id` and your goal is to change their color.

Any svg which contains color definitons _inside_ of the svg in a manner like this: `style="fill: url("#s0_3-SVGID_1_");"` will result in this issue because they're defining their appearance (fill, in this case) based off of a specific id present in the DOM. When they search for that id, they will always find the first instance and use that color.

---

_[View the full topic](https://forum.inductiveautomation.com/t/bug-6988-embedded-view-template-instance-behavior/68170)._