まとめページに戻る
Trailhead関係 年月で整理に戻る
参照して頂くのは結構ですが、そのまま内容を丸ごとコピーするような行為は控えて欲しいです。一応時間を掛けて作っているので、その点はご考慮願いたいです。
なるべく、回答の中身も転記しておきます。結構な割合で質問者さんが黒歴史を消したいのか質問自体を削除しますので... 最良の答えとしてもらっても即消されることは大変多いです。
5月は過去最低と言うくらい質問は少ないし回答しても反応はありませんね。回答しても半分以上は返答もないですね。もしかしてボットが質問しているんではないか?
We don’t show the Solutions Full Access Permission Set assigned to your User.
サポートへ
The flow doesn’t have pause configurations, with pause conditions met, for time-based resume events. Resuming platform event-based resume events, whose conditions have been met, is not supported.
I hit the same issue when debugging the Flow, however the easy resolution is to Disable Debug pause element behavior after hitting Debug.
The pause will then work and you can view the status by navigating to Monitor Workflow Services in Setup.
We can’t find a user with ‘Salesforce’ selected in the License field.
同意設定
Please check this article.
https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000JdG4ZSAV
Required fields are missing: [MasterLabel] while deploying chatbot
For anyone who finds this later, specifically for Einstein Bots, I encountered a similar problem with the MasterLabel error and did the following to fix it:
- Ensured my sourceApiVersion used in our CI/CD and target org was updated to the latest version (which was 64.0 at the time of posting). If yours is not up-to-date, you can include the sfdx-project.json file in the pull request. Check the API version of the target org you're deploying to by
generating s Enterprise WSDL
. You can't update the api version via a change set so you'll have to do this step ahead of time if you're using change sets.
-
Ensure the bot being deploying is inactive in the target org. I also made it inactive in the source org before adding it to my pull request. In change sets you'll only see the bot, but in other deployment tools, you'll see Bot and Bot Version. You'll need both of these to deploy properly.
-
Try to deploy.
Agentforce recommended the sourceApiVersion update and past experiences deploying bots went much smoother with inactive bots. Note that my bot did not have any
components that could not be deployed, at least last time I tried deploying them (i.e. messaging components).
page emdatasetupload の式「{!uploadEMCsv}」にエラーがあります: Class.Upload_Init_EM.: line 36, column 1
List has no rows for assignment to SObject
page emdatasetupload の式「{!uploadEMCsv}」にエラーがあります: Class.Upload_Init_EM.: line 36, column 1
Class.Upload_controller_EM.uploadEMCsv: line 69, column 1
予期せぬエラーが発生しました。 開発組織に通知されました。
言語設定と地域も英語にする