[SalesForce] Deployment Results – What do the Line and Column refer to

I am trying to deploy an application from a sandbox to production. Validation of the inbound change fails. When I view the reasons for the failure I see there are five headings in the Component Deployment Results table: API Name, Type, Line, Column, Problem.

The line and column headings give me some hope there could be some logs available that will let me decipher the somewhat cryptic Problem statement (this is a dashboard issue) which says:

The values of chartSummary and/or groupingColumn are not compatible
with the autoselectColumnsFromReport mode for Metric

Is there a log that I can look at?
If not, how would I determine which particular element of the dashboard is causing me problems here?

Thanks

Best Answer

OK. The line and column in this particular case (a dashboard) refers to the metadata xml file for the dashboard that can be accessed through the Force.com IDE.

If the error had been for a trigger or some other Apex code, the line and column would obviously refer directly to the line and column of the Apex code.

Related Solutions

[SalesForce] Deploying an Apex Class for a Custom Button – Too Many DML Statements Error

Don't ever do DML or SOQL within an iteration scope. You can directly perform these on a collection object.

List<Case> lstToDelete = new List<Case>(); //COLLECTION
for (Case obj : [select Id from Case]) {
        //any possible business logic

        //collect objects you wish to delete/update/anything
        lstToDelete.add( obj); //COLLECT

        //never do another soql query for related records in an interation either, collect the id's in a collection object, and then query  as SELECT  fields FROM obj WHERE field IN:collection
    }

delete lstToDelete;  //BULK EXECUTE

In all honesty, if this is your testcode, I'm a bit worried about your production code. Topics as bulkifying code and governer limits are essential to know when coding on the force.com platform.

[SalesForce] Failure of a Test Method due to UserInfo.getSessionId value

Looking at the code sample you have provided, it does look like the UserInfo.getSessionId() method is context sensitive, to the point where if its directly in a test method vs a Apex class it behaves differently. I've definitely found that not all Session ID's are equal in the past, Salesforce will generate different variants for the same physical session. I suspect this is what your seeing. Clearly your wanting to follow best practice and test your code, this maybe one where you simply have to settle for coverage alone. Interested to see what Salesforce have to say....

Best Answer

Related Solutions

[SalesForce] Deploying an Apex Class for a Custom Button – Too Many DML Statements Error

[SalesForce] Failure of a Test Method due to UserInfo.getSessionId value

Related Topic