Skip to content

Commit 5f52775

Browse files
authored
Merge pull request #23 from lumapps/fix/dis-2297-looker-studio
Fix/DIS-2297 - replace data studio
2 parents 9622809 + 237ed30 commit 5f52775

File tree

11 files changed

+10
-10
lines changed

11 files changed

+10
-10
lines changed

bi-tools/datastudio/README.md renamed to bi-tools/lookerstudio/README.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,19 @@
1-
# Using Google Data Studio with the Lumapps Datalake
1+
# Using Google Looker Studio with the Lumapps Datalake
22

3-
## Connecting Google Data Studio to the lumapps datalake
3+
## Connecting Google Looker Studio to the lumapps datalake
44

5-
This documentation explains how you can setup a connection from google datastudio to the Lumapps Datalake.
5+
This documentation explains how you can setup a connection from google lookerstudio to the Lumapps Datalake.
66

77

88
**prerequisite**:
99
* You already have created a service account and this service account was given proper permissions by the lumapps team.
1010

1111
### Step 1 : Create your first connector based of an example
1212

13-
DataStudio does not support natively the connection to google BigQuery via Service Account.
13+
Looker Studio does not support natively the connection to google BigQuery via Service Account.
1414

15-
If you want to connect Datastudio to BigQuery using a service account, you need to setup a custom connector.
16-
Google gives an example of how it could be done in [their documentation](https://developers.google.com/datastudio/solution/blocks/using-service-accounts)
15+
If you want to connect Looker Studio to BigQuery using a service account, you need to setup a custom connector.
16+
Google gives an example of how it could be done in [their documentation](https://developers.google.com/looker-studio/connector/use-a-service-account)
1717

1818
Lumapps tested this method and the connector we built can be used as a template.
1919
The source code can be found [here](./examples)
@@ -42,12 +42,12 @@ The source code can be found [here](./examples)
4242

4343
![Deploy](assets/4-deploy.jpg)
4444

45-
13. If your deployment is correct, you should see a **DataStudio URL**. Click on it.
45+
13. If your deployment is correct, you should see a **Looker Studio URL**. Click on it.
4646

4747
![Check deployment](assets/5-deploy-success.jpg)
4848

4949
14. **Authorize** the connector, and allow the requested permission. Then click on **Connect**
50-
15. You can now create a Google datastudio "Datastource"
50+
15. You can now create a Google Looker Studio "Datastource"
5151
1. Rename it as you like, you might share it within your organization so the name you choose need to make sense in that context.
5252
2. rename/hide dimensions as you would like.
5353
3. create new fields to expose new "Metrics" as you would like.
@@ -65,7 +65,7 @@ The source code can be found [here](./examples)
6565

6666
### Step 2 : Going further
6767

68-
In the previous step, you created your first datastudio connector and you shared it within your organization via a datastudio datastource or a datastudio report
68+
In the previous step, you created your first Looker Studio connector and you shared it within your organization via a Looker Studio datasource or a Looker Studio report
6969
You might want to explore other data in the lumapps datalake.
7070

7171
To do so :

bi-tools/datastudio/examples/appscript.json renamed to bi-tools/lookerstudio/examples/appscript.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@
1212
"oauthScopes": [
1313
"https://www.googleapis.com/auth/script.external_request"
1414
],
15-
"dataStudio": {
15+
"lookerStudio": {
1616
"name": "Lumapps Datalake",
1717
"logoUrl": "https://avatars.githubusercontent.com/u/2465187?s=200&v=4",
1818
"company": "Lumapps",

0 commit comments

Comments
 (0)