Initial value of Feature Flag

@Zoltan Febert 

I also just solved it with a customizationPlugin. It’s way better than an SQL script, because it only effects the current tenant and also works with new tenants.

    public class MyCustomizationPlugin : CustomizationPlugin
    {

        //This method executed after customization was published and website was restarted.  
        public override void UpdateDatabase()
        {
            this.WriteLog("MyCustomization Update Event");
            FeaturesMaint featuresMaint = PXGraph.CreateInstance<FeaturesMaint>();        

            Update<FeaturesSet>.
                Set<FeaturesSetExt.usrMyFeature.EqualTo<False>>.
                Where<FeaturesSetExt.usrMyFeature.IsNull>
            .Update(featuresMaint);
        }
    }

Is there a reason you would only want to affect the current tenant? As long as you’re only setting the value if null, I don’t see an issue with setting it universally.

Also, I’ve never seen this before, and I’m psyched to learn it exists. PXDatabase.Update sucks.

Update<FeaturesSet>.
    Set<FeaturesSetExt.usrMyFeature.EqualTo<False>>.
    Where<FeaturesSetExt.usrMyFeature.IsNull>.
    Update(featuresMaint);

Edit: I see now that this is not a replacement for PXDatabase.Update, but it’s still cool.

An SQL script is executed once, when you publish the customization, after that never again.

So if you add another tenant, it will have NULL again and the SQL doesn’t execute anymore.

The CustomizationPlugin is executed everytime the Customization gets published.

Thus, it will be executed for every tenant as well.

Also, when you execute the SQL for all, it may also effect Snapshots.

True, but if you’re defaulting the value to false, this will take care of that, since the only reason the default isn’t working now is because the record already exists and isn’t calling the defaulting event. A new record would call the defaulting event, thereby setting the value to false.