In the database view, we could go to a project and set up account restrictions using wild cards. For instance, I could say only allow accounts that have 10-40-2900-****-13. It would only allow those that fit that parameter. Now in NXT, I have to enter either a range, query or exact account number. If I use a range and accounts get added outside of that range, it doesn't pick them up. If I use a query, I have the same issue. It doesn't let me use wild cards to specify which accounts are allowed. Why was this functionality removed?

You can not use wild cards in NXT on a project.

we should also have the ability to use wild cards when searching for a vendor or client

Previously, we could go into database view and under account security, we could use wild cards to set restrictions. For example, I could restrict a user to a certain group of departments by saying they could only see the range of 10-**-2***-****-** to 10-**-3***-****-** and they would only be able to see departments that start with a 2 or a 3. Today I tried doing this for a new user and that feature has been removed from database view. I was able to do a work around with a query, but it was much easier when wild cards were allowed. Will that feature be coming in webview?

Has this been considered as an addition to web view?

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.