I'm a beginner at apex, and I've written this for a custom object called "Account". It works just fine for standard leads and accounts - just not the custom account object. I'm getting the error at the beginning of the third Account__c:

Invalid identifier: Account__c

trigger SetAccountField on Account__c (before insert, before update) {
    for (Account__c Account__c : Trigger.new) {
        Account__c.Scoring__c = '0017000000TEs0O';
    }
 }

Any help would be much appreciated. 

I'm posting this in the hopes of helping "the next guy" that hits this.  

Our ant-based deployments, which had been going flawlessly for months, suddenly started failing, with lots of UNABLE_TO_LOCK_ROW errors in the logs from our various Apex test methods.  The same exact test methods passed when executed from "Run All Tests" in the UI.  We tried deploying with Eclipse and Change Sets, but got the same UNABLE_TO_LOCK_ROW errors.

The lines of code that were failing were all record inserts for certain objects.  We realized that if we removed those objects from our package.xml, we could complete the deployment without the errors.  However, we are making lots of object-level changes (new fields, etc), so this was a bad long-term solution.

After much troubleshooting, SFDC Tech Support finally found the root cause.  It turns out that if you modify the format of an auto-number field - say, change the name from "C-{0000}" to "CDM-{0000}" - subsequent deployment of that object will fail if any test methods insert records of that object.

Ouch.  Ugly, bad bug.  But once we knew the cause, we matched up all auto-number field formats in our source & destination orgs, and then re-ran the full ant script (with all objects) again, and the deployment was successful.

Hopefully SFDC will fix this odd bug quickly.  But in the meantime, if you get UNABLE_TO_LOCK_ROW" errors during deployment, check your auto-number field formats!

public static void authenticateSelfServiceUser(String userName, String pwd) {
  try {
    SoapBindingStub binding = (SoapBindingStub) new SforceServiceLocator().getSoap();
    String sforceURI = new SforceServiceLocator().getServiceName().getNamespaceURI();
    String orgId = "12345abc";  // put your SFDC OrgId here
    LoginScopeHeader loginScopeHeader = new LoginScopeHeader();
    loginScopeHeader.setOrganizationId(orgId);
    binding.setHeader(sforceURI, "LoginScopeHeader", loginScopeHeader);
    LoginResult lr = binding.login(userName, pwd);
    System.out.println("User " + userName + " authenticated - session id is " + lr.getSessionId() + ", userid = " + lr.getUserId());
  } catch (Throwable e) {
    System.out.println("Error while authenticating SSU " + userName + ": " + e);
  }
}

Message Edited by GlennAtAppirio on 03-12-2007 02:29 AM

Message Edited by GlennAtAppirio on 02-18-2007 01:05 PM

Message Edited by GlennAtAppirio on 02-18-2007 01:05 PM

I'm posting this in the hopes of helping "the next guy" that hits this.  

Our ant-based deployments, which had been going flawlessly for months, suddenly started failing, with lots of UNABLE_TO_LOCK_ROW errors in the logs from our various Apex test methods.  The same exact test methods passed when executed from "Run All Tests" in the UI.  We tried deploying with Eclipse and Change Sets, but got the same UNABLE_TO_LOCK_ROW errors.

The lines of code that were failing were all record inserts for certain objects.  We realized that if we removed those objects from our package.xml, we could complete the deployment without the errors.  However, we are making lots of object-level changes (new fields, etc), so this was a bad long-term solution.

After much troubleshooting, SFDC Tech Support finally found the root cause.  It turns out that if you modify the format of an auto-number field - say, change the name from "C-{0000}" to "CDM-{0000}" - subsequent deployment of that object will fail if any test methods insert records of that object.

Ouch.  Ugly, bad bug.  But once we knew the cause, we matched up all auto-number field formats in our source & destination orgs, and then re-ran the full ant script (with all objects) again, and the deployment was successful.

Hopefully SFDC will fix this odd bug quickly.  But in the meantime, if you get UNABLE_TO_LOCK_ROW" errors during deployment, check your auto-number field formats!

public static void authenticateSelfServiceUser(String userName, String pwd) {
  try {
    SoapBindingStub binding = (SoapBindingStub) new SforceServiceLocator().getSoap();
    String sforceURI = new SforceServiceLocator().getServiceName().getNamespaceURI();
    String orgId = "12345abc";  // put your SFDC OrgId here
    LoginScopeHeader loginScopeHeader = new LoginScopeHeader();
    loginScopeHeader.setOrganizationId(orgId);
    binding.setHeader(sforceURI, "LoginScopeHeader", loginScopeHeader);
    LoginResult lr = binding.login(userName, pwd);
    System.out.println("User " + userName + " authenticated - session id is " + lr.getSessionId() + ", userid = " + lr.getUserId());
  } catch (Throwable e) {
    System.out.println("Error while authenticating SSU " + userName + ": " + e);
  }
}

