Skip to main content Besuchen Sie uns auf der TDX in San Francisco oder bei Salesforce+ vom 5. bis 6. März, um die Entwicklerkonferenz für die Ära der AI-Agenten zu erleben. Jetzt registrieren.
Vorgestellte Gruppe

* Known Issues *

Welcome! This group is dedicated to everything around Known Issues, Salesforce’s bug transparency site where we publicly share the status of our software defects. Join the conversation here to stay up-to-date and connect with the Known Issues team. --------------------------------------- This group is maintained and moderated by Salesforce employees. The content received in this group falls under the official Forward-Looking Statement: http://investor.salesforce.com/about-us/investor/forward-looking-statements/default.aspx
Verankert

📢 Welcome to the Known Issues community group!

 

We're dedicated to addressing questions about Known Issues, Salesforce's bug transparency site where we publicly share the status of our software defects. If you have a question about the site, or our latest updates or simply want to share your feedback, please do so! We're monitoring and will answer you back as quickly as possible 😊

 

If you have a question about a Salesforce product, please post it in the relevant group to make sure you get a quicker answer from our community of experts! See below for the main products group links:

 

Find the full list of product groups here.

 

Thank you and welcome! 🎉

The Known Issues Community Managers team

0/9000
1 Antwort
0/9000
4 Antworten
  1. 5. Dez. 2024, 17:06

    Great question! @shubham patil Here's how you can resolve this issue.

     

    Solution Steps:

    1. Verify Opportunity Splits Settings: 

       - Navigate to Setup > Opportunity Splits Settings. 

       - Ensure that Opportunity Splits are enabled and the "Opportunity Owner Split" is set up.

     

    2. Check User Permissions: 

       - Confirm that the user has the necessary permissions: 

         - Manage Opportunity Splits permission. 

         - Edit Opportunities permission. 

       - If not, update the user's profile or assign a permission set.

     

    3. Page Layout Configuration: 

       - Go to Setup > Object Manager > Opportunity > Page Layouts. 

       - Ensure that the Opportunity Splits related list and the "Edit Opportunity Splits" button are added to the relevant page layout.

     

    4. Verify Record Type and Profile Settings: 

       - Confirm that the record type assigned to the user includes access to Opportunity Splits. 

       - Check the assigned profiles or permission sets for any restrictions on Opportunity Splits.

     

    5. Check Sharing Settings: 

       - Ensure that the user has access to the opportunity record in question, as visibility impacts the availability of Opportunity Splits.

     

    Why It Works:

    The "Edit Opportunity Split" button is only visible if Opportunity Splits are enabled, configured, and the user has the necessary permissions and access. Page layout and record visibility also play critical roles in determining what actions are available to the user.

     

    Additional Advice:

    If, after setup, the button still does not display, use the Sharing Hierarchy to solve visibility issues.  

    To isolate the problem, try using a user with a different profile or set of permissions.  

    During system audits, check Opportunity Split settings often to make sure they are set up correctly and accessible.

0/9000

Hello Community, 

 

We are seeing a unique issue in one of our Winter 25 Sandbox, where the custom label is not showing the latest value in LWC on the experience cloud page. We tried upgrading LWC API to 61 but still does not fix. Any guidance or suggestions. ?

 

Thanks

Koushik

5 Antworten
0/9000
1 Antwort
0/9000

See screen shote below.  Why can't I select status and filter and why does "found release" not show version it makes it difficult for customer that only have  Tablea version numbers to reference.

known issues found in release.jpg

 

known issues status .jpg

4 Antworten
  1. 23. Okt. 2024, 18:28

    @Walberto Gonzalez This request is more complex than just fixing the status bug; it will require significant effort from the Tab team and other involved teams. For now, it's been added to the backlog. We'll keep you updated as soon as there are any developments. Thank you. 

0/9000

I had to update the API version on a flow created some time ago to the current one in order for repeaters to work properly with loop on the repeater collection. Finished up the area of change, tested change, and activated. Early adopted quicly reported that they couldn't do work... further regression testing shows that the Finish (or next) button was missing from almost all screens. Oddly, it was not missing from the screens edited in the one area of change but missing from almost all the others. It's a terrible thing to happen, but we have hundreds of screen flows that need to have API version updated. (I know why we do it, but I don't like that we leave the flows behind when we update flows... we need to stop that and find a way to un-orphan all these older flows.). Anyway... known specific and limited issue or am I going to encounter this every time I bring the API revision up to latest version?

 

I have the flow revisions still, although we normally purge the interim steps that show the interim work product and only keep the tested releases.

 

@Alex Edelstein @MVPs & AppExchange All Stars @* Known Issues *

 

@Salesforce Flow Automation 

2 Antworten
  1. 21. Okt. 2024, 13:53

    How long ago was the flow created? Knowing what the original API version might help here, but I can't think of anything in the past couple of years that would've led to this behavior. 

0/9000
0/9000

We are getting that error when user try to post opportunity chatter in Production org but not in Sandbox. Do you have any idea how to fix that issue? 

 

UpdateRPforFeed: execution of AfterInsert caused by: System.QueryException: List has no rows for assignment to SObject Class.updateRPFeedHandler.updateRP: line 34, column 1 Class.updateRPFeedHandler.updateRPFeedFeaturePoints: line 26, column 1 Trigger.UpdateRPforFeed: line 6, column 1

3 Antworten
  1. 26. Aug. 2024, 00:22

    Thank you so much for your both suggestion. I have checked the code in both environment and codes are same.

     

    This query is based on the query in  NetworkMember object, which is an Experience Cloud site object managed by Salesforce. It seems that the profile cannot access this object. When I add that profile as a member of the Experience Cloud site, the error no longer occurs, but I believe this is not an ideal solution. Do you have any idea about it?

0/9000

Hello everyone,

I have a question, Is it possible to find the time spent on each picklist. I have a picklist field on Opportunity. And I wanted to record time spent on each picklist(must include only business hours). 

 

Say picklist 1, picklist 2, ,picklist 3, picklist 4.  I would be changing from picklist 1 to picklist 2 and go back to picklist 2. So after my Opportunity is closed won I should be able to record total time spend on each picklist. 

 

Is this possible to achieve via flow? or is there any app which can support this feature? Please suggest on possible solution.

3 Antworten
0/9000

Greetings,

 

Internal organization agent/admin submitting the Survey response by clicking invitation link the behalf customer.

  1. Hiding the invitation link on Survey Invitation layout is not right solution for admin, and Invitation link fields on Survey Invitation object is locked field so the FLS cannot be changed 
  2. Survey Invitation or Survey Response records being updated by Guest user either ways click Invitation Link by internal user or by customer  

I am looking for solution, if any internal user clicks on Invitation link, I should prevent to submit the survey response.

 

and also, if the Omini product has any security settings to control/limit access to the survey invitation link in the org?

 

I really appreciate your reply soonest possible. Thanks

@Salesforce Surveys @* Experience Cloud *

1 Antwort
  1. 1. Aug. 2024, 17:29

    The Survey Response record has a field IP Response. It is the IP address of the device the participant used to take the survey.

     

    You cannot block the IP Address, but you can monitor the IP Address and find those "stuffing the ballot box."

0/9000