Hi,
I have a managed package that I'm developing. In the developer org the above expression returns:
- normal result counting more than 61 fields when ran in anonymous execution mode
- sooner 0, now 1 field only when ran from tests as well as from batch job (apex)
Why? I need all the fields to be accessible in batch job or tests.
I found that API restriction might be the limiting factor. But my package has no possibility to set its restrictions:

Hi,
when I develop my managed package in dev org I see the logs normally. But my customer installed my package (release) in his org and has some error during running my package. He gave me admin right to his org. I tried to debug my package in his org. The package contains a batchable job that writes leads to db. When I run the package in his org, new batch job appears successfully in apex jobs table in status "processing". After a while status detail contains a brief message with error and number of failures raises. But there are no logs in debug logs page. I setup new User trace flags of type DEVELOPER_LOG as well as USER_DEBUG. But after running the batch again there are still no logs. I also modified the debug level filters but without success. Why there are no logs? Many thanks

I have a visualforce page with custom controller. In controller constructor I placed System.schedule(). The page showed without error (schedule invocation was without exception), but no job was planned. Probably it relates to "DML currently not allowed" exception which does not occur when using system.schedule() but occurs if i placed insert, update, upsert or delete in VF page constructor.

Hi
I've finished my app for managing leads. I will distribute the app in managed package containing these types of items:
- visualforce pages
- apex classes
- custom objects and fields.
While permissions for accessing VF pages and apex classes can be set directly to user profiles, permissions for accessing custom objects can be set to concrete users only, using permission sets.
Primary I want to make installation of the app easy for admin. So I've set the permissions for accessing VF pages and apex classes to standard user profile and to admin profile and I've created a permission set for accessing custom objects. Shall an automatic installer assign the new permission set to all users with standard user profile and to all admins? What about other user profiles? Or is it normal to give instructions to admin what he should set to allow users to use the app? Or does your app use other practice to set permissions to users? Thank you

Hi
I've finished my app for managing leads. I will distribute the app in managed package containing these types of items:
- visualforce pages
- apex classes
- custom objects and fields.
While permissions for accessing VF pages and apex classes can be set directly to user profiles, permissions for accessing custom objects can be set to concrete users only, using permission sets.
Primary I want to make installation of the app easy for admin. So I've set the permissions for accessing VF pages and apex classes to standard user profile and to admin profile and I've created a permission set for accessing custom objects. Shall an automatic installer assign the new permission set to all users with standard user profile and to all admins? What about other user profiles? Or is it normal to give instructions to admin what he should set to allow users to use the app? Or does your app use other practice to set permissions to users? Thank you