Defaults
When Logbook Pro imports your schedule it likely does not have aircraft specific information as it's typically not available in trip data. Therefore defaults need to be set which will be used when importing the trips from your personal cloud storage athttp://nc-software.com/schedule. Select the A/C Type to use when importing trips, you can change this value when editing the flight when actually flown. The Aircraft Ident can also be preset or left blank for later entry. Some users like to enter the N-Number prefix (or the prefix for your aircraft) and then you can just add the remaining part of the Ident when flown.
Preferences
Use Recent Recall: If set to ON and Logbook Pro has stored your last used Aircraft Type and Ident from the last entered flight it will use these values instead of the Default A/C Type and Ident. If recent Type/Ident are not available the schedule importer will fall back to your defaults if the trip data does not contain the type or ident information.
AutoFill: AutoFill can be used when importing the flight information from your cloud storage. As AutoFill will not update any field that has a value, it is recommended to leave this OFF and then when you enter the flight duration when actually flown AutoFill will trigger at that time. AutoFill during schedule importing is mainly for pilots importing flights from the past, i.e. already flown and will not be modified.
Auto Night: For imported flights already flown (in the past) night can be auto calculated.
Don't Enter Duration: If set to ON the schedule importer will leave the Duration field blank. This may be useful if you don't want future flights incorporated in your reports if sync pending is ON (Settings/Synchronization) and also so that the calc button will be available after you update the OOOI times to the actual values. Otherwise after entering actual OOOI times you would have to clear the duration (red X) and then tap the Calc button to recalculate the duration value.
Don't Enter Type/Tail: If set to ON the schedule importer will leave the type and tail fields blank. This may be useful if your company schedule data has no type or tail data, or if the tail has a tendency to change between when you import it and when the flight takes place and will force you to enter it manually each time to avoid errors.
Add to Calendar can be optioned ON to automatically add the flight into your device's calendar (requires Calendar Integration ON (Settings/Calendar)).
Include Deadhead: If ON and collation is By Leg deadhead flights will be imported. This is mainly for putting deadhead flights on your calendar but they will appear in your flight log as well should you need to edit and update the information. An aircraft type "Deadhead" will be used and no Ident entered to make the deadhead more distinguishable in your calendar. If you want to import this information into Logbook Pro Desktop you must uncheck the auto-purge option (bottom checkbox) in Options/Flight Log (in Logbook Pro Desktop).
Collation can be "By Leg" or "By Day" which will retrieve information from the cloud either in a fix-fix (By Leg) format, or a By Day for the entire day in a single flight log entry.
Field Map
When importing trip data you can map the available trip fields to custom text fields created in Logbook Pro Desktop's Options/Custom (TEXT) area or choose to append the information into the remarks. Tap the > button on the right edge to choose the field assignment. Options are "Do Nothing", "Append in Remarks", or select a custom text field as the target.
Remarks Template
For Fields in the Field Map section set to "Append in Remarks" you can control the order of data in the remarks using the Remarks Template system. Each field has a variable such as "Flight Number" is represented by the "fno" variable. You can then order the variables as desired as shown in the Figure above. Variables that are not assigned, i.e. not mapped with Append in Remarks will be automatically removed for you.