# Scanclass's visibility in SQLTag Browser/Tag Browser

**URL:** <https://forum.inductiveautomation.com/t/scanclasss-visibility-in-sqltag-browser-tag-browser/38468>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [September 8, 2020, 12:30pm UTC](https://forum.inductiveautomation.com/t/scanclasss-visibility-in-sqltag-browser-tag-browser/38468 "2020-09-08T12:30:16Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![iscrac](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/iscrac/32/49757_2.png) [@iscrac](https://forum.inductiveautomation.com/u/iscrac)\
**Post date:** [September 8, 2020, 12:30pm UTC](https://forum.inductiveautomation.com/t/scanclasss-visibility-in-sqltag-browser-tag-browser/38468/1 "2020-09-08T12:30:16Z")

</div>

Hi everyone!

Is it possible to view scanclass in new versions of Ignition in SQLTagBrowser as it was in old versions?  
I think that this is the very 👉 **IMPORTANT** 👈 parameter, and in newest versions it’s so much harder to see if the tags have it’s related scanclass… I have to open each tag and check which scanclass does it have…

please, bring this option back…

see the picture below:  
in oldest versions:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/d/ed60e745b597f4b3b989f4c811f9bc00c733832f.png)

in newest versions:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/0/b0ef5e2eb83cf5448f4ec019f3791a29d257789b.png)

or… there’s another way how to check the scanclass of all (for example 100000 tags) at the same time? 👉 👈

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [September 8, 2020, 2:14pm UTC](https://forum.inductiveautomation.com/t/scanclasss-visibility-in-sqltag-browser-tag-browser/38468/2 "2020-09-08T14:14:56Z")

</div>

v8 doesn’t have scan classes. The important parts of what were scan classes are now called “tag groups”.

---

<div class="post-metadata">

**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:** [September 8, 2020, 3:00pm UTC](https://forum.inductiveautomation.com/t/scanclasss-visibility-in-sqltag-browser-tag-browser/38468/3 "2020-09-08T15:00:44Z")

</div>

And, no, you can’t preview the tag group from the main tag editor window. For one thing, it’s _not_ universally relevant in 8.0+; tags can be truly event driven (reference, expression tags) and thus have _no_ tag group whatsoever.

That said, better tools to organize, categorize, and report on your tags _are_ on our list.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [September 8, 2020, 3:41pm UTC](https://forum.inductiveautomation.com/t/scanclasss-visibility-in-sqltag-browser-tag-browser/38468/4 "2020-09-08T15:41:19Z")

</div>

> [@paul-griffith](#):
>
> And, no, you can’t preview the tag group from the main tag editor window.

This ought to be fixed, btw. There were a number of columns available in v7.9 that weren't universal either, and they worked just fine. Simply empty where not applicable. Using universality as an excuse in v8 is just lame.

---

<div class="post-metadata">

**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:** [September 8, 2020, 3:54pm UTC](https://forum.inductiveautomation.com/t/scanclasss-visibility-in-sqltag-browser-tag-browser/38468/5 "2020-09-08T15:54:11Z")

</div>

🤷‍♂️  
The tag browser panel is actively being changed for 8.1. Hopefully for the better 🙂

---

<div class="post-metadata">

**Author:** ![iscrac](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/iscrac/32/49757_2.png) [@iscrac](https://forum.inductiveautomation.com/u/iscrac)\
**Post date:** [September 9, 2020, 4:40am UTC](https://forum.inductiveautomation.com/t/scanclasss-visibility-in-sqltag-browser-tag-browser/38468/6 "2020-09-09T04:40:15Z")

</div>

> [@paul-griffith](#):
>
> Hopefully for the better

to be honest: not for me and my collegues)))  
sorry) 🥺  
the oldest version of editing tags was much better! 🤐

---

<div class="post-metadata">

**Author:** ![iscrac](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/iscrac/32/49757_2.png) [@iscrac](https://forum.inductiveautomation.com/u/iscrac)\
**Post date:** [September 9, 2020, 4:58am UTC](https://forum.inductiveautomation.com/t/scanclasss-visibility-in-sqltag-browser-tag-browser/38468/7 "2020-09-09T04:58:26Z")

</div>

> [@pturmel](#):
>
> The important parts of what were scan classes are now called “tag groups”.

> [@paul-griffith](#):
>
> For one thing, it’s _not_ universally relevant in 8.0+; tags can be truly event driven (reference, expression tags) and thus have _no_ tag group whatsoever.

you know.. adding tags is not the thing which You do only once at the beginning of creating a new project.  
During commissions and new additions to project we get new tags... and sometimes I (not only me) forgot to set tag group to new tags... and station starts to work very slowly or eats client's traffic... so... sometimes it's not so clear what happened and why this station works strange... but now I know that maybe I forgot to set the tag group...  
I understand that You want to make our lives much easier, but sometimes old stuff works fine

> [@pturmel](#):
>
> This ought to be fixed, btw. There were a number of columns available in v7.9 that weren’t universal either, and they worked just fine. Simply empty where not applicable.

I agree! from the other side it was the possibility to uncheck "scan class" to not see these empty fields...))

I hope someday you will bring it back) 🙏
