Documentation like Understanding Execution Governors and Limits says that a managed package has a set of governor limits that are separate from the governor limits applied to the non-packaged source code in an org. This is the behavior we see in developer edition orgs: numbers are reported for the managed package(cve namespace) and non-packaged source code (default namespace) separately and no limits are exceeded and our tests all pass.

But after an upgrade of an org that we setup for a customer starting from a Trialforce snapshot, the counting appears to be combined and reported only under the non-packaged source code (default namespace) so that limits are exceeded and some of our tests fail.

Can anyne offer any insight into this problem? Below are fragments of debug log output that illustrate the problem. (There is mention of the cve managed package in both logs, just not in this fragment for the problem org.)

Thanks,

Keith

From the working (developer edition org):

02:22:24.379|CUMULATIVE_LIMIT_USAGE
02:22:24.379|LIMIT_USAGE_FOR_NS|(default)|
Number of SOQL queries: 0 out of 100
Number of query rows: 0 out of 50000
Number of SOSL queries: 0 out of 20
Number of DML statements: 5 out of 150
Number of DML rows: 5 out of 10000
Number of script statements: 189 out of 200000
Maximum heap size: 0 out of 3000000
Number of callouts: 0 out of 10
Number of Email Invocations: 0 out of 10
Number of fields describes: 0 out of 100
Number of record type describes: 0 out of 100
Number of child relationships describes: 0 out of 100
Number of picklist describes: 0 out of 100
Number of future calls: 0 out of 10

02:22:24.379|LIMIT_USAGE_FOR_NS|cve|
Number of SOQL queries: 6 out of 100
Number of query rows: 6 out of 50000
Number of SOSL queries: 0 out of 20
Number of DML statements: 1 out of 150
Number of DML rows: 1 out of 10000
Number of script statements: 442 out of 200000
Maximum heap size: 0 out of 3000000
Number of callouts: 0 out of 10
Number of Email Invocations: 0 out of 10
Number of fields describes: 0 out of 100
Number of record type describes: 0 out of 100
Number of child relationships describes: 0 out of 100
Number of picklist describes: 0 out of 100
Number of future calls: 0 out of 10

02:22:24.379|TOTAL_EMAIL_RECIPIENTS_QUEUED|0
02:22:24.379|STATIC_VARIABLE_LIST|
BusinessLogicBase:MONTHS:126
PaymentSpecificationPopulatorTest:BASE:4
PaymentSpecificationPopulatorTest:LUMP_SUM:8
PaymentSpecificationPopulatorTest:MONTHLY:7
PaymentSpecificationPopulatorTest:SCALE:4
PaymentSpecificationPopulatorTest:TODAY:4

02:22:24.379|CUMULATIVE_LIMIT_USAGE_END

