Recommendation: After changing the feature column 's Data type from "Single" to "String", the training should be completed successfully for Data source from SQL Server.

[v-Hailishi]

System Information (please complete the following information):
Windows OS: Windows-11-Enterprise-21H2
ML.Net Model Builder 2019&2022: 16.13.5.2221801 (Main Build)
Microsoft Visual Studio Enterprise: 2019(16.11.11); 2022(17.1.3)
.Net: 5.0 & 6.0

Describe the bug

• On which step of the process did you run into an issue: Training Recommendation with Data source from SQLPassword and SQL Server Database File.

TestMatrix
https://testpass.blob.core.windows.net/test-pass-data/recommendation-ratings.csv
https://testpass.blob.core.windows.net/test-pass-data/iris.mdf

To Reproduce
Steps to reproduce the behavior:

1. Pre-requisite: Do Pre-requisites/SQLPassword before repro this issue.
2. Select Create a new project from the Visual Studio start window;
3. Choose the C# Console App (.NET Core) project template;
4. Add model builder by right click on the project;
5. Select Recommendation scenario>Local (CPU);
6. On Data page, select>SQL Server>Microsoft SQL Server>SQL Server Authentication to input the data source;
   Or select>SQL Server>Microsoft SQL Server Database File to input the data source;
7. Choose "rating" as Label, "userId" as User, "movieId" as Item and then click "Avanced data option".
8. Change "rating" column's Data type to "Single".
9. Change "timestamp" column 's Data type from "Single" to "String" and save it.
10. Click Start training button, prompt model builder error as below screenshot.

Expected behavior
The training should be completed successfully after changing the feature column 's Data type from "Single" to "String".

Screenshots
Data settings:

Error screenshot:

Additional context
When do the same thing for the .csv file data source, the training can be completed successfully.

[beccamc]

If we implement the custom SQL query it would make sense to just hide the advanced data options columns.

[luisquintanilla]

Work being tracked as part of #1935. Closing for now.

[v-Hailishi]

The bug has been fixed on the latest main build: 16.13.10.2251801