Data Import overrides name
See original GitHub issueDescription of the issue
When name (ID) is specified in data to be imported, ERPNext will still generate its own name and override the imported one.
Context information (for bug reports)
ERPNext: version-13-beta Frappe: version-13-beta Ubuntu 18.04 Bench >=5.0.0
Steps to reproduce the issue
- Go to Sales Settings and set Customer naming based on Naming Series
- Create a new naming series for Customer, for example
1.####
, starting at 0. - Create a new Data Import to insert into Customer.
- Download the empty template and add a customer with a higher series value in the ID column, for example
10005
. - Upload the template and start the import.
Observed result
The imported Customer gets the name “10001”. This is bad because it changes all my existing customer numbers.
Expected result
The imported Customer gets the name “10005”, as specified in the Data Import. It should still validate if a record with this name already exists, but not overwrite the value.
Also discussed here.
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
Example: Data Import File - Overrides - Oracle Help Center
FCCS_Rate Override. FCCS_Amount Override. A data import file could have these different amounts: Copy Entity, Jan, Point-of-View, Data Load Cube Name.
Read more >How to override module name (__name__)? - python
I have two classes in separate files, a.py and b.py. # a.py import logging LOG = logging.getLogger(__name__) class A: def ...
Read more >Catalog Items: Importing Location Overrides - RepairQ
You can add new catalog item location overrides or update existing catalog item location overrides in RepairQ with an import file.
Read more >[GA4] About Data Import - Analytics Help - Google Support
Typically, metadata is stored in a custom dimension or metric, though in some cases you might want to overwrite the default information already...
Read more >Data action overrides - Commerce | Dynamics 365
With data action overrides, you can override the registered action by creating a new action with the same action ID. Overriding a data...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@barredterra It seems in version-12 it is not available. However, in version-13 when you set the naming to “Prompt” the import will accept the ID(name) column. You should just make sure to change back to naming_series after the import is complete.
Proposed Solution:
After the import is done, prompt the user to manually update the current value for the series from Naming Series.
Move Naming Series DocType from ERPNext to Frappe app.