34

Hello,


It would be nice if "AL Explorer" in VS Code Extension "AL Language" could support wildcards characters for filtering like old NAV Object Designer.


Today it is not possible to effectively filter e.g. "*Cr*Memo*".

It is hard to find all instances "Cr. Memo", "Cr.Memo", Credit Memo"...


Thank you.

Category: Development
STATUS DETAILS
Completed
Ideas Administrator

Thank you for this suggestion! In 2024 release wave 2 we are adding support for `*` and `?` wildcards. It is not full filtering support, but still very powerful. Thus closing this idea as completed. For the full filtering, consider adding a separate idea.

Comments

T

As a better alternative you can use the "AZ AL Dev Tools" VS Code extension which includes a feature-rich object browser which supports filtering capabilities where you can use the same filtering syntax as you can use in the BC cluent.It already has these capabilities since January, 2019 ;)

Category: Development

T

This is a great BC Idea submission but I would argue to take it even further. The original cside object designer allowed full filter syntax: brackets, boolean operators, wildcards, ranges, case insensitivity, etc. This is all absent in AL Explorer. This is what the developers are familiar with. AL Explorer's simplistic searching and filtering doesn't meet our needs.

Category: Development

T

Because we can use that in the normal search in VS Code - same thing would be nice in the AL Explorer.

Category: Development

T

That is exactly what regex is for :-)Can't you use that option?

Category: Development

T

Please make using wildcards possible, this will be great help.

Category: Development