Google Drive Input Tool Alteryx Server error 'NoneType' object has no attribute 'Get'

[robbinrv]

Hi all,

We've been trying to update some of our workflows from the deprecated google sheet input tools to the newer google drive input tools. However, we've been struggling to get them to work on our alteryx server.

Some info:

Alteryx Server 2022.1.1.25127 (config: DCM optional, SDK allowall)

Alteryx Designer 2022.1.1.30961 (config: SDK allowall)

Google Custom API App setup according to the documentation:https://help.alteryx.com/20223/designer/google-drive

Client and ID, token name are stored in DCM and the connection through DCM is selected with AMP engine on.

When connecting on Alteryx Designer is does go to a authentication window in the browser to allow input, after which you can see all files and select the ones we want.

When uploading to the alteryx server, no errors or warnings appear, but when we try to run it on the alteryx server it throws the error '''NoneType' object has no attribute 'Get' "

Any idea if this is expected (i.e. it doesn't work on Alteryx server) or if we have setup something wrong.

Do let me know if you require and more information, thanks in advance!

[gabrielvilella · Accepted solution]

Hi @robbinrv, please take a look at this KB article: https://community.alteryx.com/t5/Alteryx-Server-Knowledge-Base/GDCM-532-Receive-quot-error-lt-class-... 

This might be related to the tokens for the connection are not available or configured properly on the Server. 

[robbinrv]

Thanks @gabrielvilella Solution B was part of the issue indeed!

After this, we still experienced problems with setting up the googleapp following the documentation:

https://help.alteryx.com/20223/designer/google-drive

It continued to throw the same error.

When setting up the app, we also had to provide an email address for a test user, which resolved the problem in the end.

[gabrielvilella]

I am not sure at this point what is wrong. You might need to contact support. 

[robbinrv]

All good @gabrielvilella we managed to resolve the problem by adding the test user email when setting up the API credentials on google. This and the synching of DCM credentials solved the problem. Thanks again