• Robin De Bondt
  • NEWBIE
  • 0 Points
  • Member since 2015
  • 10x certified consultant/developer
  • absi


  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 1
    Likes Given
  • 0
    Questions
  • 1
    Replies
Hello

I have written a simple trigger to convert lead to contact.
It has an error I can't understand:
Error
Reason: Could not process your referral.
common.exception.SfdcSqlException: ORA-20025:
ORA-06512: at "SNEEZY.CACCESS", line 2399
ORA-06512: at "SNEEZY.CACCESS", line 585
ORA-06512: at "SNEEZY.CACCESS", line 656
ORA-06512: at "SNEEZY.CTASK", line 552
ORA-06512: at line 1


{call cTask.insert_tasks(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}

{call cTask.insert_tasks(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}

I have found several links about this error:
https://developer.salesforce.com/forums/?id=906F0000000An21IAC

https://success.salesforce.com/issues_view?id=a1p30000000Sup5AAC

The scond link suggests the following:
Repro
Conditions that cause this: 
- database.leadConvert is executed for the lead inside Lead after insert trigger. 
- There is workflow associated with the Lead to create a new task as an immediate action.
Workaround
Set the workflows's "new task" task as time-dependent instead of immediate. The problem only manifest itself if the task is created at the same time the lead is converted.

Has anyone done this before? Set the workflows's "new task" task as time-dependent...?

Thank you
A number of custom picklists which are based on global value sets have been uploaded to an unmanaged package. The unmanaged package upload fails due to the following error: "This object only supports strict picklists." After navigating to the fields, I discovered that the Restrict picklist values to the values defined in the value set checkbox is grayed out, and therefore I'm unable to update/check the box to make picklist restricted. Global/Picklist Values Sets are strict by default, so there appears to be a conflict with the metadata during attempted upload. Seems like a bug to me...

Does anyone have information on this, or a suggested work-around?? Thanks!!