# Template to add correct template embeded point

**URL:** <https://clarionhub.com/t/template-to-add-correct-template-embeded-point/4933>\
**Category:** uncategorized\
**Created:** [March 28, 2022, 10:50am UTC](https://clarionhub.com/t/template-to-add-correct-template-embeded-point/4933 "2022-03-28T10:50:19Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![anon23294430](https://clarionhub.com/user_avatar/clarionhub.com/anon23294430/32/3829_2.png) [@anon23294430](https://clarionhub.com/u/anon23294430)\
**Post date:** [March 28, 2022, 9:26pm UTC](https://clarionhub.com/t/template-to-add-correct-template-embeded-point/4933/10 "2022-03-28T21:26:46Z")

</div>

So when using something like the CreateAt embed template, you have to drop to source to see what the active template embed instance really is you cant see it from an embed code template windows as the two pics below demonstrate.

The 1st pic is my jumped up version of the CreateAt embed code template and the list box \*\*\*_(last few entries) cant display the active template info \*\*\* You cant see this in the pic!_ so there is a note below it which says, drop to the source to see the complete embed info.

 ![Embed Template](https://clarionhub-uploads.s3.eu-north-1.amazonaws.com/original/2X/4/4cb6ee6edef81c77e46d69296945293360fcb48c.png)

The 2nd picture shows the information it writes which is only visible from source and it shows the proper active template embed. Its a minor limitation of the out the box templates, unless you are using something like #RunDll and an additional dll to do more work.

 ![embedsource](https://clarionhub-uploads.s3.eu-north-1.amazonaws.com/original/2X/d/dbb8cff77d0a79851db6045085c39bb5acff6149.png)

---

_[View the full topic](https://clarionhub.com/t/template-to-add-correct-template-embeded-point/4933)._