Thanks, I definitely knew it had to do with the SQL stored procedure coming up with some extra syntax to put into the JSON Schema. Below is a screenshot of the flow for any others pulling their hair out.
It really isn't intuitive as it should be on the flow there, but it is what it is.
I am curious though why on the first compose statement, couldn't I theoretically bypass this by going directly into the table to get the array instead of doing that additional substring logic?
i.e. The 'ResultSet' expression is this
outputs('Execute_stored_procedure_(V2)')?['body/resultsets']
but couldn't I just use this instead of all that parsing logic?
outputs['Execute_stored_procedure_(V2)')?['body/resultsets/Table1']
In any case, thanks very much!
