# Bug when choosing driving tags using remote tag providers

**URL:** <https://forum.inductiveautomation.com/t/bug-when-choosing-driving-tags-using-remote-tag-providers/28580>\
**Category:** Ignition Early Access\
**Created:** [September 26, 2019, 1:14pm UTC](https://forum.inductiveautomation.com/t/bug-when-choosing-driving-tags-using-remote-tag-providers/28580 "2019-09-26T13:14:30Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tordvd](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tordvd/32/11525_2.png) [@tordvd](https://forum.inductiveautomation.com/u/tordvd)\
**Post date:** [September 26, 2019, 1:14pm UTC](https://forum.inductiveautomation.com/t/bug-when-choosing-driving-tags-using-remote-tag-providers/28580/1 "2019-09-26T13:14:30Z")

</div>

I am not sure if this is a bug or not. But I struggled some with the following:

If you are using a remote tag provider and would like to have  
\*[remProv]tag01 OPC tag to “read using Polled”  
when  
\*[remProv]tag2 OPC changes.

Meaning that [remProv]tag2 would be the driving tag for your tag group “group1”.  
[remProv]tag1 further exist then under the tag group “group1”

Here comes the bug. When choosing the driving expression using the vision editor and the built-in tag browser: The editor prefixes the tag with the [remProv] while it should actually be prefixed as [default] (or maybe[~])