I fully agree that, especially once the webshop is up and running, a
modern search with multiple categories/tags/open search should be
implemented.
We have only about 300 articles in our items master; Indeed the
erpnext user fameliar with the codification scheme can easily find
articles, but once the webinterface is ready, a more sophisticated
scheme is necessary.
As far as changing the Item Code, I have not (yet) tried myself but
believe there is a tool to recodify (set-up>rename tool).
Anyway, I have learned from your sample that one can use multiple %.
On Mar 13, 3:13 pm, Addy ad...@gmail.com wrote:
Hi Robert,
I think that Item Codes and Item ID’s are same in ERP Next Back End, this
is why you can never change an Item Code once it is created since it
becomes the Primary Key in the database of mysql (I hope I am right, the
developers can shed more light on it)
This is the primary reason why I say that we should have a ID field which
is generated automatically or by a series like in transactions and also we
should have the ability to search for items via FILTERS since that is the
only thing lagging in the current system. Let me explain the things by
giving you people an example of my organisation. We are making tools of
different types now I would like that item IDs of tools be generated
automatically by a defined series like:
- Series of Carbide END Mills should be started by CBE so any new item
code of this type of item would be like CBE-001, CBE-002…etc
- Similarly for other item type the id could be generated automatically
by a defined set of SERIES.
Now the filters would be useful because currently the kind of search there
is in the system is by wild card and too works if two words are in correct
order. Let me explain this:
We have tools of different sizes like HSS-Square Tool 3/8’’ x 3/4’’ x 8’’
1X and like this there are like 5000 item codes and the only part changing
is the size part in most of the things now if I want to search for the
above item then in the wild card search if I enter %3/8%3/4%8 then it would
return the correct thing but if I enter %1X%3/8%3/4%8 then it would not
return the above size.
Like this the problem is exponentially increases if we have like 5000 item
codes and I am planning to add another 3k more for my raw materials which
again are governed by sizes (numbers). Therefore I think a search by adding
filters with drop downs would be an awesome feature which would make this
amazing piece of code even more user friendly.
I believe the best part about ERPNEXT is the kind of user friendliness it
offers to the users after everything is setup and therefore this filter
addition would add to its functionality even more.
I hope my examples would have conveyed the problems I am facing currently
with the system and I hope that this kind of a thing would be taken up in a
future road map of development of ERPNEXT. This filter based search would
come in more handy once the Web shop is up and running and I cannot expect
the visitors to remember the sequence of my Description for searching (I
hope you all can understand what I am trying to say here!!!)
On Monday, March 12, 2012 4:06:21 PM UTC+5:30, robert wrote:
Hi Aditya
I believe that we should distinguish between item codes and item id’s.
Users will always want to have the freedom to code their items one way
or the other, be it a formal coding system or a loose description. I
maintain two formal codes: my own in item ID, suppliers code in
Item_name, and i use the description field for a short description.
User ID’s, are in most systems, i believe, system generated and not
changeable by users, and from a coding perspective the integrity of
the databases are easier to maintain. Actually, I have no idea whether
Erpnext, somewhere at the background, maintains system generated id’s,
for Items or other tables.
If the system works correctly this should not be much of a concern for
the end-user.
However, I fully agree with your observations of searchability that sh/
c ould be improved.
rgds robert
On Mar 12, 7:59 am, Addy ad...@gmail.com wrote:
Hi Aditya,
The easiest way to de-codify items is to name them descriptively
(primary
keys in ERPNext are 180 characters long so its easy to do that). I think
it
would still be better than sequential naming.
Why we strongly recommend codification is because of the problem of
duplicates.
(this discussion is best left in the user-forum!)
best,
Rushabh
ERPNext - Business Operating System
W:https://erpnext.com
T: @rushabh_mehta
On Monday, March 12, 2012 12:29:05 PM UTC+5:30, Addy wrote:
Hi,
I have been using the erpnext since 18 months now and there is one
basic
improvement that I would like to suggest. The suggestion is for the
way we
import/create new items and the way they are maintained.
Basically we have an option to create an item code by ourselves, but
honestly speaking this, in my limited knowledge of ERP or any stock
management system, is not correct. Why I say this because giving users
the
right to create a PRIMARY KEY is not a good option and this ways
people
would always be asking questions on forums as to what way they should
design their item codes which is a very VAST subject given the type of
items that are there in the world.
Now my suggestion is that the item codes should be generated
automatically
and now that would give a problem of entering data. Now I suggest that
in
transactions the search of items should be through FILTERS which can
be
changes with CUSTOM FIELDS, this would make the usability and
implementation of ERP much easier for users not having a lot of prior
experience with creating item codes.
But the major requirement would be for this kind of system would be
the
ability to SEARCH with a combination of both FILTERS and WILD CARD
search.
The filters would need to be dynamic and I don’t know how much load
would
this functionality give on the SYSTEM as a whole because I guess it
would
be much more severe in terms of performance from the existing system.
This is a suggestion which I think would be much more important once
we
have the Webshop since after that a lot of people would be eager to
join in
but would get bogged down by the immense work of creating item codes
as it
is one of the major problems for people coming to a computerised
inventory
from a manual system