[ https://issues.jboss.org/browse/TEIID-3471?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3471: ------------------------------------- [~shawkins] It looks like OReva can handle the collection type when defined as property in {EntityType} or {ComplexType} and {FunctionImport} return. It does not handle in the {FunctionImport} as input Parameter. Since Function Import supports in-lining of the parameter values during the execution on a GET based call, this becomes an issue. I believe, we will have same issue in V4, but in V4 I think I modeled as "Action" in those cases (Action is always POST based). I will double check that. IMO, it may be easier to avoid adding this "arrayiterate" or any functions with collection type as parameter in OData service generation side, than consuming side, as I do not think any other service will expose in similar situation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)