<?xml version="1.0"?>
<ArrayOfFBEvent xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-01-02T16:21:00Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-12T16:12:55Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment> Verified With datapro versions 4.0.1070.49712,4.1.468.49713 and 4.2.182.49714   test setup with multiple roi's and a sensor that has been deleted can be opened and edited after migration from  4.0.729 version  .
</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2023-10-12T16:11:47Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-10-12T15:29:15Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>49703 is 4.0; 49704 is 4.1; 49705 is 4.2.
To test:
After migrating successfully in previous test, ensure that Test Setup can be opened for editing without crashing.</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-10-11T17:56:37Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-11T17:52:24Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-10-06T18:33:40Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>When migrating from eco released dp version 4 0 729  with a test setup with multiple roi and a deleted sensor i get an crash  attempting to open the test setup and datapro is forced to close .

I attached my test setup ..

Steps To reproduce ..

1. Create test setup in datapro 4.0.729   with multiple roi 
I added 3 ROI 's  
2. Assign sensors to channels and to the ROI 's
3. Delete one of the sensors in the test from the sensor database tab .

4.  Close datapro and migrate by installing datapro  4.0.1052.49567

5. AFter Migration completes successfully  open test setup that has the deleted sensor , data pro crahses with message "datapro has experienced and issue and will now close".


2023-10-06 11:21:01.683 User Admin pressed PageButton:MainWindow_ConfirmLicenseHasExpired_OK
 
2023-10-06 11:21:01.684 User Admin pressed MainWindow_ConfirmLicenseHasExpired_OK
 
2023-10-06 11:21:54.289 User Admin pressed PageButton:MainWindow_ConfirmInvalidVersion_OK
 
2023-10-06 11:21:54.289 User Admin pressed MainWindow_ConfirmInvalidVersion_OK
 
2023-10-06 11:22:16.646 !!  An exception of type: System.InvalidOperationException occurred Module: System.Core.dll, Name: FirstMessage: Sequence contains no elements StackTrace:    at System.Linq.Enumerable.First[TSource](IEnumerable`1 source) StackTrace:    at DataPROWin7.DataModel.TestTemplate.AddHardwareToChannelsIfNeeded(IRegionOfInterest record, Int32 testSetupId)    at DataPROWin7.DataModel.TestTemplate.LoadRegionsOfInterestFromDb()    at DataPROWin7.DataModel.TestTemplate.LoadFromDb()    at DataPROWin7.DataModel.TestTemplate.Load(Boolean fromDB)    at DataPROWin7.DataModel.TestTemplateList.GetTemplate(String name, Boolean bLoad)    at DataPROWin7.TestSetupsPage.EditOrCopy(Boolean bCopying)    at DataPROWin7.TestSetupsPage.EditOrCopy(Boolean bCopying)    at DataPROWin7.TestSetupsPage.OnEditTestSetup(String name)    at Microsoft.Practices.Prism.Events.EventSubscription`1.InvokeAction(Action`1 action, TPayload argument)    at Microsoft.Practices.Prism.Events.EventSubscription`1.&lt;&gt;c__DisplayClass2.&lt;GetExecutionStrategy&gt;b__0(Object[] arguments)    at Microsoft.Practices.Prism.Events.EventBase.InternalPublish(Object[] arguments)    at Microsoft.Practices.Prism.Events.CompositePresentationEvent`1.Publish(TPayload payload)    at TestSetupsList.TestSetupsListViewModel.MouseDoubleClick(Int32 index)    at TestSetupsList.TestSetupsListView.MouseDoubleClick(Object sender, MouseButtonEventArgs e)    at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)    at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)    at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)    at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)    at System.Windows.Controls.Control.HandleDoubleClick(Object sender, MouseButtonEventArgs e)    at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)    at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)    at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)    at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)    at System.Windows.UIElement.OnMouseDownThunk(Object sender, MouseButtonEventArgs e)    at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)    at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)    at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)    at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)    at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)    at System.Windows.Input.InputManager.ProcessStagingArea()    at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)    at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)    at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)    at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean&amp; handled)    at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean&amp; handled)    at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean&amp; handled)    at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)    at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)    at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
 
2023-10-06 11:22:16.652 DataPRO has experienced an issue.  The issue has been recorded.  DataPRO will now shutdown for safety.
 
2023-10-06 11:22:31.585 User Admin pressed OK
 
2023-10-06 11:22:31.598 ModalWindow: Are you sure you want to close DataPRO? Press Yes to close or No to continue. 
 
2023-10-06 11:22:31.613 DataPRO Closing ==========================
 
2023-10-06 11:22:31.614 DataPRO Closed ===========================</Comment>
    <StatusString>Reactivated</StatusString>
    <TimeStamp>2023-10-06T18:31:34Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Reactivated</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-10-04T18:08:17Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2023-09-12T17:28:56Z</TimeStamp>
    <ReleaseNote>Addresses an issue with migrated test setups with multiple ROIs</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-09-12T17:28:35Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>49544 is 4.0; 49545 is 4.1; 49546 is 4.2.

To test: 

1) Create a Test Setup with multiple ROIs, but with a sensor that has been deleted, in a database that will require migration.

2) Install a later version of DataPRO which migrates the database with the missing sensor, and ensure that the migration finishes successfully.</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2023-09-06T21:31:05Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-09-06T21:28:27Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2023-09-06T21:12:23Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Opened</StatusString>
    <TimeStamp>2023-09-06T21:12:22Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>