Eventstream custom SQL code not working due to an invalid input name

[PaxDataEngineer]

Eventstream has a custom SQL code capability. This capability always fails due to an "invalid input name", most likely due to a hyphen in the stream name. The problem is that there's no option to rename the stream, and it includes a hyphen by default. I assume since it's a new feature that this is a bug. I'd recommend to either allow the user to change the default stream name, or fix the SQL code capability so that it handles hyphens in input/output names.

[datacoffee]

Hi @PaxDataEngineer 

Currently the SQL code editor is in preview and we can expect some challenges with the service.
With that said, I cannot recreate the issue on my development environment. 
If I create a custom SQL job to my stream and do not alter it at all, it works OOTB. 

Though, I can create the error message if I'm using non-streaming SQL functions and names.
You might already know this, the SQL code behind the Eventstream is the same as the Azure Streaming analytics and is a subset of functionality - you can read the entire docs here: Azure Stream Analytics & Fabric Eventstream Query Language Reference - Stream Analytics Query | Micr...

I hope you can make it work in your environment

[PaxDataEngineer]

So it does say "no problem detected" when just using the simple "SELECT * INTO [Output] FROM..." but after saving it you can see the error specifying that the stream name is invalid. 

[datacoffee]

Ah yes. I see that.

I guess you are right with the small bug.

My guess it is due to the underscore in your stream name.

Let's see what the Microsoft team here in the community says 😀