Renaming direct query table does not change underlying name that is used. Correct functionality or a bug?
When renaming a direct query table, the original table name is often used in other areas (security scripts, join statements as shown in attached image). Is this the intended functionality? As a user, I would expect a renamed table to update the used table name everywhere. In a multiple developer scenario: one dev could rename the table without another dev's knowledge, leading to increased time needed to find the correct name to use in scripts, etc.
2 replies
-
Hi Paul,
Working as designed.
The actual database join defined by the model is shown in your red box. This is the join which will be passed down to the database as part of the query generated by Pyramid. Obviously, this has to be the actual table name, not the new name, as otherwise the database engine will not recognise it. Your new table name will be reflected in the Pyramid UI in Discover, Formulate etc., but we have to pass the actual table name in the query.
Hope that helps.
Ian
-
Hi Paul Narup
I see in the screenshot you're showing a query, not a table.
What Ian wrote is also true for queries - once created, a query has an internal name that cannot be altered - only the display name can be changed.
It is done this way because everything "under the hood" is using this name - when looking to recognize the query, it's columns, measures, relationships etc. The only thing that can be changed is the display name - so if you have created a simple calculation (MeasureA/MeasureB) - it will keep working even if you change the display name.