Flights are used to disable new features which will change the user experience. With this concept we are able to explicitly enable new features and not by default.
Scenario:
With the PU 34 update, MS introduced fights to Journal printing. So the new code is called as flight is disabled by default.
X++ :
Scenario:
With the PU 34 update, MS introduced fights to Journal printing. So the new code is called as flight is disabled by default.
As the flight is not enabled, it will go to else part in the code shown in pic.
To enable flight to it, write the below script:
SQL:
INSERT INTO SYSFLIGHTING (FLIGHTNAME, ENABLED, FLIGHTSERVICEID) VALUES ('LedgerJournal_UseOldLegerJournalDPReport', 1, 12719367)
or
X++ :
if (!SysTestFlightingManager::isFlightEnabled("LedgerJournal_UseOldLegerJournalDPReport"))
{
SysTestFlightingManager::setFlightEnabled("LedgerJournal_UseOldLegerJournalDPReport", DefaultNoYes::Yes);
Info("Flight enabled");
}
{
SysTestFlightingManager::setFlightEnabled("LedgerJournal_UseOldLegerJournalDPReport", DefaultNoYes::Yes);
Info("Flight enabled");
}
Reference: