Dataflows should verify using actual library variables

surpriseturtle  would you mind creating a new thread in the community forum with more details around your scenario? would love to learn more about how you have it setup and where things might have not been yielding the result that you were expecting with Variable.ValueOrDefault

the ValueOrDefault is definitely the recommendation for most scenarios given that you can copy / paste this M code into other products and it'll continue to work without you having to modify your script. The Variable.Value only functions with the right identifiers in the Dataflow Gen2 CICD context, so it always forces things to correctly evaluate or it'll throw an error, which would be the easiest approach for you in really nuance cases where a Default might not be the right approach