[ https://issues.jboss.org/browse/TEIIDDES-1614?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-1614: ------------------------------------------ Projected columns for procedures may also include out/inout/return parameters. They are not interchangable. The old code was problematic in several ways. First it stored the entire "results command" on the resolved create, which was not necessary and led to clone and improper usage later. Second it didn't properly differentiate between projected columns and result set columns, which is needed in virtual procedure invocation to make parameter assignments based upon out/inout/return values. Third the code in general did not properly account for the case where there is no result set defined in the metadata - which is somewhat the crux of this issue. Designer is giving us metadata for the procedure that is entirely valid - no result set and no parameters and asking us to resolve the procedure - and yet also wants to know the possible result set columns. I'm not sure what that means. Could you elaborate? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira