Changing data source location
Last updated
Last updated
Builder now enables you to modify the location or connection of your data sources easily using the 'Change data source’ option available in the source card. This functionality ensures that map configurations remain consistent as long as the updated data sources maintain the same field names and types. For any components where a property cannot be identified, the map component will revert to its default settings.
Table Data Sources:
Navigate to the source card panel and click on the three dots menu.
Select the ‘Change data source’ option and locate the new data source.
Once the new dataset is identified, click 'Change source'.
SQL Query Data Sources:
Access the three dots menu in the source card panel to update the connection.
Alternatively, in the SQL Editor panel, click on the connection information in the top-right corner to modify it.
Select your desired connection and click ‘Change Source’.
If the new data source contains the same fields with matching names and types, the map will retain its existing configuration, and no changes are expected. However, if some properties used in the map are missing in the updated data source, the following behavior should be expected:
Styling and Interactions:
If a property used in interactions (e.g., hover or click actions) is missing in the new data source, those interactions will be removed.
If a property used for layer styling (e.g., coloring by a column) is no longer available, the layer will revert to the default style.
Widgets:
Widgets linked to missing properties will remain visible, and their configurations will be preserved.
As an Editor, you can manually select a new column from the dropdown menu in the widget configuration panel or remove the widget entirely if no replacement column exists.
SQL Parameters:
The updated connection must have access to the tables referred to in your custom SQL query. If not, you’ll need to update the query to refer to the relevant table locations.
For SQL Parameters, ensure that the updated query is still valid so that parameter controls continue to work as expected.
