Additional Sort By fields in Browser Organization Scheme

[Ric_Weber]

Slightly edited:

Add additional Sort by: fields in the Browser Organization Scheme.  I don't need to group by it, just sort by it.  So first it groups by the Groups as it always has and then within each of those groups, it sorts by the first Sort by: field and then secondarily by the second Sort by: field and so on.  But without the grouping.  

Being able to add as many Group by: and Sort by: fields as we want would be the best scenario, but I'd be happy with at least one more Sort by: field in this dialog box!

Thank you.  

[Ric_Weber]

OK, so, what I think I'm hearing everyone say, and I agree, is this:  

• Unlimited "And" and "Or" schedule Filter rule list items; UI just like View Filters https://forums.autodesk.com/t5/revit-ideas/quot-or-quot-in-filter-rules/idi-p/6322629
• Unlimited "And then" items in the schedule Sorting/Grouping; similar in fashion/UI to the View Filters  https://forums.autodesk.com/t5/revit-ideas/more-than-4-sorting-and-grouping-criteria-in-a-schedule/i...
• Unlimited Grouping and Sorting options in the Browser Organization Schemes https://forums.autodesk.com/t5/revit-ideas/additional-sort-by-fields-in-browser-organization-scheme/...

Be sure to vote for each of these ideas if you agree with them.  Yes, I know, a bit of self promotion here... sorry .  Thank you!  

[Susana_Duarte_LMSI]

Actualy, what I need if for floor/ceiling/area plans to sort by Associated Level DESCENDING but simultaneously to all other view tipes (3D, sections, elevations) to sort by view name ASCENDING.

Can you please make this simple add in the setup?

[Ric_Weber]

@Susana_Duarte_LMSI, in order to do that, we would need basically a separate Browser Organization properties per Family within the Views category.  I can't believe I am saying this... but that is big enough of a different idea to probably warrant a whole separate idea post.  

[Susana_Duarte_LMSI]

@Ric_Weber, I did not want to complicate as much, even though you have a good point. 

A hole Browser Organization implies that one could choose witch parameter to organize the filters by. 

In this case I was sugesting using always the same parameter (only their value would be up to the user to schoose and having there the biggest flexibility possible). So, not really the same ideia. 

Witch one is better or easier to implement, I leave to the experts, as long as the bottom line is achieved and the UI is user friendly, I really don't care if it's one or the other (thought I would still stick to the first because that way you would not have to alternate between project browsers - something that has some ideias to improve here also - after all diferent users like diferent things and browser organization is a project configuration and not a user one. Just make sure you create easy ways to replace, remove or add keywords in several filters at the same time.).