# Why Some Classes are Not Importable

**URL:** <https://forum.inductiveautomation.com/t/why-some-classes-are-not-importable/53979>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [December 10, 2021, 2:00am UTC](https://forum.inductiveautomation.com/t/why-some-classes-are-not-importable/53979 "2021-12-10T02:00:47Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![jespinmartin1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jespinmartin1/32/57175_2.png) [@jespinmartin1](https://forum.inductiveautomation.com/u/jespinmartin1)\
**Post date:** [December 10, 2021, 2:42am UTC](https://forum.inductiveautomation.com/t/why-some-classes-are-not-importable/53979/4 "2021-12-10T02:42:58Z")

</div>

> [@Get Remote Tag Provider Info via Script](https://forum.inductiveautomation.com/t/get-remote-tag-provider-info-via-script/53972/19):
>
> Also note that not all gateway classes are exposed to scripting at all. Specifically, classes supplied by modules instead of the platform. Module classes are only accessible via deliberate scripting support from the module, or rather intricate reflection techniques.

---

_[View the full topic](https://forum.inductiveautomation.com/t/why-some-classes-are-not-importable/53979)._
