# \[BUG-13522\] system.util.getSessionInfo possible bug

**URL:** <https://forum.inductiveautomation.com/t/bug-13522-system-util-getsessioninfo-possible-bug/23571>\
**Category:** Ignition Early Access\
**Created:** [March 25, 2019, 3:31pm UTC](https://forum.inductiveautomation.com/t/bug-13522-system-util-getsessioninfo-possible-bug/23571 "2019-03-25T15:31:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![cwaddoups](https://avatars.discourse-cdn.com/v4/letter/c/43a26b/32.png) [@cwaddoups](https://forum.inductiveautomation.com/u/cwaddoups)\
**Post date:** [March 25, 2019, 3:31pm UTC](https://forum.inductiveautomation.com/t/bug-13522-system-util-getsessioninfo-possible-bug/23571/1 "2019-03-25T15:31:23Z")

</div>

The project column in the dataset that is returned by system.util.getSessionInfo() in 8.0 does not act in the same way that it did in 7.9. In 7.9 the project column returned whatever project the designer or client in vision that was open. In 8.0 it seems to return the project in which the method was called in. For example I have a global project and two daughter projects and a designer opened for all three. If I call the method in the global project the project column for all three rows in my dataset reads global, if I call the method in one of the daughter project the project column for all three rows reads whatever the name of the daughter project is. I am on version b2019032102

---

<div class="post-metadata">

**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 25, 2019, 3:41pm UTC](https://forum.inductiveautomation.com/t/bug-13522-system-util-getsessioninfo-possible-bug/23571/2 "2019-03-25T15:41:16Z")

</div>

I can’t tell from your description what you expect the behavior to be and why you think the current behavior is wrong.

---

<div class="post-metadata">

**Author:** ![cwaddoups](https://avatars.discourse-cdn.com/v4/letter/c/43a26b/32.png) [@cwaddoups](https://forum.inductiveautomation.com/u/cwaddoups)\
**Post date:** [March 25, 2019, 3:49pm UTC](https://forum.inductiveautomation.com/t/bug-13522-system-util-getsessioninfo-possible-bug/23571/3 "2019-03-25T15:49:30Z")

</div>

Ok, in 7.9 when I run util.getSessionInfo() I get a dataset that returns all the sessions that are currently open. Say I have three projects (project A, project B, project C) and a client open for each project. The dataset that is returned has a column called project. The column would read (project A, project B, project C). If I have two clients open for A, none for B, and one for C the dataset would read (project A, project A, project C).

In 8.0 the project column returns whichever project called the method so I have a client open for each project and call the method from A the dataset returns (project A, project A, project A). I call the method in C and it returns (project C, project C, project C). It does not return which project the respective client or designer has open it returns the project that called the method.

---

<div class="post-metadata">

**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 25, 2019, 3:51pm UTC](https://forum.inductiveautomation.com/t/bug-13522-system-util-getsessioninfo-possible-bug/23571/4 "2019-03-25T15:51:12Z")

</div>

Ok thanks, I understand now.

---

<div class="post-metadata">

**Author:** ![awalker](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/awalker/32/6874_2.png) [@awalker](https://forum.inductiveautomation.com/u/awalker)\
**Post date:** [April 22, 2019, 4:33pm UTC](https://forum.inductiveautomation.com/t/bug-13522-system-util-getsessioninfo-possible-bug/23571/5 "2019-04-22T16:33:17Z")

</div>

This issue was fixed in the build that was uploaded today (4/22). Please let us know if you continue to see this behavior after upgrading.
