Skip to main content A new Salesforce certification experience is coming July 21st. Discover how exams will be delivered in Pearson VUE, what it means for you, and ways to prepare. Learn more.

Feed

Connect with fellow Trailblazers. Ask and answer questions to build your skills and network.

フローで「メールを送信」を作成しています。 

 

デバッグで確認すると、下記のようになりメールが届きません。 

 

emailAddresses = null

ccRecipientAddressList = null

senderAddress = ●●.com(←正しいアドレスが入っている)

useEmailTemplate = True

emailTemplateId = 00XBI000000JTjA2AW

recipientId = {!Get_Contact.Id} (003BI00000E4RONYA3)

出力

なし。 

 

原因と対処法を教えていただきたいです。

4 answers
  1. Today, 1:00 AM

    @Keiji Otsubo

     

    送信元の設定が正しく設定されていなかったため、メールが送信されないようでした。お騒がせいたしました! 

     

    ちなみに今回のフローで送信したメールですが、取引先責任者レコードの活動ログに表示されましたが、これを別のオブジェクトに表示させる設定はフローで対応しなければいけないのでしょうか?

0/9000

We have old unused Apex Triggers and classes that are on old version of the API that being deprecated.  We want to delete them from our Salesforce instance, but there is no way on the front-end.  Any advice? 

 

#Salesforce Developer

2 answers
  1. Today, 12:48 AM

    I saw that but the scripts were created with API version 27 which is part of the API's that are being deprecated/retired, so if I just put logic in to ignore them, I assume I'm still going to get the warning emails constantly about the out of date API version components.  I suppose I'd need to investigate the Metadata API route, as even if I upgrade the API version of Apex resources, I'd still have to keep updating them with skip logic every time the API's become out of date.

0/9000

Hi, 

 

I created a permission set to grant certain users merge access for contacts. I granted CRED access and selected Modify All Records. However, when someone tried merging 2 contacts, they got this error message:  

 

Error Type: System.DmlException 

Error Date: 2025-05-15 19:44:08 

Message: "Merge failed. First exception on row 0 with id 001TR00000Q8YjvYAF; first error: INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY, insufficient access rights on cross-reference id: []" 

Context: CON 

 

Does anyone have any insights about this? 

 

Thanks!

2 answers
  1. Today, 12:35 AM
    Hi Ema, for non-admins to be able to merge, they have to be able to delete Account records they do not own, not just Contacts. The ID of the error is an Account. Try giving the user Modify All Records on Account as well and see if that helps.
0/9000

Hello, 

I have some Google Slides(with hyperlinks to different Google Docs) and other Google Docs that I would like to share with some partners. What are my options for including it in the Partner Portal (Aura)?  

 

5 answers
0/9000

I need to build an API in Anypoint Studio to accept a JSON payload that is sent to my endpoint and map that data for consumption in Salesforce. 

I have already built the API, so know how to get the data from the JSON to Salesforce, but have been given new specifications that require matching an Id from one object in the payload to an object in another object of the payload - the only issue being the Id is used as the object "name" value in the second section of the payload. This is where I need help as I have only ever referenced the values of fields in a JSON, not the "object name" 

 

I will be creating an Opportunity in Salesforce directly from Anypoint studio and need to be able to map the value that is stored in the object name to a value in my dataweave 

Simple example below - section of my payload looks like this and the value I need to extract is

3ce27e78-b419-477a-b4f7-5f9a5fe4834b

 

 

