## AL Object ID Ninja v1.2.0 – plus some Azure lessons learned

First things first. Yesterday evening, I’ve released AL Object ID Ninja v1.2.0 and there is really nothing new that you’d care about, functionally speaking. Check the changelog if you will, but trust me, you won’t be really blown away. But yes, unfortunately, it did merit a full minor version rather than just a patch number increase.

That’s it. If you only care about what’s new, then this is where you stop reading. But if you care to know what kind of a rocky ride I’ve had yesterday wrestling with Azure and fighting like mad to keep this service free, then read on.

I won this fight, by the way đ

(more…)

I had much second thought about whether I should even blog this one. You know, it so profoundly belongs in the Duh! category that I have actually created the Duh! category specifically for this post.

Now, fasten your seatbelt. I apologize for what you are about to see,  but apparently people do write code as the example below. And I sh*t you not, you canât really make this crap up, but this is what people do:

IF NOT Cust.ISEMPTY THEN
REPEAT
DoSomethingStupid(Cust);
UNTIL Cust.NEXT = 0;

Wat?

## When you just must COUNT, no matter what

I started with blogging about COUNT = 0 situation. Then I followed it with COUNT = 1. So, letâs do a COUNT = 2 today. No, no, I am just kidding, donât worry đ But I still have to do one more COUNT post, one that will cover all other COUNT situations.

Believe it or not, sometimes you really, honestly, do need to perform an actual COUNT. You just need to know exactly how many of rows there are. It may be 0, 1 or 75 or whatever, but you need to know exactly how many. These situations are few and far between, but every once in a long while this is what you need.

So, letâs give the COUNT function one last kick from another angle.

## The âIF COUNT = 1â Conundrum

If you havenât read my yesterdayâs post, then do that first.

Good. At this point you are extremely smart because you know that you should never use COUNT = 0 but should use ISEMPTY instead.

However, what if:

IF SomeTable.COUNT = 1 THEN
DoSomething();

Well, if this is what you need, then thatâs what you need. And thatâs exactly what we needed in the team a few days ago.