38 🫣
38 🫣
This kinda feels like a money grab from Mercedes 😲
Are those whistles and bells you’re not going to mis or are we talking basic functionality you’re using on a daily basis?
You could try by filling out the form from @nataliekarolak.bsky.social post?
bsky.app/profile/nata...
“.. Tonight's the Night ..”
Goosebumps when hearing this 😁
Just to be sure; Resurrection is the sequel of New Blood otherwise the story line could be confusing 🫣
m.imdb.com/title/tt1416...
I’ve struggled through the first season, because I really wanted to give it a chance. Unfortunately it’s not for me 😟
…but the goods is that m.imdb.com/title/tt3304... is here 🤩
I’ve also used an extra Boolean field “value has been set”. Good to hear that I’m not the only one who solved it like this 🤗
Fun part when you need to register temperatures for example incoming goods. Zero degrees is a valid temperature and at the same time “no value registered”. That was fun 🙈
This is future-proof-code™ when AL introduces nullable variables 🤪
After your brilliant tip of The Day of the Jackal, what was for me on of the best series of 2025 so far, I’m absolutely going to add this one to the watch list 🤗
Thanks for sharing 🙋♂️
You’ve made it to the big screen 😅
Safe travels, see u in Antwerp 🙋♂️
That is actually a good idea! I’ll need to rethink my template app on that.
You’ve made a great point on the prefixing versus suffixing 💯
That would indeed be my suggestion. It feels a bit strange, as the platform version could be determined based on the application version, so it kinda feels like doing double administration.
This is a personal preference, where in the AppSourceCop.json file, I like to use the mandatoryAffixes instead of the mandatorySuffix property.
It comes down to the same and as you mentioned to use suffixes, not prefixes, but with the mandatoryAffixes it doesn't affect the choice between them.
PS The ISV was very helpful to resolve this with us and made the change on their side and now publishing their apps with the corresponding platform version 🤗
“..This can be left at 1.0.0.0 as the server version will always align with the application version..”
When working with NuGet packages and the BCCH, the “installedPlatform” parameter uses this and then downloads a wrong artifact.
We’ve run into this with an ISV app in our ADO pipelines
Fair point 😅 No idea why the NST needs more, I can only guess that when also the SQL instance is on the same machine that this would justify this.
Not sure why it changed, but 2GB seems insufficient? 🤔
Jep! Access to all tables and fields for reporting would be great. If also a DWH is needed then Fabric together with BC2ADSLE could be a fantastic solution. For a simple setup I’m quite the fan of the Open Source and Community solution of Data Braider appsource.microsoft.com/nl-be/produc...
I pitched the idea to @chovenbitzer.bsky.social, but we both agree on that it’s maybe not the best name for the rule. So we’re going a round here gathering ideas 🤗
In general, compared to other Dynamics 365 Apps on Dataverse, accessing data is cumbersome.
..and the workaround that I see mostly used is also sunsetting learn.microsoft.com/en-us/dynami...
This feels like a no-brainer, so you’ve got my vote 🙋🏻♂️
I feel like we’re reinventing the wheel here, one ISV at a time.
Wouldn’t it make sense for the AppSource platform to provide this? It reminds me of the days when submitting an app tonAppSource required uploading an actual test app.
What a view 🤩
I've started from the template by Tom Kapitan, which was of great help!
bccaptain.com.au/2023/09/09/u...
Don’t be like me and confuse DWY and DMY, where in DWY I believe the year now matches the weeknumber with this logic? 🤔
github.com/StefanMaron/...