#Analytics37 utenti parlano di questo argomento

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 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 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. 

I’d probably keep the Looker dashboard if it’s already bringing together data from multiple sources. If the main goal is to give users an account-level view inside Salesforce, I’d first look at whether embedding the existing dashboard can meet that need before rebuilding everything in CRM Analytics.

I’ve found this approach useful in other projects too. For example, with fit-out work, it often makes more sense to work with what’s already in place and improve the parts that need attention rather than starting everything from scratch.

Hi Emily,

This mismatch usually comes down to one of two things:

1. Hidden default date filter (most likely cause) — many Data Cloud/Analytics report templates carry an implicit time-range filter (e.g., trailing 7/30 days) that isn't shown as a visible chip. Open the report in edit mode, check the lens/query for a date condition, and widen or remove it.

2. Ingestion gap — go to Data Cloud > Data Lake Objects > your Form Submission stream > Data Explorer, and check the row count there directly. If it's already ~22-24 at that level, the issue is upstream in ingestion (check the Data Stream's refresh history for a partial/failed run), not in the report.

Also worth noting: "Individual with Form Submission" counts by resolved Individual, not raw event — so if your Identity Resolution match rules are broad, some submissions may be consolidating under fewer unified profiles. That's expected for that report specifically, but it wouldn't explain a similar gap on "Form Submission Event," which should be event-level.

Start with the date filter check — that resolves this in most cases.

Posting a solution incase anyone is trying to solve the same issue in the future. It may not be the most simplified solution, but it does give the correct results: 

month_last_day(toDate(
(case
when string_to_number(date_to_string(toDate(Existing_Date_Field_sec_epoch), "MM")) <= 6
then number_to_string(string_to_number(date_to_string(toDate(Existing_Date_Field_sec_epoch), "yyyy")) - 1, "0000")
else number_to_string(string_to_number(date_to_string(toDate(Existing_Date_Field_sec_epoch), "yyyy")), "0000")
end)
+ "-" +
(case
when string_to_number(date_to_string(toDate(Existing_Date_Field_sec_epoch), "MM")) <= 6
then number_to_string(string_to_number(date_to_string(toDate(Existing_Date_Field_sec_epoch), "MM")) + 6, "00")
else number_to_string(string_to_number(date_to_string(toDate(Existing_Date_Field_sec_epoch), "MM")) - 6, "00")
end)
+ "-" + "01",
"yyyy-MM-dd"))

Hi @Shravani Muthe, 

According to Salesforce documentation, Dated Exchange Rates are only used for Opportunities and certain Opportunity-related objects. They are not used for currency fields on other objects, including custom objects. 

Please refer below salesforce help article 

https://help.salesforce.com/s/articleView?id=sales.administration_about_advanced_currency_management.htm&type=5