My Account | Internet Creations
Welcome, Guest.
UNABLE_TO_LOCK_ROW, unable to obtain exclusive access to this record
Occurrences of this issue became more common starting on 8/13/2013 when Salesforce's inbound email infrastructure was upgraded increasing the concurrency of emails passed along to the Force.com platform. The likelihood of encountering this error increases with the concurrency of emails received and automation that runs for each email received. Please see the details below for additional information.
Article #1993 • Troubleshooting • Last Updated: 
INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY, insufficient access rights on cross-reference id
Users may receive an error message that includes "INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY, insufficient access rights on cross-reference id" if they do not have both Read and Write access to a given case.
Article #1172 • Troubleshooting • Last Updated: 
Case Owner is not receiving email notifications when a new comment is added to a case
The Case Owner is not receiving email notifications when a new comment is added to a case.
Article #1175 • Troubleshooting • Last Updated: 
Critical Update: Survey recipients unable to click rating links for surveys received in Gmail
In early December 2018, Internet Creations noticed an issue with CSat (1-5 star rating) and Thumbs Up/Down survey types received and viewed in Gmail, which prevented survey recipients from clicking on a survey score to take the survey. We believe this was related to a recent update to Gmail and updated Simple Survey (2.67 and later) to create new email templates properly. However, existing email templates for CSat and Thumbs Up/Down survey types need correction.
Article #4097 • Troubleshooting • Last Updated: 
Update failed ... INSUFFICIENT_ACCESS_OR_READONLY, insufficient access rights on object id:....
Users without System Administrator permissions receive an insufficient access rights error when they click the Take Ownership button.
Article #1458 • Troubleshooting • Last Updated: 
CANNOT_EXECUTE_FLOW_TRIGGER - The record couldn’t be saved because it failed to trigger a flow. A flow trigger failed to execute the flow with version ID 301XXXXXXXXXXXX
You are performing an operation with an Internet Creations application and experience an error similar to the following: CANNOT_EXECUTE_FLOW_TRIGGER - The record couldn’t be saved because it failed to trigger a flow. A flow trigger failed to execute the flow with version ID 301XXXXXXXXXXXX
Article #3871 • Troubleshooting • Last Updated: 
Case not created: System.QueryException: List has no rows for assignment to SObject
You are processing emails via Email to Case Premium and receive an email with the following error message: An error occurred while trying to deliver the attached email. You may wish to report the following information to the owner of e2cpremium@xxxxxxxxxxxxxx.apex.salesforce.com. The apex class E2CP.ProcessMessage failed due to: System.QueryException: List has no rows for assignment to SObject
Article #2006 • Troubleshooting • Last Updated: 
Obsolete Report: This report can no longer be edited or run
You are using an Internet Creations application and encounter the following error when attempting to access one of the packaged reports: Obsolete Report This report can no longer be edited or run. Your administrator has disabled all reports for the custom object, or its relationships have changed.
Article #4035 • Troubleshooting • Last Updated: 
Attachments being replaced by Files for Lightning Experience users starting in Winter 18 release
Starting in the Winter 18 Salesforce release, Salesforce plans to deprecate the use of Attachments within the Lightning Experience, and direct users towards utilizing the more enhanced Files object. While this change specifically affects users of the Lightning Experience, Salesforce is encouraging all customers to adopt Files. In preparation for this movement, Internet Creations has updated its applications to support the Files object. For additional information on the changes made to Internet Creations' applications, please review the following.
Article #3921 • FAQ & How To • Last Updated: 
Non-selective query against large object type (more than 200000 rows)
You're organization has Case Merge Premium installed and experience the following error when attempting to update cases from a Visualforce page in the Service Cloud Console. An error occurred while querying for cases. Non-selective query against large object type (more than 200000 rows). Consider an indexed filter or contact salesforce.com about custom indexing. Even if a field is indexed a filter might still not be selective when: 1. The filter value includes null (for instance binding with a list that contains null) 2. Data skew exists whereby the number of matching rows is very large (for instance, filtering for a particular foreign key value that occurs many times).
Article #3837 • Troubleshooting • Last Updated: 

Support

Open a Case
  • «
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • »