We are just asking for parity with database view. This is a step backward and is one of the things that frustrates a lot of customers about moving to webview. For some, the gift batch numbering system is not that important. For others it is critical and they cannot use webview because of it.
Please enable this soon so customers can fully use webview gift batches in preparation for the retirement of database view.
Having GFT in front of batch numbers isn't at all useful and throws off our finance team. We want to continue the same numbering structure as in database view!
GFT in the batch number and the ability of omatic cloud to not be able to create a batch that is auto numbered by REnXT is really crazy. Having so many different type of batch numbers has really thrown our finance team off with recon.
We use this capability in Database View, so we need it in Web View. The same can be said for every capability in the entire RE application across the board.
We keep batch numbers consistent across our GL and our bank. Due to limitations of one of them, we cannot have letters or special characters. We also need the first two numbers to be specific. It's critical we have the option to set what the batch numbers will be without manual tracking.
Yes, we can't have '-' in our batches as it messes up when imported into our GL system. We need the same batch numbering abilities as we have in DBV being able to chose the start number and have it count up from there.
yes, I would be great to be able to use our own batch number order, not Eg "GFT-2025-52". It's far too long and the year has no relevance to the batch transactions. We are only using 4-digit numbers in DB
Please offer us the same options that we have in database view for determining the batch numbering system in web view. Also, it's very confusing to have a GFT-2025-1 batch in web view and a 2025-1 batch in database view. Give us the option to use the same numbering system in both views and a set of separate options for each to distinguish them more.
When the time comes that we make the switch to NXT gift entry it would be nice to be able to continue to use the batch numbering system we currently are using because having to change it creates more work for others to match your system and ensure it speaks correctly with our finance systems. It would be nice if that option is available in NXT business rules when they get released. And if not, then it would be nice if we could set what the last number to start with and be able to continue that the following year as Glenn noted above.
Looking for at least what we have in DB view. The "numbering" system we are forced to use doesn't work well with our systems.
We are just asking for parity with database view. This is a step backward and is one of the things that frustrates a lot of customers about moving to webview. For some, the gift batch numbering system is not that important. For others it is critical and they cannot use webview because of it.
Please enable this soon so customers can fully use webview gift batches in preparation for the retirement of database view.
Having GFT in front of batch numbers isn't at all useful and throws off our finance team. We want to continue the same numbering structure as in database view!
GFT in the batch number and the ability of omatic cloud to not be able to create a batch that is auto numbered by REnXT is really crazy. Having so many different type of batch numbers has really thrown our finance team off with recon.
We use this capability in Database View, so we need it in Web View. The same can be said for every capability in the entire RE application across the board.
We keep batch numbers consistent across our GL and our bank. Due to limitations of one of them, we cannot have letters or special characters. We also need the first two numbers to be specific. It's critical we have the option to set what the batch numbers will be without manual tracking.
Yes, we can't have '-' in our batches as it messes up when imported into our GL system. We need the same batch numbering abilities as we have in DBV being able to chose the start number and have it count up from there.
yes, I would be great to be able to use our own batch number order, not Eg "GFT-2025-52". It's far too long and the year has no relevance to the batch transactions. We are only using 4-digit numbers in DB
Please offer us the same options that we have in database view for determining the batch numbering system in web view. Also, it's very confusing to have a GFT-2025-1 batch in web view and a 2025-1 batch in database view. Give us the option to use the same numbering system in both views and a set of separate options for each to distinguish them more.
When the time comes that we make the switch to NXT gift entry it would be nice to be able to continue to use the batch numbering system we currently are using because having to change it creates more work for others to match your system and ensure it speaks correctly with our finance systems. It would be nice if that option is available in NXT business rules when they get released. And if not, then it would be nice if we could set what the last number to start with and be able to continue that the following year as Glenn noted above.
Or I would be interested in having the number continuous eg. last batch in 2024 be GFT-2024-30001 then the first batch in 2025 be GFT-2025-30002