Connect NBG rate
The NBG rate source loads the National Bank's daily exchange rates into the Lake, one row per day. Use it when you need exchange rates as a table you can join to your own dated data and keep up to date.
Create an NBG rate source
- Click Add datasource in the Lake and choose NBG Exchange Rate in the picker. You find it under Popular, or in the Communication & Collaboration category; Supported connectors lists every source type.
- Fill in the General section: a Name of at least 3 characters, a Code of letters and numbers (at least 2 characters), and a Folder if you keep sources in folders.
- In the Connection section, set these fields:
| Setting | What it does | Default |
|---|
| Language | Sets the language of the rates the source returns: Georgian or English. | Georgian |
| Initial Date | The earliest day a full load reads. Choose a date between 2016-01-01 and today. | None, you choose one |
| Sync Days | How far back a later load reads. Choose days between 1 and 367. | 1 |
- Click Test Connection if you want to check the settings before you save. It is optional.
- Click Add. On a saved source the same button reads Save; on a copy, Duplicate.
- Import the tables you need from the source; see Import tables.
A collapsible Documentation panel sits beside the form.
What each load reads
- The first load of an empty table reads every day from Initial Date up to the run date.
- Later loads read a window that ends on the run date and reaches back the number of days set in Sync Days. Days before the window keep the values loaded earlier.
- Each day lands as one row: the date and the day's rates as JSON.
- Tables from this source can use only the Full Reload (Upsert) sync type. The other sync types are greyed out for them; see Choose a sync type.
Change or copy a source
- Open the source from the Lake tree to change Language, Initial Date or Sync Days, then click Save.
- To copy a source, open its menu in the Lake tree and choose Duplicate. The copy keeps the settings and asks for a new Name and Code.
- Each save confirms itself in a notification: Connection added successfully, Connection updated successfully or Connection duplicated successfully.
Limits and edge cases
- Initial Date accepts days from 2016-01-01 to today. Outside that range, the form reports Date must be between 2016-01-01 and current date.
- Sync Days accepts 1 to 367. Outside that range, the form reports Sync Days must be between 1 and 367.
- Name and Code are locked after the source is created.
- The source needs no credentials; the form has no sign-in fields.
Questions, answered
What does the Language setting change?
It sets the language of the rates the source returns. Choose Georgian (the default) or English.
How far back does the first load go?
When a table is empty, its first load reads every day from Initial Date up to the run date. Set Initial Date to the earliest day you need; the field accepts 2016-01-01 to today.
How far back does a later load read?
A load on a table that already holds rows reads a window that ends on the run date and reaches back the number of days set in Sync Days. Days before the window keep the values loaded earlier.
What do the loaded rows look like?
Each day lands as one row: the date and the day's rates as JSON.
Which sync type can a table on this source use?
Only Full Reload (Upsert). The other sync types are greyed out for its tables. See Choose a sync type.
Can I change or copy a saved source?
Language, Initial Date and Sync Days stay editable; open the source from the Lake tree, change them and click Save. Name and Code are locked after the source is created. To give it another name, duplicate it and set a new name and code on the copy.
Where does a save error appear?
The form shows the reason from the server. When the server sends none, it falls back to Failed to edit connection or Failed to create connection. A failed edit shows the error inside the form; a failed new source shows a notification.