• NC Software is having a Black Friday Sale Event thru December 4th on Logbook Pro, APDL - Airline Pilot Logbook, Cirrus Elite Binders, and more. Use coupon code BF2020 at checkout to redeem 15% off your purchase. Click here to shop now.
  • Logbook Pro for Apple iOS version 8.0 is now available on the App Store. Major update including signature endorsements and dark/light theme support. Click here to install now.
  • NC Software is proud to announce the release of APDL - Airline Pilot Logbook version 10.0. Click here to view APDL on the Apple App store and install now.

APDL.net Data Export Issue

Lude2Envy

Member
Joined
Jan 23, 2017
Messages
9
I finished a trip on Saturday that ran through the interface period - Nov 29 to Dec 2. I'm trying to just export the data through Nov 30th on APDL.net, but when I choose "Get Flights" it's pulling up the flights from Dec 1st as well. I have it set to "Custom Date Range" from 11/29/2017 to 11/30/17. Why is it pulling flights from Dec 1st also?
 

Neal Culiner

Founder, President
Staff member
Joined
Nov 14, 2001
Messages
12,665
Location
VA
What are the dates of the last leg (actual IN/OUT) and in the same time zone as you're using on the exporter (DOM vs. UTC). I'd have to check the code but most likely it's where your OUT/IN are on that last flight.
 

Lude2Envy

Member
Joined
Jan 23, 2017
Messages
9
What are the dates of the last leg (actual IN/OUT) and in the same time zone as you're using on the exporter (DOM vs. UTC). I'd have to check the code but most likely it's where your OUT/IN are on that last flight.

The last leg on Nov 30th was out at 2045 and in at 2145 - both EST. I'm using Domicile, not UTC on the exporter.
 

Neal Culiner

Founder, President
Staff member
Joined
Nov 14, 2001
Messages
12,665
Location
VA
FYI, I just tried again changing the date range from 11/29/2017 to 11/29/2017 and that time it pulled just my legs from the 29th and 30th. Doesn't make any sense though.

Don't try to make sense of it, that's my job :) It's a time zone issue and I have to trace it. Will look at it tomorrow morning.
 

Lude2Envy

Member
Joined
Jan 23, 2017
Messages
9
Don't try to make sense of it, that's my job :) It's a time zone issue and I have to trace it. Will look at it tomorrow morning.

Haha, sorry. Here's a screenshot if it helps. The OOOI times are local, but the leg date still comes up as Dec 1st. I guess it's getting the leg date off of UTC time. Still doesn't explain why the search criteria doesn't work though.

Screenshot 2017-12-04 21.24.07.png
 

Neal Culiner

Founder, President
Staff member
Joined
Nov 14, 2001
Messages
12,665
Location
VA
This issue should now be fixed. Please give it a test drive.

There was a bug when using custom date ranges, the end date was incorrect.

Flight Date has been changed to reflect actual OUT and not scheduled OUT.

Thank you for the report.
 

Lude2Envy

Member
Joined
Jan 23, 2017
Messages
9
This issue should now be fixed. Please give it a test drive.

There was a bug when using custom date ranges, the end date was incorrect.

Flight Date has been changed to reflect actual OUT and not scheduled OUT.

Thank you for the report.

Looks much better. Nice work and thanks for the quick fix!
 
Top