Just checked the code, I am thinking whether is possible to re-use the standard journal entry instead of creating another new doctype.
That is up to you, adding many things in a single form is not always a good idea.
We have added incoming and outgoing payment in a single form called gl payment but they’re separate forms in SAP.
All the best.
getting error Invalid version string: '13.0.0.beta.1’
According to Ooops, a server error has occured , and the issues above:
Go to this folder /home/your-user-name/frappe-bench/apps/erpnext/erpnext/change_log
Enter folder called v13
Find the file v13_0_0_beta_1.md and rename to v13_0_0-beta_1.md (mv v13_0_0_beta_1.md v13_0_0-beta_1.md)
1 Like
Tried to upgrade to V 13
got me this
Traceback (most recent call last):
File “/usr/local/bin/bench”, line 11, in
load_entry_point(‘bench’, ‘console_scripts’, ‘bench’)()
File “/home/frappe/.bench/bench/cli.py”, line 41, in cli
bench_command()
File “/usr/local/lib/python3.6/dist-packages/click/core.py”, line 764, in call
return self.main(*args, **kwargs)
File “/usr/local/lib/python3.6/dist-packages/click/core.py”, line 717, in main
rv = self.invoke(ctx)
File “/usr/local/lib/python3.6/dist-packages/click/core.py”, line 1137, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File “/usr/local/lib/python3.6/dist-packages/click/core.py”, line 956, in invoke
return ctx.invoke(self.callback, **ctx.params)
File “/usr/local/lib/python3.6/dist-packages/click/core.py”, line 555, in invoke
return callback(*args, **kwargs)
File “/home/frappe/.bench/bench/commands/update.py”, line 43, in switch_to_branch
switch_to_branch(branch=branch, apps=list(apps), upgrade=upgrade)
File “/home/frappe/.bench/bench/app.py”, line 417, in switch_to_branch
switch_branch(branch, apps=apps, bench_path=bench_path, upgrade=upgrade)
File “/home/frappe/.bench/bench/app.py”, line 409, in switch_branch
reload_module(utils)
NameError: name ‘utils’ is not defined
frappe@erpnext5512167:~/frappe-bench$
I got exact same error
Check this out. We’re open to get this into the core, if there’s enough interest.
2 Likes
I’m interested
I’m interested
I’m interested in dunning too
Some great features in Beta 13 version , Great job !
Unable to find Role and Module list to attach to Users .
Is this by design or a bug ?
Thanks
Version 13 is awesome, Great Job by Frappe…!!!
but hooks(web-css) is not working.
web_include_css = "path-to-web-css-file"
is this a bug?
Thanks
I tried to customise BOM by adding custom field and I get the following error:
Scrap material is a data field and not currency, I don’t know why this is the case. Maybe this is the cause of the error:
Well, why is “Scrap Material Cost” a data field, not currency like the two others?
That’s the problem. and I can’t change it. I think it’s a bug
I’m suprised, this is not integrated yet. Dunning should be a core component of any invoicing system in my thoughts.
2 Likes
Great job!
Hi @rmeyer have you talked to @dominik about this? He is also looking to get his version into core.
Kind regards
Let’s take this whole Dunning discussion to Dunning / Mahnung / Warning Notice .
This comment should answer your question: Dunning / Mahnung / Warning Notice - #22 by rmeyer