Skip to main content The last day to register for a Salesforce or Tableau exam is June 30th. Learn more about the new Salesforce certification experience coming July 21st.

Feed

Connect with fellow Trailblazers. Ask and answer questions to build your skills and network.
1 answer
0/9000

Hi there! 

I'm trying to acomplish the challenge, but everytime I try to use the name and id API "Sales User Muted" it says it has been already used. I erased and started a new project but same error coming up. It should be a "Permission set group" but is not even showing.  

Can you help to locate that or what can I do to acomplish the task? TY 

Control What Your Users Can Access challenge not allowing me to use

 

 

 

#Trailhead Challenges

1 answer
  1. Today, 4:01 AM

    Hi , 

     

    You can also try the following methods. If they don't work, try using a new playground.  

     

     

    Run the following SOQL in the query editor of the developer console. 

    Record your ID.

    select Id,DeveloperName,MasterLabel from MutingPermissionSet

    The Id starting from 0QM is MutingPermissionSet

    Please replace the bold part with your ID

    https://<your domain>/lightning/setup/PermSetGroups/page?address=%2F0QMIg000000k9bc

    Change API name.  

     

    Hi , You can also try the following methods. If they don't work, try using a new playground. Run the following SOQL in the query editor of the developer console. Record your ID.

0/9000

Hi there, 

 

We’ve suddenly run into an issue with formal and informal greetings in Salesforce NPSP. 

 

Previously, the greetings were behaving correctly. For example, if a contact was marked as deceased (e.g. John [Deceased] and Margaret Smith), the formal greeting would correctly show Margaret Smith, and the informal greeting would show Margaret

only. 

 

However, last Friday we noticed that deceased contacts were being included again in both the formal and informal greetings. We initially assumed it might have been changed accidentally by a team member, so we corrected it manually. 

 

But this morning, we found the same record had reverted — the deceased spouse was included again in the greetings! 

 

Has anyone else experienced this issue recently? Any advice or suggestions would be appreciated. 

 

Thank you!

5 answers
  1. Today, 3:51 AM

    @Judi Sohn

    Thank you for your reply. 

    We usually tick the

    Deceased box, and the account greetings are then updated to the correct format.

    I'm going to check the Exclude from... checkbox fields, as some accounts didn't have the same issue and had those boxes checked. (The strange thing is, we're not usually the ones who tick those boxes — even when a donor is deceased.)

    It seems that ticking only the Deceased

    box no longer updates the account greetings automatically. 

     

    I will keep an eye on it.

0/9000

いつもお世話になっております。 

 

ある特定のユーザーを無効化したいと考えていますが、そのユーザーが使用されている箇所に影響があるのではないかと懸念しています。 

ユーザーがどこで使用されているか、ユーザーの使用箇所を調査する方法はありますでしょうか。 

ご教示いただけますと幸いです。 

よろしくお願いいたします。

2 answers
  1. Today, 3:47 AM

    @Keiji Otsubo

    さん 

    いつもありがとうございます。 

    オブジェクトの数だけSOQLのクエリーが必要とのこと承知いたしました。 

    使用されていそうなオブジェクトのアタリをつけて確認してみたいと思います。 

    ありがとうございました。 

     

0/9000

Hello if anyone could help with flow is greatly appreciated.. I have a flow to count number of attendees for events. I added another flow to recount the number of attendees when attendees get deleted but its not recounting. Not sure what could be the reason its not doing so..  

 

#Flow

 

Help with flow

 

 

2025-06-29_9-59-21 flow 2.jpg

 

 

4 answers
0/9000

I'm getting the error "We can't find that the Sales User permission set group mutes edit access for the annual revenue and customer priority fields.", from the Control What Your Users Can Access module. I checked that the Annual Revenue and Customer Priority fields have edit access muted, ensured I'm on the Muting Permission Set side, I'm just not sure what's going wrong on my program. Any help is appreciated.

We can't find that the Sales User permission set group mutes edit access for the annual revenue and customer priority fields.

 

#Security

3 answers
  1. Today, 3:44 AM

    Hi everyone 

     

    Please help. I still have difficulty with this.

0/9000

Hi team, 

 

I’m currently stuck in the "Business Process Automation" module. 

 An error message appears as follows: 

 

There was an unhandled exception. Please reference ID: PVMNRIHZ. 

 

Could someone please assist with this issue?

Thank you,

 

 

#Trailhead Challenges

1 answer
0/9000
2 answers
0/9000

現在、お客様の環境にて、キャンペーンやリードの名称をタブおよび表示ラベル、または翻訳機能を利用して、お客様に馴染みのある語句へ変更を行っております。

その中で、添付の項目についてもAccount Engagement由来で作成されたものと認識しておりますが、こちらの項目名をより分かりやすい表現へ変更したいと考えております。

例) 

 「展示会の配信済みメールの合計数」→「メール送信数の合計」

このような表示ラベルの変更は可能でしょうか。 

 どなたかご教示いただけますと幸いです。 

 

 Under Translate GPT 

 

We are currently updating the names of campaigns and leads in your environment—using tab and display labels, as well as translation features—so that these terms reflect language familiar to your team.

Among these changes, we recognize that the attached fields were also created as part of Account Engagement. We would like to update these field names to make them clearer and easier to understand.

For example:

  • "Total Number of Delivered Emails from Events" → "Total Number of Sent Emails"

Would it be possible to change the display labels in this manner? 

 If anyone could advise us on this, we would greatly appreciate it. 

 

@* MC Account Engagement (fka Pardot) * 

3 answers
  1. Jun 27, 6:20 PM

    Because Account Engagement is treated as a managed package, you are limited to changing only help text on fields with the namespace prefix pi.  You cannot change the core labels.

0/9000

I am looking to create a button/action that calls an autolaunched flow to post a chatter message. I am building this button/action on a custom object, but the flow is not showing as an option in the drop-down. Any ideas why? 

 

Flow not showing in Action

 

 

 

#Flow

2 answers
  1. Steven Trumble (Skie) Forum Ambassador
    Jun 24, 7:45 AM

    1) Make sure flow is active. 

     

     

    I think if you keep it as an autolaunched flow you'll need to use button instead of action in object manger.  

    If you want to use an Action you can build your autolaunched flow as a screenflow. 

    If you want to keep it as autolaunched then you can use the instructions here to create as a button: 

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

0/9000