ankush
January 20, 2023, 1:42pm
21
The feature wont be ported but if you’re a developer you can start using it today.
We use it while editing form and since output (the doctype.json) file is same and backward compatible we can port the changes back to old version easily.
1 Like
pmjd
January 20, 2023, 2:35pm
22
Will try and get a clip of it later
jez
January 29, 2023, 2:43am
24
This will be fantastic for new users learning and it it is similar to the way other form builders work.
1 Like
It’s more helpful in finetuning the doctype look and feel and defining properties, and adding fields.
1 Like
Hi, One small note, the form builder does not seem to have any breadcrumbs, so you have to click the back button on the browser to continue working on the DocType.
Very Nice Development it make erpnext easy for non-developer.
1 Like
Can not wait when v15 will release?
May I know why the option for “Form Builder” is not showing.
@buildwithhussain
1 Like
avc
May 12, 2023, 4:26am
32
It’s only avaliable on v15 (develop)
2 Likes
Now you can move standard fields freely in form builder customize form
frappe:develop ← resilient-tech:field-order-support
opened 05:14AM - 09 Jun 23 UTC
https://github.com/frappe/frappe/assets/30859809/730256e1-39ca-41d3-b7e2-d221ed3… e197a
### Changes Made
- remove background color distinction for custom fields (same as customize form).
- remove draggable filtering for custom fields and tabs / sections with std fields.
- remove attribute `data-has-std-field`. not used anymore.
`no-docs`
7 Likes
pmjd
June 9, 2023, 8:31am
35
Fantastic news
1 Like
Thanks, Frappe Team for removing this drawback of Frappe. Great!
Will this work when using version 14 (we are using ERPNext: v14.26.0 (version-14) / Frappe Framework: v14.37.1 (version-14)
ankush
June 12, 2023, 1:19pm
38
Standard field order customization was contributed almost entirely by @dj12djdjs and @snv
frappe:develop ← pps190:customize_form
opened 02:56PM - 28 Jan 23 UTC
continuation of: https://github.com/frappe/frappe/pull/19452
Customize Form n… ow supports reordering all fields (including "standard" ones) 🎉
### Implementation
A new property setter called `field_order` has been introduced. When `meta.sort_fields` is called following is done:
- if field order doesn't exist, existing algorithm applies
If field order exists:
- field order is "cleaned" for dead fields
- if it matches size of fields, new order is immediately updated (best case scenario)
In case new fields are present in doctype, but aren't in cleaned field order:
- if standard fields at the top of the DocType's fields table are absent in the field order, a list is created of such fields.
- if there are atleast some standard fields in field order, the above list is prepended to field order, else, the above list becomes field order (essentially field order gets invalidated)
- remaining fields are inserted using following logic:
- `insert_after` for custom fields (same as before)
- computed `insert_after` for standard fields (this is currently done based on the DocType's fields table)
### Additional implementation (if reviewer requests it)
- [ ] Delete invalid `field_order` (if no standard fields found) by enqueue-ing a DB call
- [ ] Update field order (when re-computed) by enqueue-ing a DB call
- [ ] Notify system managers if field order needs update. The "computed insert after" logic isn't 100% accurate so it can be beneficial if user reviews the order and manually fixes as needed (needs above update feature as well - to prevent duplicate notifications)
cc: @ankush @surajshetty3416
### TODO (after initial review)
- [ ] tests for "computed" logic
- [x] support for form builder
- [ ] documentation
To be backported together with #20168
10 Likes
pmjd
June 23, 2023, 2:35pm
39
Is there any easy way to install the Form Builder on ERPNext v14 to allow it to customise standard forms?
No, Form Builder will only work in Nightly/v15 beta branch
