Engine auto table naming process does not work.
When a table is created and a new table is created using NoConcatenate before the statement, the engine will assign a name to the table Tablename-1.
I was reported that a script that was using this implementation generating multiple tables with name Tablename-1 (creating and dropping tables) on the same script stopped working, the script would look for a resident table named Tablename-1 and it was found that at some point the table comes as Tablename-5 instead.
Environment
- Qlik Sense April 2020 Patch 4 (13.72.9)
This could also impact QlikView as both products QlikView and Qlik Sense use the same engine.
Resolution
As best developing practices, it is not recommended let the Engine auto-name fields or tables.
Cause
The behavior is considered to be working as designed.
There are several (intentional) limitations in this area where renaming a field or a table is suspended during a table-transformation step and a name based on the original name is automatically generated (i.e. concatenation of tables etc.). This is due to the fact that the table names are used as references throughout these operations with parallel tables, and as a consequence, a unique synthetic table names will be generated where necessary in order to maintain the correspondence between tables throughout the operation.
There are a number of occurrences where the auto-generated table names may differ with each reload, simply by adding or removing data records, thus affecting sort orders, load orders etc. This is why it is highly recommended to establish proper field names instead of relying on arbitrary, auto-generated, synthetic names.
R&D's engine team made a fix in the generation of unique table names relatively recently and that is most likely the cause for this reported change in behavior. This change was necessary in order to establish and maintain unique table names when the base name was occurring in multiple tables, whereas previously, the serial number added to the table name did not take this into account.
NOTE: Auto naming can occur in different scenarios, it is necessary to ensure that the tables are explicitly named to prevent the issue. Table names
Internal Investigation ID:
