Google Sheets Component Release Notes
A limitation was introduced when migrating to Google Sheets "v4 API", the ability to filter data directly when extracting data from Google Sheets was not possible anymore, because of the changes of Google’s API.
Filtering was still possible in Mappings and Processes, but it was performed after retrieving data, by using a filter in "staging area" location.
We unlocked this limitation by supporting again filtering directly on "source" location when extracting data from Google Sheets.
Semarchy xDI Designer 20.2.0 introduces an improvement which allows Components and Modules definition to provide themselves the proper JDBC drivers classes and URLs, for the connection wizard to automatically adapt depending on the Module selected.
This Component has therefore been updated to take into account this improvement and provide the necessary JDBC drivers classes and URLs information.
Google Sheet Component was originally using Google’s "v3 API" to communicate and operate with Google Sheet.
This API is planned to be removed by Google soon which advise to now use the currently supported "v4 API" instead.
You can find more information about the removal of this Google API at the following Google Article.
We therefore worked on this new Component which will use the new currently supported "v4 API".
The new Google "v4 API" changes a lot how to perform operations on Google Sheets and offers better performances.
There are however some limitations on this version due to the changes that you must have in mind:
When reading data from Google Sheets in a Mapping or Process, it is not possible to use filters yet to filter the data returned
Google’s "v4 API" does not allow to retrieve all the sheets of a given user as it was possible before, so for now you cannot reverse the list of Google Sheets in Metadata, but only standalone Sheets by specifying their identifier.
We are working on those limitations to unlock them in a future version.
DI-5079: The generation of Google Sheets tokens with the command-line utility fails with Java 11.
DI-5894: When generating a Google Sheets token with the command-line utility, some accounts throw the
Error 400 - Invalid Requesterror.
DI-6164: Multiple third-party libraries upgrade.
DI-6461: When running multiple data flows with different OAuth2 tokens, the tokens are mismatched with each other, leading to authentication errors.
DI-5894: "Error 400 - Invalid Request" may be thrown by some accounts when trying to generate a Google Sheets token with the command-line utility.
DI-5079: The generation of Google Sheets tokens with the command-line utility fails with java 11 with the error "java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter".