Feed

カリキュラムに従って一通り設定しましたが、 

の設定でエラーが出てしまいます。  

[Filter Records]の[Field]で

が入力出来ない為、 

他の投稿を参考に[Individual Id]で試しています。 

エラー表示と、

の設定画面を添付しますので、参考になれば幸いです。 

どのように解消すればいいか教えてください。 

Tank you!

What is the prerequisite before going to salesforce admin certification?    Do I need to complete some trailmixes ?  

My "Developer Edition org for Agentforce Authentication" is not getting created. I've been waiting hours and it is not coming through! And I have requested one twice. Anyone seen this? This trail "Learn About Authentication for Topics and Actions" requires that I use this specific org to complete the Module, so I am stuck.  

I cross checked many times but it is showing error like this only. 

Module:

I am unable to resolve this - in Topics, I am unable to get the option to input " experience management"  

I am currently experiencing an issue where a Salesforce dashboard cannot be saved. Below are the steps to reproduce the issue and a description of the problem: 

1. A Standard User created a dashboard that includes filter conditions.
2. In the “View Dashboard As” setting, Standard User from the same role was selected as "Another User".
3. After editing the dashboard and clicking “Save,” an error appears below the dashboard filters: 
   “Remove this filter. Its filter field is no longer available issue.” 
   I have confirmed that the fields used in each filter condition exist in the Org and that both the running user and the editing user have access permissions to those fields.

Goal:

I want to save the dashboard while:

• Setting the running user to another user in the same role, and
• Keeping the dashboard filters active, 
  without encountering the
  “Remove this filter. Its filter field is no longer available issue.”

I have already investigated and confirmed that assigning the editing user to a higher role than the running user can avoid this error. However, due to our company policy, I cannot assign users to higher roles.

If anyone has other ideas or suggestions, I would greatly appreciate your comments. 

Hi Everyone 

I'm encountering an issue with order status not reflecting correctly on the confirmation page immediately after updating it using OCAPI. Specifically, I'm calling the OCAPI PATCH /orders/{order_no} endpoint to update the order status from "created" to "new", and the API returns a success response. Right after that, I redirect the user to a confirmation page, which is rendered using a server-side controller (like Order-Confirm). In that controller, I fetch the order using OrderMgr.getOrder(orderNo). 

The problem is that when the confirmation page first loads, it shows the order status as "on_hold", which is incorrect. However, if I manually refresh the page, it then shows the correct status "new". This makes me suspect that the controller is accessing a cached or stale version of the order object, even though the status was successfully updated through OCAPI. 

Is there any way to get the refreshed order object not the stale one? 

Thanks 

#Trailhead Challenges