@kickapoo : could you please add some screenshots ,to see how it looks like.
@kickapoo Can you please share your github repo… Thanks…
@Basawaraj_Savalagi Hey, I dont have any repo to share the code but I have good news. I think for version 8 child table of child table will be possible from the core of erpnext.
That will merged after v8!
@rmehta any chance to get
child table of child table aka
grand child in v. 9?
I have this implemented here… https://github.com/rmehta/frappe/tree/grand-children
But don’t have a use-case yet!
@rmehta Maybe the alternative BOM Lines might be a use case
@rmehta i see …i’ve an use case for an application to build using frappe, would be possible to merge it in develop?
This is very useful if you have more details for Item master.
In Item Master, I have to specify which other items can replace the main item.
I put this info and list in a table called Alternate Items.
In any transaction, especially in Opportunity, I need to know if an item has Alternate Items and I have to show this table in Opportunity Item as a read-only field, for reference so that my purchaser will see which items can be purchased in replacement of main item.
I hope this can be considered a valid use-case.
Of course there are use cases, but who will build the alternative item feature?
Sorry, I’m not getting your point; is that a matter of who and how many people will use that feature to build erpnext features?
My point is that most people will use it in “custom apps”. That is no incentive for me to add that feature.
The quality and quantity of contribution is still very low. If you want features, you should start contributing first!!
@rmehta the people are not contributing, i think, because there is not a clear road map and we/they are not sure that the PR will be merged; probably i’m repeating myself but that what i can see.
I’m using custom app because i need specific features for stock and food retail chain (not exhaustive list):
- Multi Barcode per Item
- Import/Export custom records from/to user
- sync with other ERP and/or other Accountant software
- More infos in
Item Supplier, like item per box, box per pallet, item enabled at supplier side …etc
- Supplier side charges per item
- etc. etc. etc.
Other feature i need, and probably other peoples need:
- Purchase cycle for
- Promotional Plans
- show title_field in Links
Now, probably i asked you few times, can you assure me that if i send a PR regarding what i need, all this will be merged? If so, I will be more than happy to send a PR, as i’ve done with
options for Barcode Control and other few fix, otherwise i’d need to rewrite code back for a custom app loosing time.
I know for sure that peoples would like to pay to have feature integrated in ERPNext but, again, what about if they will pay and PR will not be merged?
I think you, the core team, have a clear road map in mind …so lets share it and discuss how to improve; once defined will be surely simpler to contribute.
Perhaps having people contributing to add feature in road map would be a good idea, the more people want it the more contribution PR will have.
I have answered this multiple times, but will do so again
- You have to follow the contribution guidelines
- Your contribution has to be designed in a manner that is useful to most people.
Will your PR get merged in first-try. Probably NO. But if you are willing to take feedback and improve your PR, very high chances it will get merged.
From my POV, anything going in a custom app, HAS NO VALUE TO THE COMMUNITY,
so I have no incentive to help. Developers of custom apps just end up wasting everyone’s time.
What really pisses me off is that most developers of custom apps, have NO INTENTION of contributing anything back.
I think it’s not a matter first-try, but if the feature itself will be merged or not. Let’s have an example:
- Multiple Barcode: it’s not a big PR, would be possible to write quite fast
My question is, if it will meet guidelines and all stuff, will be merged? Or will that will be closed and not merged because few peoples needs it? That’s my only concern, spend time to build up a PR and then not able to merge because, let’s say, “not in road map” or “most people needs that”
IMHO, you (core team) and we (as foundation members) needs to find out a way to make people contributing in some way …donating, paying for features, developing, testing, answering issues and stuff …so in some way people need to give something back; also as extreme actions …locking custom script and form customization …for not contributors.
At the begin probably, as drawback, ERPNext would loose some users …but at the end of the day …imho not much loose …and this probably will speed up contribution in any of the above ways.
Just my humble opinion …but i get really pissed of features not merged because no contributions …
I am surprised that you don’t even give it a try. It is really an approach to things. If you want to be a contributor or not. You should know by now what PRs get merged and which do not.
Well …probably helped by a crystal ball …
Let me try with Multiple Barcode for item PR …
Don’t you think will be more straightforward to have a road map?
you can push the foundation to work on this… i don’t have a roadmap
Pushed few times but not result …i’ll retry …I’m available to coordinate if no one else is available …