Select all: the twenty visible items or two thousand results?
Bulk selection across filters and pages: selection counts, hidden items, all results and clear omissions when creating a package.
Article language: English

In this article
A "Select all" button takes up little space and has unusually broad ambitions. Twenty files are visible on screen, two thousand match the filter, and the library contains even more. Which "all" has the user just selected? That cannot be filled in after the download package has started.
Bulk selection is an agreement about the scope of an action. The checkbox in a list header should not mean the current page one time and the entire catalogue another time, depending on what is easier for the application to perform. The design must show the boundary, the number of selected items and the effect of changing the filter or page.
Consider a fictional library of materials belonging to Kadr studio. A person preparing a presentation selects approved photos for a package. The list has pages of twenty rows, project and language filters, and files with different access statuses. The task here is to select items and present the scope. Actually creating the package and respecting permissions require separate checks in the implementation.
Show what the first selection covers
The simplest option selects only items on the current page. The label could then say "Select 20 files on this page". If the last page has seven items, the number must reflect that state. Do not show twenty simply because that is the configured page size.
In the Cloudscape Table view pattern, the header checkbox selects visible rows, and moving between pages overwrites the selection. This is one specific behaviour, not a rule for every table. Define and explain the boundary for your own design, then check how it works in the component you use.
Kadr may need to gather files from several pages, however. In that version, the selection persists when the user moves on, and the counter shows the total number selected. When three files are selected on the second page, the user should also be able to recognize the seven retained from the first. A "3 selected" view would suggest a different scope from an operation on ten items.
Do not forget a failure to load the next page. No visible rows after a failed request does not mean the list is empty or that the earlier selection has disappeared. Show the view error and the retained selection state according to the chosen rule. The user should be able to retry loading without accidentally triggering the bulk action.
Do not confuse the number of results with the number selected. "2000 found" describes the filter; "20 selected" describes the user's decision. These can appear near each other but need different labels. Otherwise, a large number above the table starts acting like a promise even though no one has selected most of the files.
If the first checkbox selects the page, extending the selection to all filtered results should be a separate, clear decision. For example: "20 files on this page selected. Select all 2000 filter results." After the extension, show the new scope and how to clear it. The user should not have to infer the change merely because a small message disappeared.
After extending the selection, remove one file in the test. The design must show whether the result remains all matching results with one exception or becomes a list of specific selected items. The counter should reflect that decision. If the user activates the header checkbox again, they should be able to tell whether it reselects the omitted file, selects the page or clears the entire set.
The partially selected state matters too. The Carbon data table documentation describes three states for the header checkbox: unchecked, checked and indeterminate when selection is partial. Actions apply to selected items. This description does not itself establish the scope of selection across pages, so do not infer one on behalf of the design system.
In our design, the partial state should be readable along with the count and scope. If two of twenty visible items are selected, the user must be able to extend or clear the selection according to the chosen rule. Acceptance should check this with a keyboard and an interface-reading tool as well, without relying solely on the shape of a small indicator.
Selecting a row, expanding its details and opening a file should be distinguishable actions. If the whole row opens a document, the selection area must not accidentally open the preview. On a phone, test this with longer names; for keyboard use, preserve a clear file name for each checkbox. A row number alone will not help after sorting changes.
The filter changes the view. Does it change the package too?
The person at Kadr selected ten photos and narrowed the list to the English version. Six selected files disappear from the screen. Decide whether those six items remain selected. They may remain selected, be removed after a deliberate clear action, or selection may be limited to the current view. Each model needs a clear message.
If selections persist, show the number hidden by the filter and a way to review them. "10 selected, including 6 outside the current view" describes the state more usefully than a silent counter in a corner. The user should be able to open the set and deselect a specific file without reconstructing earlier filters from memory. A "Remove from selection" button should mean exactly that. Do not use only "Delete" if the same library also permits deleting documents. The preview can then be used to correct the package scope without uncertainty about whether library assets were changed too.

