Some GoodData Writer loads may have failed with weird "Target model is invalid" errors in recent few hours. This had been caused by a bug in data modelling part of the application which we already fixed. We are sorry for any inconveniences, it should work as expected now.
There are some under the hood improvements to GoodData Writer which allow you to rename datasets already exported to GoodData and freely rename attributes and facts (to this moment GoodData Writer has been automatically adding name of dataset to attribute/fact title).
Also there is possibility to change default GoodData identifiers for datasets and their columns. This is suitable especially for projects migrated from CloudConnect, otherwise you won't need this feature probably.
This improvement is available immediately for new writers but existing ones will be migrated in several waves during upcoming days.
Date dimensions management in GoodData Writer gets improved UI. In addition you can specify custom GoodData identifiers and templates for your dimensions.
Keboola Connection now supports Multi-Factor Authentication (sometimes called two-step verification) using Google Authenticator app. It can be activated in Account section accessible from user menu. You will need to download the app first, version for iPhone is here and for Android here. This feature adds verification by 6-digit code generated by the app after entering of username and password and so increases safety of your account.
Activation looks like this:
And login will look like this:
Geocoding component now allows to configure which data provider will be used and in which locale the data will be processed. You can choose from Google Maps, Google Maps for Business, Bing Maps, Yandex, MapQuest, TomTom, OpenCage and OpenStreetMap. See Apiary documentation for more details about configuration. Notice that you need to obtain API key for most services first.
Original mode of the component which used mixed providers with our own API keys still works (for configuration tables without attribute provider) but is only temporary to allow you to migrate and will be removed after few weeks.
According to our previous notice, AdWords Extractor has been updated to use new version v201506 of AdWords API. You can start using new metrics.
Listing of users (GET /users), projects (GET /projects) and project users (GET /project-users) has been limited to 10000 results. To this moment listing of much more results didn't work anyway, Writer returned error instead of the listing. So if your writer contains more results and you have a script which process them, you will need to update it to support pagination. It works using parameters offset and limit (see docs for more information)
New version v201506 of AdWords API has been released yesterday and our extractor will update in the beginning of August. Please be sure to update your configuration to not use unsupported metric names till the end of July. Also do not use new metrics until the update, we will let you know about it.
We are investigating infrastructure issues affecting most of extractors and writers. Thanks for your patience.
UPDATE 0:33am PST / 9:33 CEST: Issue has been resolved, we'll try to restart all failed orchestrations, if we miss anything, please feel free to restart by yourself. Sorry for any inconvenience.
We have been fixing multiple errors regarding proper handling of GoodData maintenance during Saturday which could cause failing of some Writer's jobs. All problems were solved and shouldn't appear again. We apologize for any inconvenience.