For example, when looking up accounts, in the search box, you should be able to type something like 01-488***-01-05. This is just one instance of where wildcards would be valuable. This is a feature in database, not in webview.

Suggesting the option to use a query of accounts instead.

Thank you for looking at this. It is in the projects record under general ledger. In Database view, we are able to go to the project record, then the account restrictions tab, and then we are able to add a record shown above which uses **** in the place of our account code. In NXT view, we navigate to the project record and select edit, then there is a section called Account restrictions. If we try to use **** for the account code when adding an account it will reply with Account not Found. So in NXT view we are required to use the actual account codes for restriction or what we allow to be used instead of being able to use the **** wild card.

Hi Pamela and Patrick - We appreciate your input. Could you kindly let us know the areas where you are unable to use wildcards for account restrictions? Is it on the project records, or somewhere else? thanks.

If this functionality is not brought over to NXT when database view goes away, it will cause a much greater administrative burden to manage each restricted account as they are added.