Google Drive Output Not Found in Our Alteryx Distribution Since 24.1

[hellyars]

I will try this again.

Since updating to 24.1 I am no longer able to use either the Google Drive Input or Output tools to connect to Google Drive.

The ability to sing in via an internet browser does not appear (image right).  Only the connect using data connection  manager appears (image left)

Worse.  Existing workflows that used the sign in via a browser no longer can access Google Drive (left image).

Instead, running an existing workflow with a previously working Google Output tool connection results in a new errror

Error: Google Drive Output (169): Version 3.8 was not found in our alteryx distribution. Please select another version.

New Markeplace  Add-Ons tool shows it installed (with no updates).  Note also the Unhandled Exception.   This also happens when trying to use the Google Drive Input/Output tools since updating to 24.1.  

Again.  This all worked before I updated to 24.1.   I have a dozen or so workflows with Google Drive Output tools that previously worked.

What changed?

[apathetichell]

@hellyars - I guess my recommendation would be to uninstall and reinstall? I'd recommend not upgrading to 24.1 unless necessary (ie you need the external browser auth to Server). I could see a sitiuation where that change through off something in the macros which use browser auth.

[mkosmicki1]

@apathetichell & @hellyars we tried to roll back to the previous 2023 version....and were still getting the error. We are only reading files in from Google Drive. The only thing we found that worked was to uncheck "First row contains field names" on the Configure File tab in the configuration pane. Then you can rename the columns with a select tool. 

A real PITA for sure.

[Carolyn]

I'm having the same issue. I just use 2024.1 to test (read as: play with new features) and my "real" version is 2023.1 so it won't cause an issue in Production, but quite annoying!

[mkosmicki1]

Update on our Google Drive situation:

With identical setups, some of us can use the Google Drive input tool and some of us can't.

We are having the same issue with our Tableau output tool. 

In addition, there is no guarantee that any tools will work on Alteryx server. They may work on Monday's scheduled run and then fail on Tuesday's scheduled run and then fail for a couple of weeks and start working again. In the meantime, there are no errors when running the same workflow on designer desktop. 

This has us considering moving everything we can into code (Python, R, SQL, etc) and away from Alteryx so we can dump the expensive tool that doesn't seem to work reliably any longer. Sad to see Alteryx becoming a useless software package.

[apathetichell]

Hypothesis:

This is a huge bug. 3.8 is the Python version. 24.1 is using a different Python version. The tool has a  hard coded location assuming the python version is 3.8 - hence the 3.8 error.

My suggestion to @mkosmicki1 was a) uninstall. b) force uinstall the  python venv/version created in 24.1 c) reinstall an older version. open python tool. run python--version to check the version. 

[apathetichell]

I have another potential fix!

use something like 7zip to open your .yxi file of your tool.

find your maingest.json. It will look like:

{

    "version": "3.8",

    "entry_point": "GoogleDriveInput\\main.pyz",

    "tool_package": "ayx_plugins",

    "tool_name": "GoogleDriveOutput"

}

change the version to 3.10

save.

save your .yxi

reinstall your .yxi.

check your tool.

I might play around with this this weekend but it'll involve installing 2024.1 on a VM so I don't have to deal with it.

[apathetichell]

in an install - I see my google input/output manifest.json located at "C:\Users\{}\AppData\Roaming\Alteryx\Tools\GoogleDriveOutput\manifest.json" - that's the location which would need the edit.

[apathetichell]

@hellyars If you want to be the guinea pig - here's a workflow to fix the manifest error. NOTE - you may need to add a second formula tool to replace 3.8.5 with 3.10.13. I'd also recommend running in test mode first. test mode copies over your current manifest.json files with the new values. Note - the outer workflow will probably find 1,000 manifest.json files many (99.9%) of which you may not be able to access in non-elevated Alteryx modes. The next step of the workflow clarifies that you are only looking at manifest.json's related to Alteryx.

[AndresR]

@hellyars To enable login via the web browser, you would need to make DCM optional (in User Settings)