Continuous Deployment on Live Data Models

[bayram-kapti]

Hello Folks, 

How do you migrate a development data model that reads data from a Development Schema to a production data model that reads data from a Production Schema without actually creating the data model from scratch? 

Details: We're about to make our initial release of Sisense embedded dashboards. We have a Production and Development Environment in Sisense and we're quite happy to be able to migrate dashboards and data models from one env to another seamlessly. However, here is the problem. We have a very complex data model and we don't want to recreate it from scratch every time we release a new version of the dashboards.  In order to not impact the Production Dashboards while working on future versions, our Production Data Model is connected to a Production Schema in Snowflake while our Development Data Model is connected to a Development Schema in Snowflake. When we migrate DEV Dashboards and Data Models to PROD environment on Sisense, everything is good except the DATA SOURCE for our DEV Data Model. It still points to DEV Schema in Snowflake and there is no way to change the schema even though the underlying table names are same in both schemas. And again, we don't want to create the data models from scratch for Production Environment. 

Has anyone find a solution for this? Thanks!

[irismaessen]

You should have an option on the Data tab within the user interface to change the connection or the provider on a Data Source . That should allow you to switch between Dev and Production.

Open the Model, then Data Sources > Connection Settings > Change Connection/Provider/Database

Good luck!

[bayram-kapti]

Thank you for your reply @irismaessen . Unfortunately, that's not working as I get this error when I try to switch from DEV schema to PROD schema:

```All tables must belong to the same schema, please select a different database which includes all tables under one schema.```

[Ophir_Buchman · Accepted solution]

@bayram-kapti,

A simple way to do so is:

1. Export your data model

2. Edit the smodel JSON file and update the "connection" section with the correct schema name

[Ophir_Buchman]

Hi @bayram-kapti,

Can this thread be closed? Was your issue resolved?

[bayram-kapti]

It has worked @Ophir_Buchman Thanks for your answer!