---
schema_version: "1"
id: 38704f69ec662b7f3f0682cacd55e0e2fc1ebc6a6ed48e4b4096ac1b33be6a04
title: Recommended Approach for Identifying Problem Areas
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/comms_recommended_approach_for_identifying_problem_areas.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.comms_recommended_approach_for_identifying_problem_areas.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 3ab0a3ddb2d238b1c612bbcb4be611079112c9433518ce9caff4863382e016c0
description: Salesforce recommends you do a code inspection before testing to identify problems in custom-code. Issues regarding custom-code sensitivity to the data model changes are not always readily apparent and may pass a cursory test.
products:
  - Communications
  - Media
  - Energy and Utilities
release: "264"
---
# Recommended Approach for Identifying Problem Areas

Salesforce recommends you do a code inspection before testing to identify problems in custom-code. Issues regarding custom-code sensitivity to the data model changes are not always readily apparent and may pass a cursory test.

Before You Begin

- Ensure you are familiar with the [GUIDs Performance in Industries CPQ](https://help.salesforce.com/s/articleView?id=ind.comms_guids_performance_in_vlocity_cpq.htm&release=264.0.0&type=5 "The GUID performance feature is an optional performance enhancement. When enabled, the feature eliminates an expensive write operation from many common customer transactions, such as add-to-cart.").
- Have a general understanding of the feature and familiarity with Apex coding on the Salesforce platform.

To perform the code inspection:

1. Search the custom code for keywords ParentItemId and RootItemId.
    
    - Watch for search results that may occur in variable names or within SOQL queries and may include the suffix `‘__c’`, depending on the context. Examine all such results and flag them if they relate to the value stored in either a `ParentItemId__c` field or `RootItemid__c` field.
    - If there are no search results, then conduct thorough testing. However, if no results were found, then it’s likely that no changes are necessary.
2. For search results found in step 1, determine if the result is for a SOQL statement. For references within SOQL statements, look for the following:
    
    - Is the reference to `vlocity_cmt__RootItemId__c` or `vlocity_cmt__ParentItemId__c` fields one of the affected types (Asset, OrderItem, QuoteLineItem or OpportunityLineItem)? If not, you can safely remove it from consideration.
    - Is the check for null or not null only? If so, you can safely remove it from consideration.
    - If the checks above do not remove the search result from consideration, then you must modify the result. See the next section.
3. For hits found in step 1, determine if the hit is within non-SOQL Apex code. For references within non-SOQL Apex code, look for the following:
    
    - Is the reference to the `vlocity_cmt__RootItemId__c` or `vlocity_cmt__ParentItemId__c` field value of one of the affected SObject types (Asset, OrderItem, QuoteLineItem or OpportunityLineItem)? If not, you can safely remove it from consideration.
    - Is the reference only to compare the value for null or not-null? If so, you can safely remove it from consideration.
    - If the checks above don’t remove the search result from consideration, then you must modify the result. See the next section.
4. After inspecting and correcting the custom code, test the code to confirm proper operation.