New answers tagged namespace
2
I assume that you are executing Type.forName in your managed package code. In this context many of the Salesforce APIs operate as if a namespace isn't defined, and this allows all your managed package code to reference stuff within itself (objects, fields, classes etc.) without need of the namespace prefix. This is the reason you see what you see.
Local ...
3
If it is intended to be included in the package, you need it to be namespaced - I've noticed that flows include namespace prefixes in API name references when created on namespaced orgs and don't cope well when these prefixes are omitted**. This is fine for both 1GP and 2GP managed package development as long as you develop on scratch orgs with the package ...
Top 50 recent answers are included
