#Salesforce Admin363 debatiendo

Hi David,

The Salesforce Data Mask app's standard filter UI evaluates criteria as literal static dates (e.g., > 2023-04-17) and does not natively support dynamic relative date literals like N_MONTHS_AGO:18 or IS OUTSIDE operators directly in the dropdown configuration.

To achieve a moving or relative date filter (such as records where GDPR_Latest_Date__c < N_MONTHS_AGO:18), the standard workaround is to use a Formula Field on the object. 

1.Create a Formula Field on the Object:Formula Creation. 

Create a new Formula field (with a checkbox return type) on your Lead object. Use the TODAY() function combined with date math to flag records older than 18 months. 

2.Add the Date Comparison Logic:Formula Logic. 

Use a formula like: GDPR_Latest_Date__c < ADDMONTHS(TODAY(), -18) 

3.Filter by the Checkbox in Data Mask:Data Mask Configuration. 

Return to the Data Mask configuration UI, replace your date field condition, and instead filter by your new formula checkbox field equals True. Because this is evaluated dynamically based on TODAY(), it will always respect your moving 18-month window.

Hi Guilherme, Custom Keys aren’t required for basic push notifications. They’re used when the app needs to receive additional key-value data in the push payload, for example to support tracking, deep linking, or custom app behavior. The mobile app code needs to be implemented to handle those keys. 

For the basic MC Next setup, you’ll need to configure the mobile app and the appropriate iOS/Android push service credentials, then configure the SDK in the app to receive push notifications. 

So if the implementation doesn’t require any custom data or app-specific behavior, Custom Keys generally aren’t necessary. If you share what the other company is asking you to configure as the Custom Keys, it may be easier to determine whether they’re actually needed. 

It's been a long time since I've done that Challenge.   

I think you're supposed to select the Account record for "Edge Communications" and then click the Gear icon and then Edit Page  

Ciao Raffaele,

Questo errore si verifica perché i nomi utente (Username) in Salesforce devono essere univoci a livello globale in tutte le organizzazioni Salesforce esistenti (produzione, sandbox, trial e altri playground), e l'indirizzo _testuser_@example.com è già stato utilizzato da qualcun altro in passato su Salesforce.

Per risolvere il problema:

• Modifica il nome utente aggiungendo del testo univoco all'inizio o prima del dominio (ad esempio, _testuser_tuonome@example.com o testuser_accenture_2026@example.com), pur mantenendo la struttura di un'email valida.
• Assicurati che l'indirizzo email di contatto (Email) possa anche essere diverso dal nome utente se necessario, poiché il campo Username deve solo rispettare il formato email ed essere globale.
• Salva nuovamente l'utente e procedi con la verifica del modulo Trailhead.

Hi Sana,

This error ("Our trailbots are having a problem accessing your hands-on org") typically happens when the automated checker cannot connect to your playground because the session has expired, the environment is temporarily unresponsive, or the system needs a fresh connection handshake.

To resolve this:

• Click the Launch button to open your playground, make sure you are actively logged in, and then return to click Check Challenge again.
• Verify that you created the permission set with the exact label (View Account Fields) and API name (View_Account_Fields), and ensure the View All Fields object permission is enabled specifically on the Accounts object.
• If the connection error persists, create a brand-new Trailhead Playground from the dropdown menu, assign the permission set there, and run the check again

We are migrating to SOQL, meaning we will use the same Google Connector to query the data directly instead of exporting reports. Because this SOQL export operates via the API rather than the UI, it successfully bypasses the mentioned limitation.

However, please keep the following SOQL specifics in mind:

• Row Limits: Extracts are capped at 10,000 rows.
• Headers: Google Sheets will display field API names instead of standard field labels.
• Formatting: The column order in the sheet may not match the order of fields in your query.

Despite these quirks, this remains a highly effective workaround.

Hi Tami,

Don't worry, the functionality is still there, but a couple of UI layout changes and common list view quirks can make the template button seem to disappear.

Here are the most common reasons this happens and how to get your template back:

1. Check the Bottom-Left / Bottom Toolbar of the Composer

In the Send List Email pop-up window:

• Look at the bottom toolbar (below the main body text box, near the send/attachment buttons) rather than the top formatting bar.

• Look for an icon that looks like a sheet of paper with a plus sign / folded corner (the tooltip will read "Insert, create, or update template").

• Click that icon and select Insert a template... to choose your template. You will get that familiar prompt asking if you want to overwrite existing content.

2. Make Sure the Composer Isn't Minimized or Cut Off

If your browser zoom is high or the modal is docked:

• Sometimes the action toolbar at the bottom gets pushed below the visible window frame.

• Try maximizing the email composer pop-up or zooming out (Ctrl - / Cmd -) to reveal the bottom icon row.

3. Check Which List View You Are In

• If you are in the default "Recently Viewed" list view, mass emailing behavior and button visibility can be restricted or behave inconsistently.

• Make sure you switch to a custom list view (e.g., All Contacts or your specific filtered list) before selecting records and clicking Send List Email.

4. Template "Related Entity Type" Mismatch

If you click the template icon but your template is not showing in the list:

• When creating Lightning Email Templates, check the "Related Entity Type" field on the template.

• If it was created specifically for a different object (like Lead or Account instead of Contact), or if the folder where the template is stored isn’t shared with your user/public group, it won't appear as an option to insert when sending from Contacts.

Hope this gets your emails out the door! If this helps resolve it, please consider marking it as Best Answer so others running into the same issue can find it quickly.