nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Duplicated Web view batch numbers

JoAnn Strommen

Am waiting for chat but wondering if anyone else has encountered this issue. We are running an event registration through NXT (reconsidering if it was best option due to all the duplicates created). But today when I should be on batch XXX-56, I have batches XXX-39 through XXX-43 from the weekend. These would have been created weeks ago. IMO there should never be duplicate batch #s. We did move the registrations to another batch and delete batches but if #s are going to be reused it shouldn't have started with 39.

Anyone else seen this?

Find more posts tagged with

Comments

Elaine Tucker

This may be an internal setting somewhere, and if you deleted the batches NXT may not have a way of updating. This doesn't sound like a good thing; RENXT should recognize batch numbers that have been used in the past.

JoAnn Strommen

I've not found any where in NXT to set batch #s like users can in db view. We have previously deleted event batches and not had batch #s reused. Don't know what is going on. Yes, definitely not a good thing. Would certainly mess up tracking/query by batch.

Have been trying to connect with support on chat but the connection keeps getting lost. Am hoping for a support person who can read the case and respond without my having to explain it all again.

Shane Littleton

Hey JoAnn Strommen‍, I have not used the NXT Event module, but in the database view, you can edit the Batch options (Configuration > Business Rules > Batch Options), to change what number that the batch generation will start from. For example, you could change it from XXX-44 to XXX-56.

I'm not sure if those rules cross over with the web-view, but they might! It may be worth even checking what is listed as the next available batch number in the business rules in the database view.

JoAnn Strommen

The db view receipts are a separate function from the web view and/or e-receipt numbers. Our db receipt #s are in the hundreds or thousands.

As I said, I've not found any where I can specify # for web view receipt #s. Still waiting to hear back from support. Connection lost multiple times yesterday. Had 3 or 4 different support staff each time I reconnected even using the case #.

Thanks anyway, Shane Littleton‍

JoAnn Strommen

Sorry, replace 'receipt' with 'batch'. Had my mind on something else. ?‍♀️

JoAnn Strommen

Just finished another session with support. Summary from my perspective: users have no control over web view batch numbers. Batch numbers may be reused by system. What # is reused may/may not be related to anything else. If I don't want to reuse batch #, I need to manually edit batch # in web view.

This is another significant glitch with RE NXT. So disappointing that it happens and with support today.

I just created a suggestion in idea bank: RENXT-I-4285 For what it's worth please vote.

Jeannie Goings

Absolutely crazy making! Voted. Thank you for adding to idea bank.

JoAnn Strommen

Have an email from a senior analyst today stating "We are double-checking with our developers if there was a recent change to be working as intended or if this is an issue we will need to resolve."

Today's registrations created our 8th duplicate web batch #. ?

Glad to hear to hear they are looking at it!

JoAnn Strommen

Had been going along smoothly with batch #s proceeding in sequence - created duplicate batch #s all the way through. Yesterday was on NXT batch 2021*65. Today it's back to batch 2021*53. That makes 3 NXT batches with the same batch #!

Updated case with support - still waiting for answers. Has anyone else experienced this?

I did create suggestion to 'not allow duplicate batch #s' - idea bank: RENXT-I-4285. Appreciate the vote.

Marguerite Gravois

Is nothing sacred?? I feel your pain--voted. Carry on!

JoAnn Strommen

Our reunion event where we were having daily batches is over. So don't anticipate having the issue again. Support is still looking into why this happened.

If it happens for you, please create a case. At times support had me wait to do anything to batch so they could analyze from backend. Am guessing more examples of it occurring would be helpful to resolve.