If a user creates a stored procedure that is supposed to return a dataset with aliased column names, Ignition may have an issue with not reading in the aliased column names, and will instead use the original column names. An example of this would be with executing a procedure call in scripting, and reading in the result set, like so:
call = system.db.createSProcCall("procedure_name")
result_set = call.getResultSet()
Go into the Ignition Gateway, and under the "Configure" tab, navigate to Databases->Connections, and click "Edit" next to the MySQL database connection that is having issues. In the "Extra Connection Properties" section, add the following parameter to any existing parameters:
Click on the "Save Changes" button at the bottom of the page to apply the change.