Forum Discussion
MISSING QUERY FEATURE from Lookup activity
- 2 years ago
I found why the following T-SQL statement was not being processed correctly:
SELECT MAX(stationId) FROM dbo.EcoCount_StationInstead, if you add an alias, like so:
SELECT MAX(stationId) AS result FROM dbo.EcoCount_Stationthen it works.
This is the kind of stuff that an intelligent engine can auto add transparently and the user will see the activity work properly. Plus, the GUI could pop up an advisory bubble notifying the user of how to specify the T-SQL statement while at the same time telling the user that it automatically did it for him. Not rocket science.
To be perfectly honest, I am so sick and tired of this BS, always trying to guess how we are supposed to enter config or SQL statements in the GUI. I mean it's mindboggling that we are still at this a year after the so-called GA release of Fabric. And this is just basic functionality we are talking about, not landing a rocket on Mars. 🙃
I found why the following T-SQL statement was not being processed correctly:
SELECT MAX(stationId)
FROM dbo.EcoCount_Station
Instead, if you add an alias, like so:
SELECT MAX(stationId) AS result
FROM dbo.EcoCount_Station
then it works.
This is the kind of stuff that an intelligent engine can auto add transparently and the user will see the activity work properly. Plus, the GUI could pop up an advisory bubble notifying the user of how to specify the T-SQL statement while at the same time telling the user that it automatically did it for him. Not rocket science.
To be perfectly honest, I am so sick and tired of this BS, always trying to guess how we are supposed to enter config or SQL statements in the GUI. I mean it's mindboggling that we are still at this a year after the so-called GA release of Fabric. And this is just basic functionality we are talking about, not landing a rocket on Mars. 🙃
This does not really work for me, it tells me the table does not exist. Any other setting necessary for writing SQL query in the lookup activity?