In the selection preview, retain the information needed to distinguish versions. Two files may have the same title but concern different editions of a project. The number "10" does not answer whether it includes the right photographs. A thumbnail, version label or project name may be needed; choose based on how the team actually recognizes material.
If the design clears the selection when the filter changes, the user should understand that rule before losing work. Do not make them discover it after several minutes of assembling a package. Automatic clearing may be acceptable for a short list; for a longer task, consider explicit confirmation or another way to organize the selection. Test the decision against a task the company actually performs.
Designing filter state and search results (in Polish) covers filter behaviour. Bulk selection adds a second state that may survive a change to the first. The mockup should therefore show both at once: which files are visible now and which belong to the planned action.
When selecting all results, also establish whether the selection is a specific set or a search rule. In the first version, a file added later will not enter the selection. In the second, it may belong if it matches the filter. The difference has a real effect. The design must connect it to the application's behaviour, not just choose whichever message sounds more convenient.
Kadr may decide that the package covers the selection state at the moment of confirmation. In that case, show the count and important conditions before starting. If the list has changed in the meantime, the application should resolve the scope and report the change according to the agreed mechanism. The "Create package" button alone does not freeze data without appropriate system behaviour.
Selected does not always mean executable
A selected photo may have been withdrawn or be unavailable to the user. The team must decide whether such an item can be selected and how the restriction is shown. There is no single answer for every task. The shared requirement is a recognizable scope: what was selected, what the application can process and what needs a decision.
If the operation will skip unavailable material, show that before execution when the state is already known. "Prepare 18 of 20 files" should lead to an explanation of the two omissions. The user can then accept a smaller package or return to the selection. Hiding exceptions behind a generic "done" leaves them to count downloaded files by hand.
When a restriction appears only during processing, the result must identify what was actually prepared. Long-running tasks on a page (in Polish) covers further communication about progress, interruption and return. In the summary, distinguish the number of files selected from the number of results prepared. When items are skipped, show whether processing can be retried for those missing or the user must return to the selection.
For a partial result, let the user review skipped items and a reason they are permitted to see. Do not reveal the contents of an inaccessible file just to explain the restriction. A message can refer to the selected item and the next course of action while maintaining the appropriate information boundary.
Likewise, a file count does not determine order. A user may sort the list by name even though the package uses a separate order. If order matters for the presentation, it must be designed explicitly. Reordering items with an alternative to dragging (in Polish) is a separate operation; it should not start accidentally during selection.
Show the available shared actions in the design too. If an action is unavailable for some selected items, explain why it is unavailable or which items will be skipped. A greyed-out button alone does not tell the user what they can change to finish the task. Clearing the whole selection should not be the only way to find one problematic item.
Also distinguish "Clear selection" from "Cancel package preparation". The first changes the input before a task starts; the second concerns a task that may already be running. If both appear in one panel, name their effects and states. The user should not think that deselecting rows stopped a download already in progress.
Review the sequence, not just one checkbox
For the test, prepare several pages of files and establish the expected set in advance. The user selects part of the first page, moves on, changes the filter and removes one selection. Before starting, they should be able to say what will enter the package and whether any items are outside the view. Checking that checkboxes can be pressed is not enough.
Next, test extending the current page selection to all results, if the design offers it. Add a new matching item and change access to one of the earlier ones. Compare the result with the agreed selection rule. These cases show whether the counter describes the actual set or only the last number displayed above the list.
In an automation, such a set must remain linked to records and their versions. Batch task results (in Polish) need checking on the processing side. If an operation requires approval, approval of the action (in Polish) should cover the same scope that the user assessed. A summary mockup helps make a decision; it does not replace checking execution.
When talking to Aeneia Design, show the list and explain how the user gathers material for one task. The most valuable moment is when the selections no longer fit on the screen. The design must then preserve orientation: which "all" was selected, how many items remain and what exactly will happen at the next step.








