Feed

@Izabela Górska

Salesforce out-of-box error messages cannot be translated directly using Translation Workbench. Since the values under error messages are being pulled dynamically - it uses the default org language - English. 

Please refer to the below article - 

Regards 

Sravani

@Genesis Tifa-Tejada

please refer to the below thread -  

@Absa Thiam Vous pouvez utiliser cet identifiant de package et ce lien 

pour installer l'application. 

Package  Id: 04tB00000009UeX 

Thank you

in support they are asking for product and topic what would i choose ? @Keiji Otsubo

If you're using Lightning you can add specific fields to an Update Action and add the Update Action to the Product Record Page Layout using the Related Record feature then add a Visibility Filter to the Update Action based off a product specific attribute. If you add multiple Update Actions each with their own, mutually exclusive Visibility Filter, the user will only see the one specified. It will look pretty hacky on the backend though. https://www.reddit.com/r/salesforce/comments/kqpd0k/opportunity_product_multiline_layouts/?utm_source

Or you can Custom LWC or Flow-Based Component

@Mykhailo Vdovychenko

I did sign up for the developer edition org. The error is occurrying while creating the app in salesforce. 

The previous challenges are only questions.

Hello @Vignesh R

, 

Thanks for the follow-up, and great question! 

Yes, if you're creating Web-to-Lead through metadata and using Apex to submit the lead, the context changes slightly. When you're inserting leads via Apex code (e.g., using DML like insert new Lead(...)), the data bypasses the standard Web-to-Lead HTTP endpoint and goes directly into Salesforce from within the platform. 

Since this Apex code is running inside Salesforce, you're already protected from classic SQL injection — Salesforce doesn’t expose SQL-style query execution the way traditional systems do. Apex DML and SOQL are strongly typed, and the platform sanitizes inputs properly. 

If the data passed into Apex comes from an external source (like a public form, external system, or integration), then:

1. You must validate and sanitize the input before processing it — even if you're using Apex.
2. If you're calling dynamic SOQL inside Apex (e.g., Database.query()), be extra careful. Always bind variables securely instead of string concatenation.

I hope that helps. 

Thanks & Regards 

Amit Kumar

@Shubham Ahire

please refer to the below article - 

Salesforce MIAW doesn’t offer a built‑in idle timeout to launch a chatbot popup but you can do it through different ways. 

Hi @SangHyun Bae, 

You can search for beginner-level mods here:  https://trailhead.salesforce.com/search/learning?keywords=data+cloud&levels=beginner

This trail could be a good starting point: https://trailhead.salesforce.com/content/learn/trails/explore-customer-360-audiences

The next one could be: 

https://trailhead.salesforce.com/users/strailhead/trailmixes/prepare-for-your-data-cloud-consultant-credential

Not forgetting to read everything here: https://help.salesforce.com/s/articleView?id=sf.c360_a_data_cloud.htm&type=5

Great short videos here: https://www.youtube.com/playlist?list=PLgIMQe2PKPSI5DoY3FTYK7fXKVXNeQ4Xe

Hope this helps!