Bases: Group By / Sorting improvement: make a note fall into multiple groups

There is one. You can use DataviewJS.

+1

I managed to achive something similar with a custom view, but it would be way better to have it as a standard feature.

It would also be awesome (at least IMO) to have the group title to acts as a link, and clicking that link search all the notes with that property (like with tags), for example clicking on Finance will search all the notes that have the area property which contains Finance

+1

This is exactly the behaviour I am after.

Thank you. I have heard of DataviewJS, but I am not a programmer.
Instead, I did try submitting the Use Case / Problem into Perplexity.ai, asking if it could help? Perplexity came back with the following (see below). In the absence of this “Making a Note fall into Multiple Groups” feature request becoming a priority, I guess trying working with DataJS in Obsidian is next best option. Thanks again
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
PERPLEXITY.AI >
Yes, I can provide a DataviewJS workaround for multi-value properties like your “area” field, where notes with multiple values (e.g., NOTE1: [“Finance”, “Business”]) appear in each relevant group. This manually expands arrays and groups notes across categories.

Core Workaround Code
Paste this into a dataviewjs code block in Obsidian. It queries pages with an “area” property, flattens the array for multi-grouping, and renders headers with note lists.

text

// Get all pages with 'area' property
let pages = dv.pages().where(p => p.area);

// Create map: area value -> list of notes
let groups = {};
for (let page of pages) {
  if (Array.isArray(page.area)) {
    for (let area of page.area) {
      if (!groups[area]) groups[area] = [];
      groups[area].push(page.file.link);
    }
  } else {
    // Handle single values
    let area = page.area;
    if (!groups[area]) groups[area] = [];
    groups[area].push(page.file.link);
  }
}

// Render sorted groups
Object.keys(groups)
  .sort()
  .forEach(area => {
    dv.header(3, area);
    dv.list(groups[area]);
  });

## Example Output
For your use case:
```
### Finance
- NOTE1
- NOTE2

### Business
- NOTE1
```
NOTE1 appears under both "Finance" and "Business"; NOTE2 only under "Finance".[1]

## Customization Options
Filter by folder or tags by modifying the `pages` query, e.g., `dv.pages('"Your Folder"').where(p => p.area)`. Sort notes within groups by adding `.sort(p => p.file.name)` before `dv.list`. For tables instead of lists, use `dv.table(["Note"], groups[area].map(link => [link]))`.[7]

+1 to this request. the current behavior can remain the default with a toggle in the sort menu for users who want this behavior

this is insane

Strong agree with this request, and the various examples given in the comments above illustrate why this request is more logical and intuitive as a default behaviour.

To me this seems rather obvious.

+1 for this FR from me.

Honestly surprised that this is not the default. Would love this

+1 because this introduces some friction in my workflows (e.g. notes for “nodes" can be in multiple graphs). Workaround is to create seperate views, but this hides the overview and fact that nodes do not exlcusively belong to one category or the other.

No worries I’ve vibe coded it too :smiley:

I also dislike the current implementation of this feature.

Being able to group things into multiple groups would be massively helpful. Being able to assign characters to multiple families or towns, being able to list songs under multiple artists, and far more. Having “John” “Perry” and “John, Perry” as separate groups is a rare want. It can be helpful if you want to look for collabs specifically, but it isn’t for general purposes.

Sort By being able to sort each item in a list property individually is also helpful, though in a way that is less immediately obvious for a lot of people. But it still is very helpful. Like if you have a base of incident reports of a house and you want to mark down every time the house loses power. You dont need a new note for each power loss incident, even if you have unique notes for getting mice or mold or whatevet. You still want to mark down the power loss, but not have a bunch of the same identical notes with the only difference being the time.

Or if you’re writing a note about a collection of things where you don’t care about the specific members of the collection, just what are possible things that exist in the collection. Like.. What colors things come in is something you sort by and you have a large collection of figures that are identical though they have different colors. You would want the figures to appear next to each of the individual colors even if you don’t group by colors.

I personally would find the sorting helpful for mapping out time travel shenanigans, as an event may appear twice within an individual person’s timeline and I would rather have events be their own notes that link to/are linked to by character notes.

+1
This is exaclly what I need right now

+1 Must have.

+1. It should also work for document tags (file.tags), so that I could see notes grouped by individual tags (not by clusters of all the tags assigned to the note)

+1 to this from me too.

I’m using the grouping feature for deciding which categories to assign to my production items. Some must have multiple categories. I can’t effectively make the decisions if I can’t see that an item that isn’t showing up in category A does in fact have that category name assigned. It keeps throwing my brain into inefficiency loops - something that Obsidian usually lets me avoid.

I’ve made separate views for each category and embedded them on a note but it’s cumbersome to have to make multiple separate tables when the grouping feature exists.