Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


Praxis Consulting
2024-11-15T19:28:12Z
I've been on 9.9.7 for a while and want to upgrade. Can I upgrade straight to 12.01, or should I upgrade first to 10 and then 11?

Thanks
Sponsor
Forum information
AHTECH
2024-12-09T21:50:10Z
Our team is attempting from 9.7.5 do you have any notes from your testing to share?
2025-03-11T11:10:17Z
Hi we're also looking at moving from 9.2.5 to 12.1.3 - could anyone share any notes or challenges that they experienced during a similar upgrade?

Thanks,

Dominic
2025-03-11T11:14:11Z
Hi we're also looking at moving from 9.2.5 to 12.1.3 - could anyone share any notes or challenges that they experienced during a similar upgrade?

Thanks,

Dominic
tonyp
2025-04-03T02:53:36Z
@ttsupport@ttint.com
Did you end up going to 12.1.3? If so, any issues?
thomas
2025-04-07T08:29:55Z
I haven't tried upgrading myself, but I would be wary of the bug talked about in this post: https://www.visualcron.c...aspx?g=Posts&t=10799 . From reading through the changelogs, I can't see that they have fixed it yet
E2021
2025-08-04T18:18:01Z
Originally Posted by: thomas 

I haven't tried upgrading myself, but I would be wary of the bug talked about in this post: https://www.visualcron.c...aspx?g=Posts&t=10799 . From reading through the changelogs, I can't see that they have fixed it yet



I met that issue as well or something very similar, going from 11.2.1 to 11.2.2, where the job should read a tabular list and write each line as an item in Sharepoint list, by looping through each line. I am unable to figure out if it was fixed and support is not responding since I was initially told they knew of the issue.
Joey S
2025-08-07T16:25:48Z
I would not think that a big jump in versions will cause any new or worse issues than doing it incrementally

We used to see a lot of issues simply going to the newest version if the jobs we made were originally created in v8 or lower and the fix was always just to remake the jobs. There was probably something not being added in the xml or something that did not translate as expected and remaking the job would create the correct values
Scroll to Top