We've all been there. You need a simple Rule or a Data Request for a common table. You have that nagging feeling that "surely someone has done this already," but digging through hundreds of objects, checking old projects, or asking around takes longer than just building it yourself.
The result? You end up creating duplicate object number 50. Your system gets cluttered, maintenance becomes a nightmare, and you lose valuable time.
Usually, this is the part where I tell you how I locked myself away for a weekend to code a solution in Groovy. But today is different. Today, I want to celebrate the power of community.
Browsing through JDE List, I came across a tool shared by user JohnDanter2. He understood this frustration perfectly and, instead of complaining, he built a brilliant solution that he was generous enough to share.
It’s not just a search bar; it’s an Orchestrator that audits your Orchestrators.
Essentially, this tool takes a keyword and scans all your User Defined Objects (UDOs). It doesn’t just tell you if it exists; it gives you the full context.
Imagine typing "Address Book" or a UDC code and instantly getting:
✅ The internal name and description of the object.
✅ Which project (OMW) it is "hiding" in.
✅ If there is any active Orchestrator currently using it.
It is a pragmatic tool to prevent duplication and keep your development hygiene in check.
Why should you try it?
Time Saver: Find reusable components in seconds.
Cleanliness: Stop creating the fifth version of the same Data Request.
Visibility: Understand the dependencies between your objects and projects.
Huge thanks to JohnDanter2 for allowing me to share this with everyone. The true spirit of JDE is sharing knowledge.
👉 You can download the tool directly here
Now I ask you: Is there any tool, trick, or "home-brewed" development you use to make life easier that you think the community should know about? Or even better, do you have a crazy idea we could try to build together?
I’d love to read your thoughts in the comments! 👇
