# Can I export factorytalk view global objects to ignition templates?

**URL:** <https://forum.inductiveautomation.com/t/can-i-export-factorytalk-view-global-objects-to-ignition-templates/66247>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [November 8, 2022, 6:42pm UTC](https://forum.inductiveautomation.com/t/can-i-export-factorytalk-view-global-objects-to-ignition-templates/66247 "2022-11-08T18:42:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Edgar\_Hernandez](https://avatars.discourse-cdn.com/v4/letter/e/ed8c4c/32.png) [@Edgar\_Hernandez](https://forum.inductiveautomation.com/u/Edgar_Hernandez)\
**Post date:** [November 8, 2022, 6:42pm UTC](https://forum.inductiveautomation.com/t/can-i-export-factorytalk-view-global-objects-to-ignition-templates/66247/1 "2022-11-08T18:42:24Z")

</div>

¿Hay manera de que los global objects de factorytalk view, se puedan exportar a templates en ignition?

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [November 8, 2022, 7:42pm UTC](https://forum.inductiveautomation.com/t/can-i-export-factorytalk-view-global-objects-to-ignition-templates/66247/2 "2022-11-08T19:42:12Z")

</div>

Just fyi, this is ~~an English forum only~~ a predominantly English forum  
Translated with google:  
"Is there a way that factorytalk view global objects can be exported to ignition templates?"

The short answer is no. You'll need to recreate these yourself.

The longer answer is, you _could_ potentially export the ftview global objects to XML and then write a script to process this and create JSON to create **Perspective** Views for each object, but it will likely be more work than its worth, with the results being suboptimal.  
Converting to **Vision** Templates via script is more or less impossible / a LOT of work

---

<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:** [November 9, 2022, 2:32am UTC](https://forum.inductiveautomation.com/t/can-i-export-factorytalk-view-global-objects-to-ignition-templates/66247/3 "2022-11-09T02:32:18Z")

</div>

> [@nminchin](#):
>
> The longer answer is, you _could_ potentially export the ftview global objects to XML and then write a script to process this and create JSON

This _could_ work, assuming that the display doesn’t have objects that Rockwell in their infinite wisdom decided to serialize into some encrypted nonsense that isn’t exportable. (In some instances even into FTView itself, e.g bitmap objects and VBA scripts).

Animations would have to be converted to various expressions that wouldn’t be 1:1 or even compatible, tags would need to be converted to the corrects paths, and if you had HMI tags instead of direct reference you would also need to have a tag export so that you could look up the tag path.

It isn’t worth the effort. I’m having nightmares just thinking about it.

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [November 9, 2022, 2:45am UTC](https://forum.inductiveautomation.com/t/can-i-export-factorytalk-view-global-objects-to-ignition-templates/66247/4 "2022-11-09T02:45:02Z")

</div>

Yes, maybe I under-exaggerated the complexity of it, but it is significant especially compared to just creating them all manually to actually suit Ignition. Most of the time you wouldn't just want to convert another platform's components into Ignition regardless of whether you can or not. Since the sub-optimal way the other platform does it will become blatantly obvious if you did it the same way in Ignition.

---

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [November 9, 2022, 6:57am UTC](https://forum.inductiveautomation.com/t/can-i-export-factorytalk-view-global-objects-to-ignition-templates/66247/5 "2022-11-09T06:57:47Z")

</div>

The OP may have some interest in Flintium

> [@Introducing Flintium! An open source library of Ignition faceplates](https://forum.inductiveautomation.com/t/introducing-flintium-an-open-source-library-of-ignition-faceplates/36302):
>
> I’ve been working on this library for a while now, and just made the repository public. Originally based on the [FactoryPacks](https://inductiveautomation.com/exchange/113/overview) project from the Ignition Exchange. Once Flintium is stable, a version will be posted to the Exchange, but for now, feel free to try out the working version on Github. The project needs input from this community! For information on contributing, please see the [Contributing](https://github.com/jlbcontrols/Flintium/wiki/Contributing) Wiki page. Anyone is welcome to post comments, feature requests, and report bugs on the [issues pa…](https://github.com/jlbcontrols/Flintium/issues)
