+ Start a Discussion
rscottrscott 

Visualforce Email template in a Managed Package

We have several Visualforce email templates defined in our managed package. Some of them reference a component in our managed package to create an attachment. All works well until, after we install the package, we try to modify the template to point to a new component in the installed org (not in the managed pkg). Then we get an error saying that it can't find the component.

 

The installed template still shows the component referenced as <c:compName/>. Both that and changing it to <namespace:compName/> reference the component in the managed package. Changing to <c:newCompName /> where newCompName is outside of the managed package gives us the afore-mentioned error. Seems like a bug to me or at least an oddity in how components are handled in managed email templates. Anyone else come across a similar issue?