Apex Code Development You need to sign in to do that
Don't have an account?
mshelman Is anybody out there?
It's my belief that all of these recent threads on this board probably refer to the same problem that seems to have surfaced within the past week or so having to do with dynamic apex and packaging and perhaps the "API access restrictions" on packages. I'm experiencing all the problems described below in a class that references only a custom object that is included in the package. My experience with these problems is that they occur intermittently.
Schema.SObjectType.Contact.fields.getMap() and Managed Package
Schema.SObjectType.Contact.fields.getMap() and Managed Package
Schema.SObjectType.Opportunity.fields.getMap() Returns Empty Map
System.QueryException: object is not accessible in query due to package restrictions
More Dynamic Apex issues
Message Edited by mshelman on 10-15-2008 02:06 AM
Schema.SObjectType.Contact.fields.getMap() and Managed Package
Schema.SObjectType.Contact.fields.getMap() and Managed Package
Schema.SObjectType.Opportunity.fields.getMap() Returns Empty Map
System.QueryException: object is not accessible in query due to package restrictions
More Dynamic Apex issues
Message Edited by mshelman on 10-15-2008 02:06 AM
Namespaced(fRecruit) Dynamic code has access to fRecruit__Canidate__c sobject. But if the subscriber adds a field to the object, Dynamic code cannot operate on this custom field.
2) By default, namespaced code should have complete dynamic access on the namespaced objects/fields - regardless of whether PAC is enabled.