eFlightLog exports flights via SOAP API into BlueEye (MRX Maintenance Systems).
The administrator of your BlueEye system must first create a user account with read/write access for eFlightLog. The login (database name \ user name) and password are stored in a hidden settings file on your eFlightLog domain – contact your eFlightLog support for this.
In Backend, choose MRX-Export from the menus on the left. All FlightLogs not yet exported will be listed in a table.
Choose an aircraft from the dropdown list or enter a date range to filter the results displayed. Check ’show exported Flights‘ to display all flights. Here you can make a last plausibility check before exporting.
Once exported to BlueEye, all data in the FlightLog concerning flight time, block time or cycles is locked for editing.
Even though every single flight leg is listed, ‚Export‘ and ‚Block‘ always apply to all flights in a single FlightLog.
Click ‚Export‚ to create a Techlog entry in BlueEye with the flights in the FlightLog. On successful Export, the BlueEye Techlog-ID is written to the FlightLog, marking it as ‚exported‘. Make sure you proceed chronologically, exporting oldest FlightLog first.
If a FlightLog listed for export has already been recorded manually in BlueEye, click on ‚Block‚ to prevent export and remove the FlightLog from the list to be exported (setting FlightLog idTechlog to -1).
The ‚Reset‚ button appears if a FlightLog has been exported or blocked, and releases an exported or blocked FlightLog to be exported anew. Editing the FlightLog is now possible.
Important: If you re-release a FlightLog for export, be sure to delete the corresponding Techlog in BlueEye before repeating the export!