Allow wild cards when setting account restrictions in NXT
In database view, you can use wild cards for account restrictions (EX: 10-10-6100-****-00). However, in NXT you cannot use wild cards.
Please allow us to use wild cards in NXT as it is critical to our Accounting department and we don't want database view to go away without it.
-
Guest
- Sep 1 2023
- Reviewed: Need Further Info
Related ideas
we should also have the ability to use wild cards when searching for a vendor or client
Attachments Open full size
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?
Attachments Open full size
Has this been considered as an addition to web view?
Attachments Open full size
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.
Attachments Open full size
Suggesting the option to use a query of accounts instead.
Attachments Open full size
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.
Attachments Open full size
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.
Attachments Open full size
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.
Attachments Open full size