I agree with all these points.
legally, one is required to keep account numbers. However, the main coders for ERPNext are currently overwhelmed with work, and there is a big effort to prioritize the requirements that all of us are asking.
I have spoken personally with several coders such as @nabinhait and @rmehta and @umair during ERPNext conference 2017 and it is clearly evident that despite their most extreme best efforts, they simply do not have enough time and resources to cater to our every whim. It’s just humanly impossible! The stress is evident. They MUST focus their work on serving their current customers well. They need to put food on the table. There is a big effort to prioritize the requirements that all of us are asking.
Simply put: We can “sit tight and wait” or “Contribute ourselves.”
Consequences of each:
Sit tight and wait
- You have no control over when this feature will effectively work
- You cannot effectively contribute much to this feature
- You have a greater degree of control over when this feature will work.
- There is also flexibility into what contributing means: You can propose ideas in this forum or GitHub (Which do not guarantee the feature will make it) or you can go all the way to coding yourself the actual feature on your ERPNext develop fork, and then make a pull request. You can still program a perfect feature, and yet, it can still be rejected for core integration. So, you still have one more option: Your self-coded masterpiece, can be implemented as an App, which you publish on GitHub and document how to install it onto ERPNext. At least you now have control over your own ERPNext implementation, can then decide to contribute the code to the community or not. If enough users demand it be merged to core after having several successful real life test cases, then your contribution has accomplished one of the maximum contributions possible. Sure, great documentation, multilingual in the best case, and even video tutorials, with good subtitles and multilingual tracks, will have made your feature one of the best contributions possible.
It is just a matter of doing this:
- Add the field to the account DocType.
- Create a separate report that displays the “newly specified” account_number field as a Ledger view. Or modify the existing one to do so, but you run the risk that with each successful ERPNext update, the feature will break (although the existing data will not)
One could manually add the field, start registering the data, and when ERPNext pulls it and implements it out of box, it is just a matter of migrating to the new field name.