![]() ![]() ![]() I can assume that it's due to YellowfinBI's manipulation to the view's underlying SQL. For example, I created a Freehand view with a CTE and even though my SQL is valid I received an error. The SQL is available if you click on the info button next to the title of the view for example:Īlthough it is available there, it is not available on errors and it is the SQL from the view, not the SQL after the report manipulates it. He is speaking about cases when there is an error. Can you please give me your use case with a corresponding screenshot of where you're not seeing the option to view the SQL, so I can get a better idea of what you're referring to? However, Yellowfin does say it had an error retreiving the data from the database, so that narrows the issue down to something at the db level, which is unrelated to the SQL:īeing able to view the SQL here wouldn't help with troubleshooting the issue in this case.īasically, since what you're asking for is to see the SQL Error in the View SQL tab, I'm looking for an example where a SQL error is what is causing a report not to load. `lastfmimportdata`.`Song`from 'Song' to 'Country,' which is an unpopulated Column in my database. The only way I was able to get an error message where I couldn't view the SQL is when I created a Column with no values, and switched the last part of this codeĬOUNT(`lastfmimportdata`.`Artist`) / COUNT(`lastfmimportdata`.`Album`), Both of your screenshots are showing the option to view the SQL even though your query didn't return any results, which I've also been able to replicate: Unfortunately, I'm unsure what you are referring to here.
0 Comments
Leave a Reply. |