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
Much ado about nothing
There is really nothing special with this post. I just wanted to let you know…
Look and feel update
I decided to upgrade the look and feel of this blog, so I start with…
Why are "mandatory" fields baaad?
Last time, I gave you a recipe on how to do a bad thing. If you really need to do something bad, I figure it's better to do it the way that would hurt the least, or the way that isn't so bad after all. I wouldn't have dreamt of a comment on that blog post, but Ian came, and gave the perfect example which really explains why things like that *ARE* bad. Funny thing is, how many customers really go for such a requirement, and even funnier, how many consultancies give in. I gave in once, most of you probably did. But, why are mandatory fields so bad after all?
- Go to the previous page
- 1
- …
- 151
- 152
- 153
- 154
- 155
- 156
- 157
- …
- 163
- Go to the next page