From the failing (customer org:

01:35:40.307|CUMULATIVE_LIMIT_USAGE
01:35:40.307|LIMIT_USAGE_FOR_NS|(default)|
Number of SOQL queries: 6 out of 100
Number of query rows: 6 out of 50000
Number of SOSL queries: 0 out of 20
Number of DML statements: 6 out of 150
Number of DML rows: 6 out of 10000
Number of script statements: 631 out of 200000
Maximum heap size: 0 out of 3000000
Number of callouts: 0 out of 10
Number of Email Invocations: 0 out of 10
Number of fields describes: 0 out of 100
Number of record type describes: 0 out of 100
Number of child relationships describes: 0 out of 100
Number of picklist describes: 0 out of 100
Number of future calls: 0 out of 10

01:35:40.307|TOTAL_EMAIL_RECIPIENTS_QUEUED|0
01:35:40.307|STATIC_VARIABLE_LIST|
BusinessLogicBase:MONTHS:130
PaymentSpecificationPopulatorTest:BASE:8
PaymentSpecificationPopulatorTest:LUMP_SUM:8
PaymentSpecificationPopulatorTest:MONTHLY:7
PaymentSpecificationPopulatorTest:SCALE:4
PaymentSpecificationPopulatorTest:TODAY:8

01:35:40.307|CUMULATIVE_LIMIT_USAGE_END

Could someone please help?

In my custom app, I added a custom button, and then added it to the default layout of Contact.

After I packaged and installed the app into a new organization. I can see the button installed and deployed  from set up, but, when I open Contact layout, I don't see the custom button.

DO I have to add it into the Contact layout mannually after the package deployed? If so, If I install this app to 10 apps, I have to add the button 10 time?? Thanks in advance.

Hello Experts!

I am not very familiar  to outbound message using workflows 

I need to pass some parameters from a custom object say serial number ,product type and product family from Salesforce  to an end point URL (the end point URL is within our firewall) to get the License activation code,

i know i can accomplish this using outbound message using workflows ,please clarify if i am wrong 

If i can accomplish this using an outbound message, how can i retreive the details from the outbound message response to a custom field? 

In this example i get a license activation code back from the outbound message i want to populate it back to the custom object record from where the outbound message was sent,how do i accomplish this?

IF this is not possible using Workflow outbound message ,should i write a custom webservice Apex class?,if you can point to any examples that would be appreciated!

Please reply incase you have trouble understanding the question

thanks!

HI allll...

             I am trying to write a query in which for the where cluase i would like to check with a lookup field.

How this can be done. Please suggest.

ex: Select Product_name__c from Franchisee__c where Franchisee_name__c=

Here Franchisee_name__c is a lookup field refering to accounts.

Please suggest I am New to this Envi

Thanks in advance

Hi,

I need to use webservice class of one salesforce account into  another salesforce account.

Can any one tell me how to call that class in another salesforce account.?

Documentation like Understanding Execution Governors and Limits says that a managed package has a set of governor limits that are separate from the governor limits applied to the non-packaged source code in an org. This is the behavior we see in developer edition orgs: numbers are reported for the managed package(cve namespace) and non-packaged source code (default namespace) separately and no limits are exceeded and our tests all pass.

But after an upgrade of an org that we setup for a customer starting from a Trialforce snapshot, the counting appears to be combined and reported only under the non-packaged source code (default namespace) so that limits are exceeded and some of our tests fail.

Can anyne offer any insight into this problem? Below are fragments of debug log output that illustrate the problem. (There is mention of the cve managed package in both logs, just not in this fragment for the problem org.)

Thanks,

Keith

From the working (developer edition org):

02:22:24.379|CUMULATIVE_LIMIT_USAGE
02:22:24.379|LIMIT_USAGE_FOR_NS|(default)|
Number of SOQL queries: 0 out of 100
Number of query rows: 0 out of 50000
Number of SOSL queries: 0 out of 20
Number of DML statements: 5 out of 150
Number of DML rows: 5 out of 10000
Number of script statements: 189 out of 200000
Maximum heap size: 0 out of 3000000
Number of callouts: 0 out of 10
Number of Email Invocations: 0 out of 10
Number of fields describes: 0 out of 100
Number of record type describes: 0 out of 100
Number of child relationships describes: 0 out of 100
Number of picklist describes: 0 out of 100
Number of future calls: 0 out of 10

02:22:24.379|LIMIT_USAGE_FOR_NS|cve|
Number of SOQL queries: 6 out of 100
Number of query rows: 6 out of 50000
Number of SOSL queries: 0 out of 20
Number of DML statements: 1 out of 150
Number of DML rows: 1 out of 10000
Number of script statements: 442 out of 200000
Maximum heap size: 0 out of 3000000
Number of callouts: 0 out of 10
Number of Email Invocations: 0 out of 10
Number of fields describes: 0 out of 100
Number of record type describes: 0 out of 100
Number of child relationships describes: 0 out of 100
Number of picklist describes: 0 out of 100
Number of future calls: 0 out of 10

02:22:24.379|TOTAL_EMAIL_RECIPIENTS_QUEUED|0
02:22:24.379|STATIC_VARIABLE_LIST|
BusinessLogicBase:MONTHS:126
PaymentSpecificationPopulatorTest:BASE:4
PaymentSpecificationPopulatorTest:LUMP_SUM:8
PaymentSpecificationPopulatorTest:MONTHLY:7
PaymentSpecificationPopulatorTest:SCALE:4
PaymentSpecificationPopulatorTest:TODAY:4

02:22:24.379|CUMULATIVE_LIMIT_USAGE_END

From the failing (customer org:

01:35:40.307|CUMULATIVE_LIMIT_USAGE
01:35:40.307|LIMIT_USAGE_FOR_NS|(default)|
Number of SOQL queries: 6 out of 100
Number of query rows: 6 out of 50000
Number of SOSL queries: 0 out of 20
Number of DML statements: 6 out of 150
Number of DML rows: 6 out of 10000
Number of script statements: 631 out of 200000
Maximum heap size: 0 out of 3000000
Number of callouts: 0 out of 10
Number of Email Invocations: 0 out of 10
Number of fields describes: 0 out of 100
Number of record type describes: 0 out of 100
Number of child relationships describes: 0 out of 100
Number of picklist describes: 0 out of 100
Number of future calls: 0 out of 10

01:35:40.307|TOTAL_EMAIL_RECIPIENTS_QUEUED|0
01:35:40.307|STATIC_VARIABLE_LIST|
BusinessLogicBase:MONTHS:130
PaymentSpecificationPopulatorTest:BASE:8
PaymentSpecificationPopulatorTest:LUMP_SUM:8
PaymentSpecificationPopulatorTest:MONTHLY:7
PaymentSpecificationPopulatorTest:SCALE:4
PaymentSpecificationPopulatorTest:TODAY:8

01:35:40.307|CUMULATIVE_LIMIT_USAGE_END

I want to use Fieldsets in a managed package. The documentation states:

If a Visualforce page is added to a managed package and distributed, subscribers can edit the properNames field set. The logic for generating the Visualforce page remains the same, while the presentation differs based on each subscriber's implementation. To reference a field set from a managed package, you must prepend the field set with the organization's namespace

But if the custom object is in the same managed package as the fieldset does the namespace still need to be prepended?

Hi,

I'm about to release v1 of a managed package. Once this package is in the wild, I'll need to make bug fixes and do maintenance releases. At the same time, I will be building v2 in a separate code base / branch. 

I initially thought package extensions might be a way to accomplish this, but there are some issues:

• If customer wants v2, they must install v1 first. This gets worse as new major releases are completed.
• The DE org(s) for major releases after v1 would each create a new namespace prefix.