#Trailblazer Community Questions3,342 人正在讨论

Hi, please review the below discussion which has answer to your question. 

https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000E9opBSAR

Moreover, I agree with Jon's and would recommend to either engage with implementation partner/consultant or learn yourself. 

https://trailhead.salesforce.com/content/learn/modules/nonprofit-success-pack-basics

https://trailhead.salesforce.com/content/learn/trails/nonprofit_fundraising

https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000E9opBSAR

 Hii , 

You can approach this using an extended ProductDiscoveryContext and SalesTransactionContext. 

Since the Branch ID is stored on Catalog, add a custom BranchId attribute to the Catalog node in ProductDiscoveryContext and map it to Catalog.BranchId__c.

Then add the same BranchId attribute under SalesTransactionItem and map it through ProductDiscoveryContextMapping. 

Finally, use QuoteEntitiesMapping to map SalesTransactionItem.BranchId to QuoteLineItem.BranchId__c. 

The flow would be:

Catalog.BranchId__c 

→ ProductDiscoveryContext.Catalog.BranchId 

→ SalesTransactionContext.SalesTransactionItem.BranchId 

→ QuoteLineItem.BranchId__c

This allows the pricing procedure to use the branch ID associated with the catalog from which the product was selected.

Make sure you are using extended context definitions, because the standard ProductDiscoveryContext and SalesTransactionContext can't be directly modified. 

 Salesforce's current twin-mapping documentation uses the same general pattern for moving values into Quote Line Items.

Reference links:

https://help.salesforce.com/s/articleView?id=005318021&language=en_US&type=1

https://help.salesforce.com/s/articleView?id=sf.product_catalog_productdiscoverycontext_context_definition.htm&language=en_US&type=5

https://help.salesforce.com/s/articleView?id=product_catalog_extend_productdiscoverycontext_context_definition.htm&language=en_US&type=5

https://help.salesforce.com/s/articleView?id=ind.pricing_use_context_definitions.htm&language=en_US&type=5 

Hi @Aira Gutierrez

The "UTAM not defined" and module import errors in 2026 typically stem from missing compiler generation steps or an incomplete link between your testing environment and the generated code.

1. Resolve "UTAM is not defined"

In 2026, the global utam object is not provided by default in standard Node.js scripts; it must be imported or generated via the compiler.

• Ensure Compilation: Your wdio.config.js and tests depend on JavaScript files that are compiled from .utam.json files. Run the compiler command you added to your package.json:

npm run test:ui:compile

• Manual npx check: If the script fails, try running it directly to see specific error messages:

npx utam -c utam.config.js

• WDIO Global Hooks: Ensure your wdio.config.js properly exports the UtamWdioService. If you are trying to use utam in a test script, you must use the utam object injected by the service. In your test file, you typically don't import a global "utam"; you use the browser object or the injected loader: 
  javascript-

// Instead of calling a global utam 

const loader = browser.utam; // The service adds this to the browser object 

2. Fix "Module not found" for Salesforce Page Objects

The salesforce-pageobjects package contains JSON definitions that must be compiled into JavaScript before they can be imported. 

• Correct Import Paths: In 2026, the standard package structure for salesforce-pageobjects does not always require the /dist/ path in the import string. Try importing from the package root: 
  javascript-

// Use this 

import { DesktopLayoutContainer } from 'salesforce-pageobjects/pageObjects/desktopLayoutContainer'; 

// Instead of 

import { DesktopLayoutContainer } from '/salesforce-pageobjects/dist/navex/...';

• Update Package Version: Ensure you are using a version compatible with the current Salesforce release (Winter '26). Check for updates:

npm install salesforce-pageobjects@latest --save-dev

• Check utam.config.js: Ensure your configuration file explicitly lists salesforce-pageobjects in the injectionConfigs. An empty or missing configuration will prevent the generator from finding the Salesforce definitions. 

3. Verify WebDriverIO Configuration

If you recently upgraded to WebDriverIO v8 or v9 (standard in 2026), ensure your wdio.conf.js is using the newer object-based service definition. 

• Service Configuration: Ensure the UtamWdioService is properly imported and added: 
  javascript-

const { UtamWdioService } = require('wdio-utam-service'); 

exports.config = { 

    // ... 

    services: [ 

        [UtamWdioService, { 

            implicitTimeout: 0, 

            injectionConfigs: ['salesforce-pageobjects/ui-global-components.config.json'] 

        }] 

    ], 

};

Final Troubleshooting Step: If imports still fail, check your node_modules folder manually to confirm the file path salesforce-pageobjects/pageObjects/desktopLayoutContainer.js exists. If only .json files exist there, the package was not compiled correctly.

If you relate the scaffold on matching fields then the filtering will carry over.  I would reinstate the 5x5 scaffold and relate it using a relationship of 1=1 - that way the grid is never filtered by anything from the main data - then perform the “join” for each cell in a calculation instead of the relationship, something like:

SUM(IF [Likelihood] = [Likelihood scaffold]
    AND [Impact] = [Impact Scaffold] Then [Measure] END)

Hello @Priyanka Kote, +1, and in your trailblazer profile page (trailblazer.me) you can also filter your badges view by badges/supebadges/modules, but not per trailmixes. That can be explained because anyone can create a trailmix, and they can be modified after you take it.Eric

I'm glad you're figuring this out. Your data and/or LOD calc needs to be cleaned up as it is not returning a single value per user (see image below). But to fix your user counts you need to change the CNT(User) on the License Matrix sheet to CNTD(User) to count distinct users.

Hello @Caroline Fearey concerning the action, check your API name; it is written " Label the action Translate Survey Input with API name Translate_Survey_Input using any description you’d like". Yours has an extra "Fitness" in it.Eric