You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/dynamics-365/sales/button-in-command-bar-not-appear-after-grid-item-selection.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,8 +4,9 @@ description: Button in command bar doesn't appear after grid item selection in M
4
4
ms.reviewer:
5
5
ms.topic: troubleshooting
6
6
ms.date: 03/31/2021
7
+
ms.custom: sap:Opportunity
7
8
---
8
-
# Button in command bar does not appear after grid item selection in Microsoft Dynamics CRM Online
9
+
# Button in command bar doesn't appear after grid item selection in Microsoft Dynamics CRM Online
9
10
10
11
This article provides a resolution for the issue that the button customized to show doesn't appear as expected after one or more grid items are selected in Microsoft Dynamics CRM Online.
11
12
@@ -29,11 +30,11 @@ This means that buttons that don't require an item to be selected, will simply n
29
30
The method that the determination is made is based on whether the command associated with the ribbon button has a SelectionCount rule. If it has a SelectionCount rule, it's considered to be an *item-specific* command.
30
31
31
32
> [!NOTE]
32
-
> Flyouts and split buttons are excluded from this change, and still shown in both cases of when items are selected or not. This is to ensure that menu items, some of which may be generated dynamically, is not incorrectly hidden.
33
+
> Flyouts and split buttons are excluded from this change, and still shown in both cases of when items are selected or not. This is to ensure that menu items, some of which may be generated dynamically, isn't incorrectly hidden.
33
34
34
35
## Resolution
35
36
36
-
This is designed behavior, that affects all buttons, not just custom buttons, but out of box buttons as well (Note - flyouts and split buttons excluded since they have a menu with further child buttons and cannot be easily categorized). This is an explicit design change from web client to Unified Client.
37
+
This is designed behavior that affects all buttons not just custom buttons, but out of box buttons as well (Note - flyouts and split buttons excluded since they have a menu with further child buttons and can't be easily categorized). This is an explicit design change from web client to Unified Client.
37
38
38
39
In most cases, it's helpful to hide buttons that don't act on selected items, so that *item-specific* commands appear more prominently.
0 commit comments