#Automation34 discutindo

Hi SidParnam,

If you're maintaining a long list of company names in a formula, I wouldn't recommend moving the same large IF/OR logic into Apex. Apex doesn't have the formula field's 5,000-character limit, but hard-coding a large company list makes the solution difficult to maintain.

A better approach would be to store the company values as configuration:

• Create a Custom Metadata Type with the company name and the checkbox value.
• Use a before-save Record-Triggered Flow to look up the company and set the checkbox.
• If you need more complex processing or a very large dataset, Apex can also query the configuration and update the record.

This way, adding or removing a company doesn't require changing and redeploying your formula/Apex code. 

If you share approximately how many company values you have and whether the checkbox needs to update immediately when the Company field changes, we can suggest the simplest implementation. 

Hi Robert,

For the ICU Locale Format migration, I would recommend treating it as a testing/impact-assessment exercise rather than just changing the setting.

A few things to check:

• Review the Salesforce ICU Locale Format Migration documentation and identify which locales your org uses.
• Test date, time, number, currency, and address formatting for your supported locales.
• Pay particular attention to Apex, Visualforce, LWC/Aura, integrations, reports, and any custom JavaScript that parses or formats dates/numbers.
• Test automation such as Flows, validation rules, formulas, and email templates where locale-dependent values are involved.
• Test integrations carefully if they exchange formatted dates/numbers with external systems.
• Enable ICU in a sandbox first, run regression testing, and compare the results with the existing format.
• Document any impacted customizations and update them before enabling it in production.

The main risk is usually custom code or integrations that assume a specific date/number format rather than Salesforce's locale-aware formatting.

If you share which Salesforce products/customizations you're using, I can suggest a more specific migration checklist. 

Hi Rashi,

Salesforce doesn't natively write files directly to an organization's shared network drive. A common approach is to use an external integration or middleware between Salesforce and the network location.

For example:

1. Schedule a Salesforce report/export or query the required records through the Salesforce API.
2. Have an integration service retrieve the data on a schedule.
3. The integration writes the generated CSV/file to the shared network drive for the bot to process.

Depending on your environment, this could be implemented using MuleSoft, an ETL/integration platform, or a small scheduled service that uses the Salesforce API. 

If the requirement is specifically for a scheduled Salesforce report export, rather than querying the data directly, the available options are different. Sharing the required file format, frequency, and whether middleware is already available would help determine the best approach. 

Hi Branden, 

Changing the minimum password length in Salesforce Password Policies does not immediately change or invalidate passwords that existing users have already set. 

The new policy applies when users set or change their passwords going forward. Existing passwords can remain as they are until the user changes/resets the password. 

If you want to force existing users to comply with the new password policy, you would need to have them reset their passwords (or use an appropriate administrative process). 

Hi Michael,

The issue is that /img/samples/stars_100.gif, stars_200.gif, and stars_300.gif are Salesforce's sample images, and those images are based on the standard 5-star rating scale. Changing the picklist values doesn't change the number of stars in the image itself. 

If you want a true 3-star display, you'll need to use your own 3-star image files as a Static Resource and reference those in the formula.

For example:

IMAGE(
    CASE(
        Grade__c,
        "1", "/resource/YourStarResource/star_1.png",
        "2", "/resource/YourStarResource/star_2.png",
        "3", "/resource/YourStarResource/star_3.png",
        "/resource/YourStarResource/star_0.png"
    ),
    "Rating"
)

Create the appropriate 0-, 1-, 2-, and 3-star images and upload them as a Static Resource. That way the displayed scale is actually limited to 3 stars. 

Hi Bob,

If you're referring to Enhanced Notes, you can automate this using the ContentNote and ContentDocumentLink objects. 

One approach is to use a record-triggered Flow on ContentDocumentLink to detect when a note is linked to the record, then send an email notification to the appropriate users. 

Keep in mind that ContentDocumentLink is used for linking the Note to records, so you'll need to determine the linked record and recipients before sending the notification. 

If you share which record you want to notify users about (Account, Contact, Opportunity, etc.) and whether you're using Enhanced Notes, I can suggest the exact Flow configuration. 

Hi Brenna,

The INVALID_CROSS_REFERENCE_KEY on RecordTypeId usually means Salesforce can't use the Record Type ID being sent by the integration for that transaction.

Even if the integration user has the correct permissions, I would check:

• Confirm that 0123F000002c926QAA actually exists in the target org and belongs to the object being inserted/updated.
• Check whether the Record Type was recently deleted and recreated. A recreated Record Type gets a new ID, so an integration using the old ID will fail.
• Verify the integration is pointing to the correct org/environment. Record Type IDs are org-specific and shouldn't generally be hard-coded between environments.
• Check the integration payload/logs to see where that RecordTypeId is coming from.
• Verify the Record Type is available to the integration user's profile/permission set.

If you can't find that ID in Setup or through a query, I would especially suspect a stale Record Type ID in the integration configuration or source system. 

If you can share the object being created/updated and the relevant integration payload (with sensitive data removed), it would help narrow down the cause. 

Hi Kyle,

For Web-to-Case spam, a few things are worth checking:

• Enable reCAPTCHA for the Web-to-Case form if your setup supports it.
• Make sure Require reCAPTCHA Verification is enabled in the Web-to-Case settings.
• Add server-side validation/rules to reject obvious spam based on email, subject, or other known patterns.
• Consider using a honeypot field or similar bot-detection approach if you're using a custom form.
• Review the source/IP patterns in the incoming Cases to identify common characteristics of the spam.
• If you're using a custom Global Action, verify that it isn't bypassing protections that would normally be present in the standard Web-to-Case flow.

Since your submission mechanism is custom-built, the exact solution will depend on how the action is generating the Case. If you can share the Global Action/LWC or Apex implementation and how the Community user submits the request, that would help narrow it down. 

Hi Patrick,

Could you share the exact HTML error message you're getting and the type of email template you're creating (Lightning, Classic, or Visualforce)? 

If possible, also share the HTML/code you're trying to save and a screenshot of the error. The solution can depend on the template type and the specific HTML being used. 

With those details, someone should be able to pinpoint the issue. 

Hi Dasiny,

You can build this using an Experience Cloud site and a Screen Flow. You don't necessarily need to expose the custom object directly on the Experience site.

A common approach is:

1. Create a Screen Flow with the fields you want the external user to complete.
2. Add the Flow to an Experience Cloud page.
3. Configure the external user's permissions for the Flow and the records/fields it needs to access.
4. Have the Flow create the record in your custom object.
5. Use Flow email actions (or an Email Alert) to send a confirmation to the external user and notify the appropriate internal users.

If you are trying to use the standard object's record/detail components in Digital Experiences, the object may not appear because of the site's object/permission configuration. 

Also, make sure you consider guest-user security carefully if the form is intended to be available without login. 

If you can share whether these users are guest users or authenticated Experience Cloud users, and which Experience Cloud template you're using, it would be easier to suggest the exact setup.