This forum is obsolete

This support forum has been replaced by a news version. You can browse old posts in this forum, but please post your questions to the new forum by clicking on "Support" in the top level menu.

Support Forum
Subject: Interesting issue that has happened twice so far
Prev Next
You are not authorized to post a reply.

Author Messages
dblackmon
Posts:55
Golden Member

04/07/2016 7:59 AM  
I noticed a couple of version back from the latest version that some of our event booking data had been erased from the table FlexBooking. At first I though this was an issue that was resolved with the latest version. However after having to erase the module and re install on a fresh install of DNN the same issue has happened again after being live for a few weeks. Originally I though it was removing attendees from events that have past as a house cleaning procedure, however this is not the case.

Bookings are being deleted from the FlexBooking table that have not happened yet. This makes it difficult for our Office Managers to have a way to cross check and verify attendees. They are having to save the Automated emails that are sent when a person books an event. This is the only check and balance they have.

Looking at the ItemID column it goes from 1,4,8,14,17,21,22,23,26,28,29,30,31,32,33, so as you can see bookings are missing due to the numbering order. We had planed on using the data to gauge the success of events to better market our classes. Currently this is not possible because data is being purge at a unknown time.

My question is was this by design, or is it a function that my not be preforming correctly that needs to be address. If it is by design is this something I can disable. We want to collect this data for future reference becasue its important information.

Thank you,

Doug
Pengtsen R
Posts:13551


04/17/2016 7:40 PM  
There are only two ways to delete a booking record in flex events:

1, you can manually delete a booking record when you view it. There is a delete button.
2, when an event is deleted, unpaid booking records are deleted. Paid records will not be deleted.

Actually, if there is paid records. The corresponding event can no longer be deleted(because the paid records cannot be deleted in first place).

So, do you think if these missing records comes from when flex events delete an event?

Pengtsen R
http://www.bizmodules.net
dblackmon
Posts:55
Golden Member

04/17/2016 8:09 PM  
Well we don't delete bookings at all and like I said active events were removed along with payment information. This is what concerns me becasue the only way to verify the information is from the conformation emails that were sent.
dblackmon
Posts:55
Golden Member

04/22/2016 11:24 AM  
So in follow up on this, I confirmed with one of our Office Mangers that indeed some Paid records and UnPaid records were removed by the system.

I will reiterate that we don't manually delete any bookings, Concerning Events I will mark them pending so they will not show up in the list if the class doesn't make a minimum of attendees.

I am not sure which stored procedure is the one you use within the DNN Scheduler that will purge stuff. However looking at some of the stored procedures I see that

FlexEventDelete shows where it will delete an event with a Payment Status of 1.

/****** Object: Procedure [DotNetNuke].[FlexEventDelete] Script Date: 4/22/2016 11:07:20 AM ******/
USE [DNN_DATA]
GO
SET ANSI_NULLS ON;
GO
SET QUOTED_IDENTIFIER ON;
GO
CREATE PROCEDURE DotNetNuke.FlexEventDelete
@ItemId Int
AS

DELETE FROM DotNetNuke.FlexBooking
WHERE
PaymentStatus = 1

DELETE FROM DotNetNuke.FlexEvent
WHERE
ItemId = @ItemId
GO

FlexBookingDelete shows where it will delete a booking if the payment status is 3

USE [ATN_DATA]
GO
SET ANSI_NULLS ON;
GO
SET QUOTED_IDENTIFIER ON;
GO
CREATE PROCEDURE DotNetNuke.FlexBookingDelete
@ItemId int

AS

DECLARE @OccuranceId int, @PaymentStatus int
Select @OccuranceId = OccuranceId, @PaymentStatus = PaymentStatus from DotNetNuke.FlexBooking Where ItemId=@ItemId

DELETE FROM DotNetNuke.FlexBooking
WHERE
DotNetNuke.FlexBooking.ItemId = @ItemId

If @PaymentStatus = 3
BEGIN
Declare @ConfirmedBookings int, @ConfirmedAttendees int
Select @ConfirmedBookings = count(ItemId), @ConfirmedAttendees = sum(Attendees) from DotNetNuke.FlexBooking Where OccuranceId = @OccuranceId And PaymentStatus = @PaymentStatus
UPDATE DotNetNuke.FlexOccurance SET ConfirmedBookings = @ConfirmedBookings, ConfirmedAttendees = @ConfirmedAttendees Where ItemId = @OccuranceId
END
GO


Am I looking in the wrong place or is this one of the procedure that are ran every hour.

In addition we use the "Manual Pay" as a means to request a PO from the clients and have to use the "Addition Notes" field to collect this information because the module doesn't contain any extra fields to collect this information.

How can I prevent the module from purging booking data when someone selects "Manual Pay". Because in reality a "Manual Pay with a supplied PO Number really means that had committed to Pay. I do not want our office managers using the "Manage Bookings" feature within the module becasue it will create additional training and confusion.

Anyway I need to figure out a solution or a work around to continue moving forward.
Pengtsen R
Posts:13551


04/24/2016 11:50 PM  
I sent you an email asking for further details.

Pengtsen R
http://www.bizmodules.net
You are not authorized to post a reply.
Forums > Flex Events > Support Questions > Interesting issue that has happened twice so far

Copyright © 2005-2013 BizModules Contact us