[ https://issues.jboss.org/browse/TEIID-2785?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2785: --------------------------------------- That's the current behavior though. If you recall in the old mmx days functions regardless of their source were globally defined. In this case having them be SYS.JCR implies they are for a specific purpose. And even if they are scoped to a model you can still attempt to invoke them against another source. Again the rationale for this is introducing a single function definition rather than having each model with its own. That an issue with Designer usage. In a dynamic vdb (or even a live designer vdb) the pushdown function metadata gets injected just like the schema scoped metadata, so it's there at runtime. For design time we have a couple of options, the simpliest of which is to add an import option to include the pushdown functions in the schema metadata (although it would be nice if the resolver knew the relationship between the function definitions). Beyond that designer would have to know how to update the function library based upon the translator set in use. -- 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