# Handle existing Tag Providers using SDK **URL:** \ **Category:** Module Development\ **Tags:** ignition79, ignition80\ **Created:** [March 1, 2022, 1:57pm UTC](https://forum.inductiveautomation.com/t/handle-existing-tag-providers-using-sdk/56665 "2022-03-01T13:57:34Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Matteo\_Boniardi](https://avatars.discourse-cdn.com/v4/letter/m/b487fb/32.png) [@Matteo\_Boniardi](https://forum.inductiveautomation.com/u/Matteo_Boniardi)\ **Post date:** [March 1, 2022, 1:57pm UTC](https://forum.inductiveautomation.com/t/handle-existing-tag-providers-using-sdk/56665/1 "2022-03-01T13:57:34Z")
Hello everyone, I’m trying to develop a module for Ignition 7.9, which would integrate an already existing Ignition-based solution. The current problem is that I want to “handle” an existing Standard Tag Provider from this module: I thought I found something promising in the 8.0 Tag API Examples of the SDK Programmers’s Guide, like [Read and Write Tags - Ignition SDK Programmer's Guide - Ignition Documentation](https://docs.inductiveautomation.com/display/SE/Read+and+Write+Tags), but anyway I was not able to adapt them for version 7.9, which is mandatory. Afterward, I tried to use the simple-tag-provider example module (v. 7.9) as a starting point to achieve the same goal, but I came to the conclusion (I probably reinvented the wheel) that I can’t use a brand new Tag Provider instance to manipulate the existing provider. In my attempt, I used the same name to generate a Tag Provider from the module, hoping that somehow it would have been able to “detect” the other one in Ignition and “fallback” on it: when I opened the Designer, there was effectively a Tag Provider with the right name but without any tags; after I uninstalled the module and restarted the Designer, the original (Standard) Tag Provider reappeared correctly. In the end, I’ve come across this thread [Creating Standard and Remote (Not Managed) Tag Providers Using SDK](https://forum.inductiveautomation.com/t/creating-standard-and-remote-not-managed-tag-providers-using-sdk/48471), where @pturmel post seems to be the final answer to my problem (despite the different context). So, even sounding like completely dumb questions, I have to ask: - is it possible to achieve the handling of an existing Tag Provider from a module in Ignition 7.9? And in Ignition 8.0/8.1? - in case it is indeed possible, can someone please provide a small example (or a link of where to find it)? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [March 1, 2022, 1:58pm UTC](https://forum.inductiveautomation.com/t/handle-existing-tag-providers-using-sdk/56665/2 "2022-03-01T13:58:56Z")
You’ve written a lot of words and somehow still not explained what you’re trying to do… What does “handling” a tag provider mean? ---
**Author:** ![Matteo\_Boniardi](https://avatars.discourse-cdn.com/v4/letter/m/b487fb/32.png) [@Matteo\_Boniardi](https://forum.inductiveautomation.com/u/Matteo_Boniardi)\ **Post date:** [March 1, 2022, 2:37pm UTC](https://forum.inductiveautomation.com/t/handle-existing-tag-providers-using-sdk/56665/3 "2022-03-01T14:37:34Z")
Hello Kevin, thank you for your quick response Practically, I have a Standard Tag Provider called YLab\_Tag\_Provider: from the module, I’m trying to “catch” it from the GatewayHook using this syntax ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/6/26959cb87b252d9d3a5d9dd2d13a6dafc288488d.png) I would want to operate with this tag provider as I do in the Tag Browser of the Designer (browse, read/write, create/eliminate tags) ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [March 1, 2022, 3:22pm UTC](https://forum.inductiveautomation.com/t/handle-existing-tag-providers-using-sdk/56665/4 "2022-03-01T15:22:53Z")
You’re going down the wrong path entirely. From [`GatewayContext`](http://files.inductiveautomation.com/sdk/javadoc/ignition79/795/com/inductiveautomation/ignition/gateway/model/GatewayContext.html), call [`getTagManager`](http://files.inductiveautomation.com/sdk/javadoc/ignition79/795/com/inductiveautomation/ignition/gateway/model/GatewayContext.html#getTagManager--), then on the `SQLTagsManager` call [`getTagProvider(name)`](http://files.inductiveautomation.com/sdk/javadoc/ignition79/795/com/inductiveautomation/ignition/gateway/sqltags/SQLTagsManager.html#getTagProvider-java.lang.String-), which gives you a [`TagProvider`](http://files.inductiveautomation.com/sdk/javadoc/ignition79/795/com/inductiveautomation/ignition/gateway/sqltags/TagProvider.html) you can read, write, and browse. Do note that 7.9 is getting quite close to end-of-life: > **[The Future of Ignition 7.9 LTS and EOL Plans](https://inductiveautomation.com/blog/the-future-of-ignition-79-lts-and-eol-plans)** > > Ignition 7.9 is the last Long-Term Support (LTS) release for the Ignition 7 branch. LTS versions of Ignition receive active support from our development and tech support teams, including improvements and fixes for a full five years after their... ---
**Author:** ![Matteo\_Boniardi](https://avatars.discourse-cdn.com/v4/letter/m/b487fb/32.png) [@Matteo\_Boniardi](https://forum.inductiveautomation.com/u/Matteo_Boniardi)\ **Post date:** [March 1, 2022, 5:30pm UTC](https://forum.inductiveautomation.com/t/handle-existing-tag-providers-using-sdk/56665/5 "2022-03-01T17:30:56Z")
Now I have a clearer view of the situation, thank you @paul-griffith, also for pointing out this information regarding 7.9 Many thanks to both you and @Kevin.Herron for your time and your immediate replies!