No more exporting Environment Variable Values
Next month, the default experience will no longer export environment variable values in your solution.
This makes it easier to follow best practices and avoid inadvertent mistakes.
A new “Export value” toggle within the environment variable settings will allow you to opt-in to exporting the value, if needed.
I never understood why a solution export would also export the Environment Variable values, but glad it is going to be solved.
Power Platform Advisor
Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.
Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).
Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.
Services:
– Strategy and tactics advise
– Automating and integrating
A daily newsletter on automation and eliminating friction
FluentAssertions v8 is now paid software Free: Assert.True(result); $130 per developer: result.Should().BeTrue(); 😱 dotnet
Progressive Enhancement for JS is overrated. In today’s web, HTML + CSS + JS is a package deal. Almost every browser supports the trio, and let’s be real: users expect apps to work smoothly with JavaScript. 95%+ of users have JS enabled – why build for the exception?...
Alpine.js just clicked. 🎯 Its declarative syntax—attributes on HTML tags—is perfect for simple UI logic. Most of the time, I don’t even need to touch JavaScript. And when I do? I can write just a little bit, and it fits right in. What’s even better? The declarative...