# Version control via dataset

**URL:** <https://forum.inductiveautomation.com/t/version-control-via-dataset/97283>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [October 15, 2024, 10:20pm UTC](https://forum.inductiveautomation.com/t/version-control-via-dataset/97283 "2024-10-15T22:20:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eugene49](https://avatars.discourse-cdn.com/v4/letter/e/c6cbf5/32.png) [@Eugene49](https://forum.inductiveautomation.com/u/Eugene49)\
**Post date:** [October 15, 2024, 10:20pm UTC](https://forum.inductiveautomation.com/t/version-control-via-dataset/97283/1 "2024-10-15T22:20:34Z")

</div>

I am ready to get burned for not wanting git.

When I was working as ASIC programmer in semicon industry.

We use config manager for version control. A dropdown box, that allows us to point to specific version of the code.

I like this simple approach. Thinking if I could do the same thing.  
To illustrate, Say I have the following:

- Top Main view with an embed view.
- a tag called Embed\_View\_Path (which hold the path of embed view to use)
- couple of views (e.g. view\_v1, view\_v2)

In this case, I store the path of view\_v1 in tag Embed\_View\_Path.  
I will bind this tag to the path of "Embedded View" component.

This way I can dynamically choose, which version of embed\_view to use by writing on the tag.

Before I develop this, I wanted to see if there is major flaw on this strategy.

I just feel like there should be a simple way, straight/native, version control mechanism..  
I don't have experience with git. I am not sure I want to go that route..  
My opinion, doesn't worth the headache.. idk.

---

<div class="post-metadata">

**Author:** ![Adarsh\_K](https://avatars.discourse-cdn.com/v4/letter/a/ee7513/32.png) [@Adarsh\_K](https://forum.inductiveautomation.com/u/Adarsh_K)\
**Post date:** [October 16, 2024, 7:31am UTC](https://forum.inductiveautomation.com/t/version-control-via-dataset/97283/2 "2024-10-16T07:31:06Z")

</div>

I usually maintain different version of Projects before git.

---

<div class="post-metadata">

**Author:** ![victordcq](https://avatars.discourse-cdn.com/v4/letter/v/f6c823/32.png) [@victordcq](https://forum.inductiveautomation.com/u/victordcq)\
**Post date:** [October 16, 2024, 7:56am UTC](https://forum.inductiveautomation.com/t/version-control-via-dataset/97283/3 "2024-10-16T07:56:48Z")

</div>

So for every edit you do you would have to make a new view, new paths, and remeber to update all the dependancies of those views. Which would than also need their new version that would need to also update all their dependancies/paths ect..

Seems like a lot ot work. git is realy easy, and has plenty of ui tools that removes any need to know how to trigger the commands