Trouble with Connector (Undefined Document ID)

[tr...@agilebts.com]

Hi,

I'm trying to create a process in which I need to upload a Google spreadsheet to Google Drive. I keep on getting this error

Task "Upload Google Spreadsheet" (id: 4[0] - status: ABORTED): Error while processing {P_result.document_id}
Expression P_result.document_id is undefined on line 1, column 3 in Upload Google Spreadsheet.

My process looks a little like this.

Login Google Spreadsheets--->Download Google Spreadsheet--->Login Google Documents---->Upload Google Spreadsheet.

I had to login to Google twice because I was having an authentication token problem (Invalid Auth Token) after the second step so if any light could be shed on that as well, that'd be awesome. Any help or guidance in why the document id isn't being recognized would be greatly appreciated. Thank you,

Trent

[thoshino]

Hi Trent,

It seems that Google API return is in the format of, 

entry.id

So, in your output variable of that connector, you should have ${P_result.entry.id}.

Above seems to return the uri endpoint of the document.

If it is not what you are looking for, 

entry.resourceId

might be it. 

You can look at the whole response from Google API in P_result variable in process report > Parameters tab> Internal parameters tab.

I am still not sure about your authentication problem, investigating.

Best regards,

Taka

[thoshino]

Hi Trent,

I took a look at your design.

The problem is caused by downloading a file using Spreadsheet service, and uploading file using Documents service.

The connectors for Google Client Login API looks exactly the same, but are slightly different in parameters, specifying which service to authenticate to:

https://developers.google.com/gdata/faq#clientlogin

Different authentication service results in separate Auth tokens, in client login API.

OAuth 2.0 API allows you to specify multiple services (scopes), with 1 Auth token.

For example, in your working process, you are using service=wise, then service=wirtely. You are doing it exactly as Google API requires.

Also, it might not be so visible, but if you imported the connectors from the Connectors library, then in the description tab of the connectors, it should mention which service to authenticate to.

Best regards,

Taka