Skip to content
+1-888-319-3663

COMMUNITY FORUM

GPRollingColumn – Smartconnect 2017

Mick Egan asked 4 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.
Mick
Answers
Patrick Roth Staff answered 4 years ago
Mick,
This is a bug on SC 20.17.0.11 – 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 20.16.1.24 was the last published release where this was working.
David Dery replied 4 years ago

Patrick – Any estimated release date for the hotfix?

Mick Egan replied 4 years ago

Thanks for the update.
Mick

Patrick Roth Staff replied 4 years ago

Mick,

Just released that hotfix yesterday!

mick.egan@nexon.com.au replied 4 years ago

perfect, we will download and test.
Mick

Matt Brook replied 2 years ago

Mick,

I am currently using SC 20.16.1.24 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 4 years ago
Patrick,
Looks like in the latest release the GlobalLastError and GlobalRunErrors are becoming blank.
Mick
 
John replied 4 years ago

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


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