SysTestFlightingManager is used specifically for tests only. It lets developers enable or disable flights temporarily during automated test runs, without affecting actual feature settings.
On the other hand, the Flight class controls real feature rollout in production and preview environments, using lifecycle stages, flights, and kill switches.
To disable a feature, you either turn off its flight or activate its kill switch, which forces it off even if it was on by default.
therefore, first thing
1) Flight (X++ class) = real feature control
2) SysTestFlightingManager (X++) = temporary control for test scenarios
Not all the time you would have record in the table SYSFLIGHTING (which you can manipulate).
If you look at the Microsoft DLL (which is behind the whole logic of Flight class), here is the matrix/table you will end up with, that shows not all the time features are controlled by Flight, sometimes those are on by Default.
| Stage |
Description |
Available To |
Enabled By |
Can Be Disabled By |
| Incomplete |
Microsoft internal only |
Microsoft dev/test environments |
Internal environment + Flight |
No Logic |
| PrivatePreview |
Opt-in preview users |
Microsoft + selected customers |
Flight |
Kill switch |
| PublicPreview |
Public rollout (default on) |
All customers |
Default |
Kill switch |
| Released |
Fully released feature |
All customers |
Default |
Kill switch |
Please note that above table may not be perfect with all details/scenarios, I have tried my best to make it, after reading code in the DLL (Microsoft.Dynamics.ApplicationPlatform.FeatureExposure)
For your case, your feature is on by default using a calls named DisableDefaultFilterForSysDataBaseLogFlight
This class DisableDefaultFilterForSysDataBaseLogFlight is a subclass of an Interface(another X++ class) named Flight.
You can try two things from here:
1) try to disable the feature using the class DisableDefaultFilterForSysDataBaseLogFlight (Which it would NOT allow you because it is an internal object for that model and you cannot extend it in your model). So that option is no more available for you.
2) Contact Microsoft with a support call, and explain them why you do not want this feature on with the business Impact.
Microsoft's DLL logic behind the Flight class [Microsoft.Dynamics.ApplicationPlatform.FeatureExposure]
