AL Object ID Ninja
Zero-configuration, dead-simple, lightning fast, no-collision object ID assignment for multi-user repositories
- No collisions, ever: Real-time, conflict-free ID assignment that always gives every developer a guaranteed unique object ID.
- Lightning-fast: Get your conflict-free object IDs instantly, with IntelliSense integration.
- Zero-configuration: No setup, no onboarding, no settings — you work exactly like before, and it silently keeps your IDs clean.
From the blog
A Tribute To A Friend
This post has no category. It may be irrelevant to you; it won't provide any value to you or your business.
But to me, personally, it's the most relevant so far.
“Our old software” syndrome
A few days back, while prototyping a new solution for a customer, one of the key users said: "But in our old software it didn't work like that." I was about to try to explain why the change, but then the user's boss said:
- We aren't implementing a new solution so that everything can stay the way it was.
How often does it happen to you that your customers say to you a similar thing: "But in our old system..."? What do you say to them? How do you approach change when your consultant proposes a new way of doing things, or a new approach to a common problem?
Serial Numbers Conundrum
A blog reader has asked me for help about an allegedly strange behavior of items with serial number tracking. They had a customer who had serial number tracking switched on for an item with FIFO costing method. Whenever they posted a sales transaction, they chose the serial number manually. Then they noticed a puzzling behavior.
No matter the specification of the serial number on the sales lines, Microsoft Dynamics NAV seemed to be closing the item entries according to FIFO method. This effectively allowed a serial number to be sold twice (or more). They called for help.
- Go to the previous page
- 1
- …
- 141
- 142
- 143
- 144
- 145
- 146
- 147
- …
- 163
- Go to the next page
