Ampersand in SQL source.
Posted: Tue Jan 13, 2015 10:15 am
Hello All,
I am using TM1 10.2.2 FP2 (not updated in my profile as I use many versions). I have observed something that I hope has been seen before and someone may have a resolution for.
I have a TI, created in Performance Modeller which brings in various lines to a TM1 cube from an ODBC source. It fails for just one line and that line contains an ampersand in one of the element records. All other lines are working as expected. I have an asciioutput on the data tab that also creates a file so I can see which records are being processed. The file is being created as expected, but does not contain any records that relate to the source items which contains the ampersand. This would indicate that the TI engine does not recognise these as valid records and is just negating them. The data tab contains just cellputn statements and sets a single variable.
I have amended the source SQL statement to show only the line containing the ampersand. I can see it in the TI preview, but when I run the process, no file is created on account of the asciioutput, indicating that the data tab does not execute.
I have also amended the SQL statement to contain CHR(38) in place of the ampersand, again, I can see the line in the preview, but no file is exported indicating that the data tab has not executed.
Has anyone else encountered such an issue with an ODBC source containing an ampersand and found a solution. If so, I hope you would be willing to share a resolution.
I am using TM1 10.2.2 FP2 (not updated in my profile as I use many versions). I have observed something that I hope has been seen before and someone may have a resolution for.
I have a TI, created in Performance Modeller which brings in various lines to a TM1 cube from an ODBC source. It fails for just one line and that line contains an ampersand in one of the element records. All other lines are working as expected. I have an asciioutput on the data tab that also creates a file so I can see which records are being processed. The file is being created as expected, but does not contain any records that relate to the source items which contains the ampersand. This would indicate that the TI engine does not recognise these as valid records and is just negating them. The data tab contains just cellputn statements and sets a single variable.
I have amended the source SQL statement to show only the line containing the ampersand. I can see it in the TI preview, but when I run the process, no file is created on account of the asciioutput, indicating that the data tab does not execute.
I have also amended the SQL statement to contain CHR(38) in place of the ampersand, again, I can see the line in the preview, but no file is exported indicating that the data tab has not executed.
Has anyone else encountered such an issue with an ODBC source containing an ampersand and found a solution. If so, I hope you would be willing to share a resolution.