Usually, it is the first place you will find out about critical bugs.

users have gotten used to see the errors that have occured during a job queue transaction run and now with the absence of it the users might think that NO errors occured.

Nice! 😉

Waiting for them to update: aka.ms/BCLastMinorUpdate

Running MSDO(s) on windows 😄

Another question related to that. Will the apps be forced upgraded when upgrading to major? If so we should warn customers that upgrading to major may affect their existing customizations => to costs

Top of my mind I don't think so.
Our customers are more like "Don't update it if it aint broke".
I would advise customers to not do that before they had tested/read about the updates.
If you have heavy customized base app then the probability that customer specific features will get broken.

Definitely! You at least broke ours 😉 Just glad that I couldn't sleep and was able to start 🧹 at 04:14 in our most active projects before the others started working.
Those LC0051 and LC0075 are really valuable!

What a bug fix! 🌊🌊🌊
Suddenly a lot of warnings that I thought was under control now showed up and told me it wasnt! 😬
Time to fix the breaking pipelines 🧹
Still, good work though!

😭

That's an fairly easy thing to do! 😊

Still on app source though.
appsource.microsoft.com/en-us/produc...

I thought of Data Braider (sparebrained.com/appsource/da...) as well but as Vyska announced yesterday I don't know how available it is at the moment.

I agree with @matnav.co.uk , I hope this will be the turning point and that there will be a way better 2025!

Row count for [CompanyName$Sales Invoice Line$y$VSIFT$Key9] is 409521 and rowcount for Sales Invoice Header is 240609

My first thought as well, but then I tried to find it "written". Could it find it within a couple of minutes and gave up.