Skip to content


GPRollingColumn – Smartconnect 2017

Mick Egan asked 6 years ago
We have found with Smartconnect 2017 the GlobalRollingColumn is not passing through to the SQL Tasks, whereas in previous Smartconnect versions we could use the GlobalRollingColumn to assist with sql update statements.
Patrick Roth Staff answered 6 years ago
This is a bug on SC – the GlobalRollingColumn isn’t being set internally as it should be so when accessed via a task it is empty.
This issue and other “global variable” issues are going to be fixed in a not-yet-released SC 2017 hotfix coming out soon.
Until then, the only workaround is to roll back to your previous version of SmartConnect as SC was the last published release where this was working.
David Dery replied 6 years ago

Patrick – Any estimated release date for the hotfix?

Mick Egan replied 6 years ago

Thanks for the update.

Patrick Roth Staff replied 6 years ago


Just released that hotfix yesterday! replied 6 years ago

perfect, we will download and test.

Matt Brook replied 3 years ago


I am currently using SC and I don’t have a Global Variable named ‘GlobalRollingColumn’ and when I try to Add one called ‘GlobalRollingColumn’, it capitalizes the name and wants me to add ‘GBL_’ in front of the name.

How can I get the Global Variable into the System, so I can updated the Source Data with the Newly Created Journal Number?

Mick Egan answered 6 years ago
Looks like in the latest release the GlobalLastError and GlobalRunErrors are becoming blank.
John replied 6 years ago

Same here, I updated to and the GlobalLastError is blank. Any update?

If you would like to submit an answer or comment, please sign in to the eOne portal.