Message Edited by GlennAtAppirio on 03-12-2007 02:29 AM

Message Edited by GlennAtAppirio on 02-18-2007 01:05 PM

Message Edited by GlennAtAppirio on 02-18-2007 01:05 PM

I'm a beginner at apex, and I've written this for a custom object called "Account". It works just fine for standard leads and accounts - just not the custom account object. I'm getting the error at the beginning of the third Account__c:

Invalid identifier: Account__c

trigger SetAccountField on Account__c (before insert, before update) {
    for (Account__c Account__c : Trigger.new) {
        Account__c.Scoring__c = '0017000000TEs0O';
    }
 }

Any help would be much appreciated. 

Hey guys... I'm confused. I'm attempting to deploy from my sandbox to production and am running in to inconsistent errors with the process...

When I "run all tests" in Salesforce web - everything works fine. I get coverage for everything over 75%, and no failures.

When I go into eclipse and sync all my classes, obj, etc... and then r-click>force.com>run tests - everything works as well...

However, when I attempt to validate my deployment, I get a these terrible errors:

Run Failures: ImacControllerTest.testNewIMAC System.DmlException: Insert failed. First exception on row 0; first error: UNABLE_TO_LOCK_ROW, unable to obtain exclusive access to this record: [] InstallTicketControllerTest.testInsTkt System.DmlException: Insert failed. First exception on row 0; first error: UNABLE_TO_LOCK_ROW, unable to obtain exclusive access to this record: [] LocationPrepOrderControllerTest.testLocPrp System.DmlException: Insert failed. First exception on row 0; first error: UNABLE_TO_LOCK_ROW, unable to obtain exclusive access to this record: [] RequirementControllerTest.testRqm System.DmlException: Insert failed. First exception on row 0; first error: UNABLE_TO_LOCK_ROW, unable to obtain exclusive access to this record: [] ShipmentControllerTest.testShp System.DmlException: Insert failed. First exception on row 0; first error: UNABLE_TO_LOCK_ROW, unable to obtain exclusive access to this record: [] TerminalPrepOrderControllerTest.testTrmPrp System.DmlException: Insert failed. First exception on row 0; first error: UNABLE_TO_LOCK_ROW, unable to obtain exclusive access to this record: [] triggerTestAxnUpdateAfter.testAxnUpdateInsert System.DmlException: Insert failed. First exception on row 0; first error: UNABLE_TO_LOCK_ROW, unable to obtain exclusive access to this record: [] triggerTestAxnUpdateBefore.testAxnUpdate System.DmlException: Insert failed. First exception on row 0; first error: UNABLE_TO_LOCK_ROW, unable to obtain exclusive access to this record: [] triggerTestInsTktUpdate.testInsTktInsert System.DmlException: Insert failed. First exception on row 0; first error: UNABLE_TO_LOCK_ROW, unable to obtain exclusive access to this record: [] triggerTestLocPrpUpdate.testLocPrpUpdateInsert System.DmlException: Insert failed. First exception on row 0; first error: UNABLE_TO_LOCK_ROW, unable to obtain exclusive access to this record: [] triggerTestShpUpdateAfter.testShpUpdate System.DmlException: Insert failed. First exception on row 0; first error: UNABLE_TO_LOCK_ROW, unable to obtain exclusive access to this record: [] triggerTestTrmPrpUpdate.testTrmPrpUpdate System.DmlException: Insert failed. First exception on row 0; first error: UNABLE_TO_LOCK_ROW, unable to obtain exclusive access to this record: [] axnUpdate Test coverage of selected Apex Trigger is 0%, at least 1% test coverage is required shpUpdate Test coverage of selected Apex Trigger is 0%, at least 1% test coverage is required TrmInAxnUpdate Test coverage of selected Apex Trigger is 0%, at least 1% test coverage is required shpUpdateBefore Test coverage of selected Apex Trigger is 0%, at least 1% test coverage is required LocPrpUpdate Test coverage of selected Apex Trigger is 0%, at least 1% test coverage is required axnUpdateAfter Test coverage of selected Apex Trigger is 0%, at least 1% test coverage is required axnUpdateBefore Test coverage of selected Apex Trigger is 0%, at least 1% test coverage is required trmPrpUpdate Test coverage of selected Apex Trigger is 0%, at least 1% test coverage is required installTicketUpdate Test coverage of selected Apex Trigger is 0%, at least 1% test coverage is required shpUpdateAfter Test coverage of selected Apex Trigger is 0%, at least 1% test coverage is required Average test coverage across all Apex Classes and Triggers is 25%, at least 75% test coverage is required

 All of this is already successfull! What gives?

