In the 'Chatter Post to Account Owner' element, we can’t find the 'Target Name or ID' field set to '$Record > Id'.
$Recordのラベルが変わっています。
In the 'Email Lead Routing' element, we can't find the action set to the 'Send Matching Account to Lead Routing'
In the 'ChatterMessage' text template, we can’t find a mention for the account’s owner. (Hint: Review the syntax for at-mentioning.)
これでなく、もう一つが正解みたい 2024/07/16
I see space in your code, please try below.
@[{!$Record.OwnerId}]
2つ答えがある?
こっちが正しい
- How do i mention the account owner in the chatter message text template body? Can I get the proper syntax?
- In the 'ChatterMessage' text template, we can’t find a mention for the account’s owner. (Hint: Review the syntax for at-mentioning.)
please try below.
@[{!Look_for_Matching_Account.OwnerId}]
please try below.
@[{!Look_for_Matching_Account.OwnerId}]
https://trailhead.salesforce.com/trailblazer-community/feed/0D54V000076BjfDSAS
In the Chatter Message text template,we can't find a menthon for the account's owner.
@[{!Look_for_Matching_Account.OwnerId}]
In the 'Update Matching Account' element, we can’t find a field value that sets the 'Possible Matching Account' to 'Look for Matching Account > Id'.
I think there is a problem with the 'Update Matching Account' element. Compare the difference with the video.
Please check this video.
In the 'Chatter Post to Account Owner' element, we can’t find the message set to use the 'ChatterMessage' text template.
I had previously saved the flow of the Post to Chatter action element's message input value as "the ChatterMessage text template."
I simply copied and pasted the text into the input value instead of selecting the ChatterMessage text template. After realizing the mistake, I made the change but since I had not saved the flow as a new version I kept getting the same error.
Conclusion: The problem was solved by saving the current flow as a new version.
以前、 Chatter に投稿アクション要素のメッセージ入力値のフローを「 ChatterMessageテキストテンプレート」 として保存しました。
ChatterMessageテキスト テンプレートを選択する代わりに、テキストをコピーして入力値に貼り付けるだけです。間違いに気づいた後、変更を加えましたが、フローを新しいバージョンとして保存していなかったため、同じエラーが繰り返し発生しました。
結論:現在のフローを新しいバージョンとして保存することで問題は解決されました。