Clarifications Regarding Version Upgrade from 2023.2 to 2024.2

EN6924

Hi,

I’ll be performing a version upgrade from 2023.2 to 2024.2 and just have 4 questions I’d like to clarify:

1. Is it necessary to manually install the Connectors after the upgrade?

2. Do I need to manually install Python 3.10 on the server once the upgrade is complete?

3. For users running flows that utilize Python 3.8, will they also need to install Python 3.10 on their local machines?

4. Are there any other potential challenges or considerations I should be aware of during this upgrade?

Thanks in advance!

KGT

Directly addressed below to the best of my thoughts right now... but the core principle is to not half perform the steps related to Python.

Alteryx installer takes care of the Python version. You do not need to do ANYTHING with the python version that is not a part of Alteryx or Alteryx Tool installers. When yxi tools that use Python are installed, they connect to the current Python Version in the Alteryx engine. Hence, they need to be re-installed after that version changes. Sometimes that will be a new version of the connector/tool as well. If you do those installs in the wrong order, it will not work.

Answers

1. Yes. Python version has been upgraded to 3.10 in 2024.1 and so the connectors need to be re-installed, so they can be installed and working on that version (they will currently think they are running on v3.8)
2. No, the Python version will install with the main Alteryx installer.
3. Not exactly. If the tools are the same, then they should translate, but this is dependent on whether the tool is pushed with the workflow etc. The answer to your question is definitely no, but that's not a total answer, as there are many different ways "users running flows" could work.
4. a. Don't skip steps or think that you can get away with half doing something around the Python versions. The python version is embedded into the core Alteryx Engine (as opposed to R that is separate due to the licensing type). So, when upgrading versions that have a large Python change, make sure that the order etc is correct, as the base version needs to be upgraded and then the tools installed, so that they know what to work with.
5. b. Make note of anything that caused issues or was a little janky, to see if you can set the system up in a way that enables easier upgrades next time.