Why does it not work in deployment when it works in the sandbox?

UNABLE_TO_LOCK_ROW, unable to obtain exclusive access to this record:

I am getting the above error message when I am trying to load data through the data loader but in case of UI  I am not having the issue.

I have a trigger on after insert of lead which is trying to update records leads and on that line this error is occuring.

Hey,

We are seeing some strange behaviour with a VF controller we're trying to deploy from a Sandbox org to production.  In our org we have a parent-child relationship (lookup) between two objects.  A method in the controller class creates a record of the parent object, and then creates a child object record, linking it to the new parent record (newChildRec.Parent__c = parentRec.Id ).  This is all in one method, so presumably it's all taking place in a single transaction.

So this works fine in the sandbox, and the covering testMethod works fine too - both parent and child records are created no problem.

But when we try to deploy to the production org, the testMethod fails, saying (roughly) "Unable to obtain exclusive access to the record" (UNABLE_TO_LOCK_ROW) when trying to create the CHILD record.  Why would this be?  I do understand that when you create a child object record, the system locks the parent record.  But how come this would work on the sandbox but not when we try to deploy to production?  Wouldn't the fact that this is within the same transaction cause this failure to NOT happen?  Could it have to do with API versions, perhaps?  The controller in question is 15.0, and it is being deployed using Eclipse with force.com plugin version 15.0.    The sandbox is on Summer '09 whereas the prod org is of course still on Spring '09, in case that makes a difference.

Can someone advise, by any chance?  

Thanks!

Hi,

I've run into a very annoying problem. I have a simple visualforce page that displayes an organizations address pulling from the organization fields, like so:

<apex:outputText value="{!SUBSTITUTE($Organization.Street, '\n', '<br />')}" escape="false" /><br /> <apex:outputText value="{!$Organization.City}" />, <apex:outputText value="{!$Organization.State}" />&nbsp;<apex:outputText value="{!$Organization.Country}" />&nbsp;&nbsp;&nbsp;<apex:outputText value="{!$Organization.PostalCode}" /> <br />

As you can see I'm tyring to replace the new line character with html break tags. Unfortunately it doesn't seem to be picking up the newline character. I really don't want to write custom controller just to generate a string with proper line breaks (this is all the controller would do for this page, I have no need for anything else). Is there a different character for line breaks that I'm missing? 

In testmethod I inserted a account with Name field.Its showing the following message

System.DmlException: Insert failed. First exception on row 0; first error: DUPLICATE_VALUE, duplicate value found: <unknown> duplicates value on record with id: <unknown>

But I am able to create Account record through tab.

My email template (below) works fine when using the "preview" function to populate the Recipient (WhoID) and RelatedTo (WhatID)  - but when a workflow rule triggers the emai lto be sent, it comes back blank as if it's not resolving the who or what correctly. .

<messaging:emailTemplate recipientType="Contact"
    relatedToType="Account"
    subject="Your website Access"
    replyTo="anaddress@us.com" >

    <messaging:htmlEmailBody >        
    <html>
        <body>
        <p>Hello {!recipient.name}--</p>
        <p>Here is a list of the website access you users currently have for account {!relatedTo.name}:</p>
    <apex:datatable cellpadding="5" var="cts" value="{!relatedTo.Contacts}">
        <apex:column value="{!cts.Name}" headerValue="Name"/>
        <apex:column value="{!cts.Seat_Holder__c}" headerValue="Website Program Access"/>
        <apex:column value="{!cts.Email}" headerValue="Email" />
        <apex:column value="{!cts.Phone}" headerValue="Phone" />
    </apex:datatable>
        </body>
    </html>
    </messaging:htmlEmailBody> 
</messaging:emailTemplate>

I created a simple workflow rule that's called whenever a contact is edited. The workflow rule uses an email alert. The email Alert uses this template. I've checked to make sure the email template is for Contact objects, and that the Recipient is specified as Email Field: Email.

I must be missing something obvious..... any ideas?

Message Edited by icemft1976 on 10-24-2008 09:28 AM