From 11.7 onwards, it is no longer possible to perform a freeform search query within a TM when the query contains tmassetid The following error would be displayed: |
A defect has been raised to suggest that the illegal term search is refined to not block words that may contain restricted terms within the middle of the word. The defect ID = CRQ-31030 There is a suggested workaround that has worked for some customers with this issue: The workaround used for a SQL Server deployment is described below: SQL Server provides the ability to have a synonym for a column name, as described in this Stack Exchange post. If you want to retain the table name but refer to an existing column by a new name, a computed column will do this for you. The computed value of the column will be just the value of the existing column. alter table [dbo].[Product] Now you can write select The two columns will have the same value, always. If you reference only the computed column my guess is there won't even be a run-time overhead. This change can be applied as follows: alter table ZTMxxxx_translations In the User Interface, for your working TM you will see the TMGROUPID. You will need to get the xxxx value for the above query by using the following query to have the TM databaseid. This is the value of xxxx in the earlier query. select * from tmGrouptmDatabases |
This is linked to recent security changes in the product which is blocking certain key words when doing SQL based queries to prevent cyber attacks. The official documentation states: Starting with WorldServer 11.7.3, the following terms and characters are hard-coded as illegal terms: ; , -- , .. , @ , SELECT , DROP , DELETE , INSERT , UPDATE , ALTER , EXEC , UNION , UNION ALL , EXISTS , WAITFOR , WAITFOR DELAY , DECLARE , SET , SLEEP , SLEEPTIME , GET_HOST_ADDRESS , RECEIVE_MESSAGE , SYS. , DB_NAME .The reason that tmassetid is blocked is down to the fact it contains the word SET in the middle of the whole word. |