Skip to main content

#Trailhead Challenges1,187 discussing

Hands-on challenges are the “secret sauce” of Trailhead. Before searching for solutions to superbadge challenges, review the Salesforce Certification Program Agreement and Policies. ** NOTE ** : If you were able to get a response that solved your issue, please mark it as the 'Best Answer' to help other Trailblazers. If the issue persists after 48 hours, create a Trailhead Help case at https://help.salesforce.com/s/support for further assistance.
1 answer
  1. Oct 5, 1:22 PM

    Hi @Zeal Caduyac,  

    The Contact object in this org has Street Address marked as a required field (either standard field requirement, validation rule, or custom configuration), but Salesforce could not find a matching column from your CSV file.

    You can fix this in below ways:

    1. Click OK.
    2. Click Show errors or locate the row for Contact: Street Address in the field mapping screen.
    3. Click Change next to that field.
    4. Map it to the CSV column that contains the contact's street address.
    5. If your CSV doesn't have a street address column, then: 
      • Add a Street Address column to the CSV and populate it, or
      • Review whether the field is being made required by: 
        • validation rule
        • page layout setting
        • custom field configuration
        • before-save flow or trigger
    6. If Street Address is not required, consider updating the field configuration or related validation rules to make it optional, then retry the import.
0/9000

Set Up Product Qualification Rules (https://trailhead.salesforce.com/fr/content/learn/modules/product-qualification-and-disqualification-with-agentforce-revenue-management/set-up-product-qualification-rules)

Following the trail steps to set up the Qualification Procedure, I need to reference a custom field (BillingState__c) on the Account node inside my "Evaluate Qualification" element's Billing_State input parameter. 

 

  • I created a custom Context Definition (ProductQualificationContext) extending the standard ProductDiscoveryContext.
  • On the Map Data tab → Account node's Object Mapping, I mapped BillingState__c → BillingState, and clicked Save and Publish.
  • However, on the Structure tab, BillingState__c still shows with no anchor icon, unlike the other 4 native attributes (id, AccountId, ContactId, CurrencyIsoCode) which are all anchored.
  • As a result, BillingState__c never appears as a selectable resource in the Qualification Procedure builder's Resource Manager, so I can't complete the Billing_State input parameter on the Evaluate Qualification element.

 

I also confirmed:

  • The Billing State Qualification Lookup Table itself is Active, refreshed, and has valid data (3 rows with Billing_State__c, IsQualified, ProductId).
  • The Qualification Procedure's Context Definition field only accepts ProductDiscoveryContext (per the lab note), not my custom extension directly.

 

Question:

 Is there an additional step needed to "anchor" a custom-mapped field on an inherited standard context node, or is this a known limitation when extending standard Context Definitions? 

 

Any guidance appreciated — happy to share screenshots of each step if useful. 

 

#Trailhead Challenges

0/9000