Posted: July 2, 2020 at 5:59 am
Hi, |
|
I have prepared a pdf with screenshots to explain but don’t know how to get it to you. My email address is registrations@codingforsail.uk |
|
Hi Anita, To send screenshots/PDF’s you can use support[at]eventespresso.com. Or host the image and post the links here on the forums to view: https://eventespresso.com/wiki/troubleshooting-checklist/#screenshots You can also mark your reply containing those private so only EE support can view them. |
|
Hi Tony, |
|
Hi Anita, My apologies for the delay, I had to do some digging to find out what was happening here and if there is a workaround for it. So the sections that are displaying the amended details all pull the details from event/related objects themselves but line items section is pulling the details directly from the line items themselves. So to fix that specific output would require the line items themselves are updated, however, currently EE doesn’t expect a date change to be done within the ticket itself and rather the datetimes assigned to that ticket so we don’t have a method to update those line items within a transaction at this time. I can likely write a snippet that will update the line items on a specific transaction but note that will only help on a single transaction at a time, so you’d need to open each transaction linked to the registrations showing the above and click a button to update its line items (there’s one already but it’s for the taxes/total, not names/descriptions). |
|
Hi Tony, |
|
Just a thought – could I modify the report to pull the line item details from the data that has been amended instead of from the original line items? |
|
In short, don’t use the date in the ticket names/descriptions. The datetime is intended as the ‘instance’ of the event and the ticket gives access to a datetime(s) so for a day change you would change the Datime and the Tickets themselves remain the same. However, I looked over your events and saw the setup so I understand it’s easy to say the above and not always so easy to implement. No links have been posted to the site here so I wont link directly, but as an example Event ID 1566 has a single datetime spanning across 2 days. Then I assume there were 2 tickets, one for the first day and one for the other and the day is in the ticket to help differentiate. Would it not work to have 2 datetimes there and set a datetime name that shows help split them up, then have Ticket A assigned to datetime 1 and Ticket B assigned to Datetime 2? You could been then have Ticket 3 assigned to both if needed.
Sure, but you’ll need custom message shortcodes to do that and its still more of a workaround as if anywhere else uses the line-items they would then still show the ‘wrong’ value. |
|
Yes, there are indeed two tickets, one for each day.
I asked the client this. She says she uses the date in the ticket name field to allow her to distinguish between bookings on the transaction screen. If it were set up with 2 datetimes and a ticket for each, would she still be able to see separate transaction items? (It’s a live system and I haven’t got a dev instance I can play with at the moment.) |
|
September 28, 2020 at 12:42 pm I’m sorry but I don’t follow the above, which transaction screen for the event? Can you post a screenshot so I can see what you are referring to above? |
|
Hi Tony, I have attached screenshot in an email I just sent to your support address. Kind regards, Anita |
|
Ok, no, that transaction screen would not show the date by default, it would show something like this: https://monosnap.com/file/13YhURzqW3Pn28uQjPQZzbKHJ743h0 That’s from an event with 2 datetimes and a ticket on each datetime, then selecting 1 of each ticket. However, that section is filtered so is it just that specific section they need that info on? It should be possible to include additional datetime details there if needed. |
|
The support post ‘Invoice shows previous LINE_ITEM details against an updated EVENT_LIST’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.