Azure Data Factory Pipeline scenarios with 'Invalid Column Name' scenarios When Using Derived Column Transformation
I've tried everything I can think of but I've tried everything I can think of but I'm reviewing some code and I'm sure I'm missing something obvious here, but I'm working with an scenario with Azure Data Factory where my pipeline fails during execution. I'm trying to use a Derived Column transformation to create a new column based on an existing one, but I keep getting an behavior message stating `"Invalid Column Name: <column_name>"`. This happens despite the fact that the column exists in the source data. Here is the configuration I have: 1. The source is an Azure SQL Database, and the query I'm using is: ```sql SELECT id, name, created_at FROM my_table ``` 2. In the Derived Column transformation, I'm trying to create a new column called `created_date` using the expression: ``` toString(created_at) ``` 3. The mapping section shows that `created_at` is correctly recognized. I've also verified that the `created_at` column is not null and correctly formatted in the source data. The pipeline runs fine when I remove the Derived Column transformation, but it fails when I include it. I tried re-validating the expression and even changing the name of the new column, but the behavior continues. Does anyone have insights on why this behavior might be occurring or how I can troubleshoot this further? Are there specific limitations with column names or data types in Derived Column transformations that I might be missing? I'm working on a web app that needs to handle this. Am I missing something obvious? I'm on Linux using the latest version of Sql. Any examples would be super helpful. I've been using Sql for about a year now. I've been using Sql for about a year now. I'd be grateful for any help.