# Vision - EasyChart with different tag provider and database **URL:** \ **Category:** Ignition\ **Tags:** vision\ **Created:** [August 7, 2025, 7:50pm UTC](https://forum.inductiveautomation.com/t/vision-easychart-with-different-tag-provider-and-database/109501 "2025-08-07T19:50:12Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\ **Post date:** [August 12, 2025, 4:01pm UTC](https://forum.inductiveautomation.com/t/vision-easychart-with-different-tag-provider-and-database/109501/5 "2025-08-12T16:01:06Z")
> [@seth](#): > > hadn’t seen that before Standard QualifiedPath formatting. See: > [@Get the Historical Tag Path from the Tag Path](https://forum.inductiveautomation.com/t/get-the-historical-tag-path-from-the-tag-path/61981/6): > > So, the driver is actually part of the full tag path. It is possible if you are using remote tag providers to use a gateway message handler in conjunction with this function to get what you’re looking for. If you put this function in a shared script on the same gateway as the tag provider, then it should return your historical tag path. Inspired heavily from the script provided by @paul-griffith def getHistoricalTagPath(path): from com.inductiveautomation.ignition.common import QualifiedP… --- _[View the full topic](https://forum.inductiveautomation.com/t/vision-easychart-with-different-tag-provider-and-database/109501)._