Tim's avatar
Tim
Data Integration
11-22-2025
Status:
New Idea

Feature request: Let me connect a livemodel to a source with different table names

Let me connect a livemodel to a source with different table names

The problem:
I want to change my livemodel's connection to a different database. The new database has the same tables, but they belong to a different schema or have different names. As a result, I get a message "select a different database which includes all tables under one schema". So, I cannot change to the new database.

Feature request:
When I change the source database in an elasticube, I get an interface where I can map my datamodel's tables to the new names. I'd like the same interface for livemodels.
Better yet, let me switch to the invalid connection, and then show the error only when I try to publish the model.

Workarounds:
A) In the old database, I could create the new table names. Then I can point my livemodel to the new names before switching connection.
B) I could edit the .smodel file.
C) Tech support suggested this:
Use the REST API 2.0 PATCH /datamodels/{datamodelId}/schema/datasets/{datasetId}.
I used it with the fillowing request body, then I could change the database.
==
{
 "database": "c00845810new",
 "schemaName": "dbo",
 "type": "live",
 "connection": { "oid": "99380074-a2bb-4cd7-8bc3-7a5d20152b82" },
 "liveQuerySettings": {
   "timeout": 60000,
   "autoRefresh": false,
   "refreshRate": 30000,
   "resultLimit": 5000
 }
}

Related discussion in support case 500Pk00000s1fVCIAY.

1 Comment

  • Tim's avatar
    Tim
    Data Integration

    Another workaround is: In the datamodel, change all your tables to "Table Queries". Make them queries like "SELECT * FROM MySchema.MyView" instead of clicking on view name in the list.