We need to execute a query on behalf of another user.
Ex: User creates an Action Item record (think of it as question to the field force), the question needs to apply only to Accounts accessible to the user. To do so we have an intermediate object, ActionItemAccount.
ActionItemAccount is refreshed nightly to reflect any changes in the users's access overtime.
The batch Deletes existing records, and recreates records based on the currently accessible to the user Accounts.
To do so the batch needs to query the Account object (Run As) the Owner of the Action Item.
Hope the above makes sense, can you please share your thoughts on the desired approach,
We need to execute a query on behalf of another user.
Ex: User creates an Action Item record (think of it as question to the field force), the question needs to apply only to Accounts accessible to the user. To do so we have an intermediate object, ActionItemAccount.
ActionItemAccount is refreshed nightly to reflect any changes in the users's access overtime.
The batch Deletes existing records, and recreates records based on the currently accessible to the user Accounts.
To do so the batch needs to query the Account object (Run As) the Owner of the Action Item.
Hope the above makes sense, can you please share your thoughts on the desired approach,
We are planning to use base and extension packages in our AppExchange product and would like to know how base and extension packages behave during update and upgrades. More specifically:
1. What is the behaviour of updates to a base package? If there is an extension package installed, will any components (e.g. page layout, field label) in the extension package be overwritten with those in the base when the base is updated or upgraded?
2. Do extension packages follow the same guidelines as for base managed packages (as outlined in Appendix B of Developing Packages for Distribution)? Are the same items updatable/upgradable?
3. Can we package updates to extension and base packages together?
The fact that a given managed package can be owned and developed in one and only one DE has many side effects that make it different from typical custom software development. Can you help me with this one?
(1) A managed package is developed and released from a DE instance with a namespace. There are many classes and custom objects, so the namespace is highly embedded in code and meta-data.
(2) After release 1.0 of the managed package is uploaded to the AppExchange, work begins on release 2.0 in the same DE instance. Assume that Eclipse IDE and SVN are used to archive and source manage all code versions.
(3) Many changes are made while 2.0 development is in progress. New fields are added to custom objects, for example. It is not complete, however, when...
(4) Suddenly, an emergency patch release (1.1) is needed, for the 1.0 release has a major bug that is just discovered that affects several Apex classes and custom objects.
(5) Here's the question: The DE instance is loaded with in-progress release 2.0 work. The SVN repository has a snapshot of the code as of release 1.0, but it cannot overwrite the ongoing 2.0 work in progress in the DE instance, right? How can you produce a 1.1 patch without seriously screwing up your DE instance that contains release 2.0 work in progress?!
In the Profile page there is a "Standard Object Permissions" section. This section enables the option of having "View All" or "Modify All" permission to a class of objects (eg: Accounts, or Opportunities). How can I programmatically read whether these values are set? In which database tables are these configuration options stored?
