Could any one highlight on effects and implications of using standard objects wherever required in a Managed package. It could be as simple as 'test class failure' resulting into installation failure due to an already existing validation rule on a Standard object in the org in which a customer is trying to install a Managed package. It would also be great to know if there is any specific strategy one can follow in the design or the code-base so that such situations would be avoided or any other consideration that can be helpful.

We are designing an Appexchange ISVforce App and this is a very crucial decision that we have to make while designing, whether to consider some of the standard Objects like Products and Price Books or to custom build them for our app. Custom building such Objects would definitely be a challenge as there might be a lot of data duplication if some of our potential customers are already using the Standard functionalities related to these standard objects and eventually we have to think on some Integration strategy as well to have a sync between data for the standard and custom objects on a case to case basis which would be an overhead for sure.

Really looking forward for some detailed insights into it as I am unable to get any info on this in any of the docs or anywhere in the community.

Apologies if I am unable to maintain the brevity in my query.

I have a very simple query that ls looking querying Accounts to find one particular Account, then assign that Account's ID to the Account field on my Contact record.  I continue to get the "System.QueryException: List has no rows for assignment to SObject" error, but when I run the query using Query Editor, it returns the appropriate record.  Can anyone please tell me what I'm doing wrong?
 

trigger assignAccounttoContact on Contact (before insert, before update) {
    
    Account a = [
        SELECT ID, Name 
        FROM Account 
        WHERE Name = 'TestAccount'
    ];
    
    for(Contact c: Trigger.new){
        
        c.AccountID = a.ID;
    }
    
}

 

I'm in the process of integrating jqGrid into a VisualForce page, ideally using a JSON data source provided by Apex RESTful services.  At this point it keeps telling me that the session is invalid, so I'm trying to figure out what to do.

 

My Apex RESTful service class looks like:

 

@RestResource(urlMapping='/jqGrid/*')
global with sharing class JqGridController
{
    @HttpGet
    global static JqGridResponse doGet()
    {
        ...
    }
}

 

and the referencing VisualForce page contains the following:

 

jQuery('#{!gridId}').jqGrid(
{
    datatype: 'json',
    url: "{!URLFOR('/services/apexrest/jqGrid')}",
    loadBeforeSend: function(jqXHR)
    {
        jqXHR.setRequestHeader("Authorization", "Bearer {!URLENCODE($Api.Session_Id)}");
    },
    ...
});
...

Does anyone know why this isn't working and, more importantly, what I need to do to get it working?

 

Thanks!