"Multiple Product Selection": {

"3ce27e78-b419-477a-b4f7-5f9a5fe4834b": {

"splitLoanData": [

 

output application/java

---

[{

Nimo_Security_ID__c: "object name here"

}]

 

This unique id is not represented as a value in this portion of the JSON payload, so I need to be able to grab the value from this object name section. 

 

Can anyone help? Full scenario below if it helps 

 

Full Scenario if it helps: 

Home Loan Application form sent to API endpoint as a JSON.  

This application is to facilitate multi-loans which are grouped at a property level, and can then be split into sub-loans. These applications can have multiple properties in it, which then need to be matched to the appropriate product selection and loan data for the resulting sub-loans. 

Array "Home Loan Multiple" can have 1 or more properties in it. In this section of the payload I am given a unique id for that property as a value, which I can extract easily - see below (last row) 

Each property in this section of the payload will become a "parent loan" under which there can be multiple sub-loans. 

Section 1 - "Home Loan Multiple":

"Home Loan Multiple": [

{

"fhb": "Yes",

"propertyImage": "example",

"amount": 500000,

"address": "example address here",

"opportunityName": "example",

"purpose": "example",

"from": "Home Loan Multiple",

"id": "3ce27e78-b419-477a-b4f7-5f9a5fe4834b"

}

 

So here I would have 1 x parent loan with the unique ID:

3ce27e78-b419-477a-b4f7-5f9a5fe4834b

 

The next section of the payload is where I am having difficulties. 

Section "Multiple Product Selection" is an object that then contains one or more other objects (I will refer to it as a sub-object for clarity) 

Each sub-object is named for the unique id of the property in the "Home Loan Multiple" section of the payload. Within this sub-object is an array called "Split Loan Data" which contains the specifics values for that sub-loan. There can be multiple sub-loans that roll-up and relate to the parent-loan - I need to be able to identify for each which parent loan it belongs to. 

You will see in the example below that the sub-object under "Multiple Product Selection" is NAMED for the unique id of the property. This id is not included as a value within this section of the payload, only as the object name. 

See example below:

"Multiple Product Selection": {

"3ce27e78-b419-477a-b4f7-5f9a5fe4834b": {

"splitLoanData": [

{

"goalsPurchase": "example",

"productNameQuote": "example",

"repaymentType": "example",

"id": "cc2d02f0-f33b-4e4e-b6dd-a30f92f27d04",

"loanFeatureOne": "offset",

"loanLengthInyears": 40,

"loanAmount": "200500"

},

{

"goalsPurchase": "example",

"productNameQuote": "example",

"repaymentType": "example",

"id": "ba2bf660-55fe-4cf0-b4be-d4023551c315",

"loanFeatureOne": "offset",

"loanLengthInyears": 40,

"loanAmount": "30000"

}

],

}

 

 

 

#MuleSoft  #Anypoint Studio  #DataWeave  #Json

0/9000

I am sending an email through Email tab of Chatter Publisher component from a Case Record page. The recipient are Salesforce user as well as User verified email ids. Even though I can see email logged in the system (showing up in activities as well) but emails are not showing up in recipient inbox.  

 

Any help and suggestion will be much appreciated. Thank you. 

 

 

#Salesforce Developer  #Sales Cloud  #Chatter

5 answers
0/9000

Hi all, 

I’m trying to understand why there is a significant difference between the data storage size shown in Salesforce and the actual size of data when exported.

 

For ex: when I export all fields values from an object into a CSV file, or extract the data (not compressed) through any data platforms, the resulting file size is considerably smaller than the size reported by Salesforce storage. 

 

Could this be related to specific configurations or background processes, and are there any recommended maintenance steps to optimize or better understand storage usage?

 

Has anyone else encountered/noticed this?   I would appreciate any insights into what factors or components contribute to this difference. 

Thank you in advance for your support.

4 answers
  1. May 15, 5:29 AM

    Hi @Selvazhaki Govindarasu

     

     

    Yes, what you're seeing is expected behavior, and it's a common point of confusion.

     

    Why the size reported in Salesforce is larger than exported CSV size:

     

    1. Record-Based Storage Calculation

    Salesforce does not store data based on raw byte size like a CSV file does. Instead:

    • Each record in a standard object typically consumes a minimum of 2 KB, regardless of the number of populated fields.
    • This applies even if most fields are null or only a few characters long.

    2. Internal Metadata and System Overhead

    Salesforce storage includes:

    • System fields (like CreatedDate, LastModifiedById, etc.).
    • Hidden fields used internally by Salesforce.
    • Relationships (lookup/master-detail), record IDs, indexes.
    • These don't show up in CSV exports unless explicitly selected but still count toward storage.

    3. CSV Is a Compressed View of Data

    • CSVs only store raw, visible text.
    • There's no metadata, indexing, or schema—just values.
    • Text compression (especially repeated values, short fields, or blanks) leads to a much smaller file size.

    Things That Do Not Count Toward Data Storage

    • Files, Attachments, and ContentVersions (they count under File Storage, not Data Storage).
    • Chatter messages, some setup metadata, and system logs (depending on context).

    Maintenance Tips (If You Want to Reduce Usage)

    • Archive/delete unused records.
    • Periodically clean up: 
      • Old Task and Event records.
      • ProcessInstance, FeedItem, and FieldHistory objects (which grow over time).
    • Consider using Big Objects or external storage if you're working with high-volume data. 

       

       

       Hope this helps! Let me know if you need more clarification. 

       Also, if you find this content helpful please mark it as the best answer.

0/9000

Already have the associate certificate and working on gaining the Salesforce Administrator certificate but would like to get the experience outside of trailhead.   

3 answers
  1. May 18, 11:27 PM

    What is best way to connect you Vinod

0/9000

I have around 6 years of BA experience in Salesfroce Product. Please share some thoughts or tips get in back to market . Currently looking for opportunity in fast paced environment . Do you know any contacts plese let me know. Thanks  

 

I am spending most of my day in LinkediN and Job portals

0/9000

First off, thank you to this amazing platform for enabling us to ask questions and share ideas — it's incredibly valuable! 

 

We’re currently implementing a brand new WhatsApp integration via Digital Engagement, and I was hoping to gather some best practices from those who’ve done this before.

Specifically, I have a few questions: 

 

  1. Meta Business Account setup  

    Is it best to register a

    Meta Business Account under the client’s business entity rather than using a personal Meta account? - I think this is a "No brainer - Yes"  

      

     

  2. Phone number strategy  

    Is it a good practice to:

    • Use one phone number for the Production setup, and
    • Get a separate number linked to the same Meta Business Account for the Dev/Sandbox environment to support development and testing? I believe we should not test using the Number that is in use for day-to-day business purpose.
  3. General setup advice  

    What are some “must-do” items or best practices when setting up WhatsApp for Salesforce? 

 

Any recommendations, advice and suggestions would be of great help.

2 answers
  1. May 18, 11:20 PM

    Hi @Peter Jones

     

    Thank you for your reply! 

     

    I will be keeping an Eye Out for the Help Article. But, given that there are sooo many help articles relating to the same topic, could you please point me to the correct Link when the video / article is published? 

     

    Update: I think i got this:

    Link Here

0/9000