We are just switching on the case feed within our Salesforce org but have noticed a rather irritating
issue. We have a number of custom buttons and when we go into the list and click on the link /
button within the drop down list all works well.
for example ‘Case ID’ is simply a javascript alert that shows the Case ID (this is just an example). We click from the list as in one of the values as shown here
and we get this:
if we do this from the default value in the list
then we get redirected to ( http://{instance}.salesforce.com/undefined )
this seems to be the case for any javascript buttons only. If the button is simply a link to some normal or visualforce page, it works fine.
Does anyone have any suggestions on a workaround until Salesforce fix what seems like an apparent platform issue? I’d love a solution that is efficient, i.e. not requires redirecting to some visual force page which does what the button should do and the redirects back to the case we came from.
Answers:
Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.
Method 1
Answering my own question. Salesforce have confirmed that the behavior is a bug with no known release date for fix. The best workaround is to switch from custom button to custom links which are rendered differently in case feed (one by one in a list, not as options in a dropdown). That means all “buttons” are visible all the time and clicking them will work as you expect without bugs.
All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0