Hi Rick! I'm a big fan of your blog and your writing, they have helped me out numerous times. Congratulations for the excellent work on this library! There's obviously a lot of time and effort put in to this project.
Mi question is if do you think it would be too complicated for me to add more lookup levels? I would like to use three or four levels of storing and retrieving the values. We'd just use one key for the resource, and the other three would come from the user's session (account, company, facility)
Background: I'm working on a massive ERP project with potentially lots of clients. Some clients like to call items "materials", others might prefer to call them "products". We'd like to have the possibility of having this terminology in the db, and choosing the proper one based on the user's account, company and facility)
Could you point me in the direction of which portions of the code might be affected by this, or if it's at all possible?
Hi Rick! I'm a big fan of your blog and your writing, they have helped me out numerous times. Congratulations for the excellent work on this library! There's obviously a lot of time and effort put in to this project.
Mi question is if do you think it would be too complicated for me to add more lookup levels? I would like to use three or four levels of storing and retrieving the values. We'd just use one key for the resource, and the other three would come from the user's session (account, company, facility) Background: I'm working on a massive ERP project with potentially lots of clients. Some clients like to call items "materials", others might prefer to call them "products". We'd like to have the possibility of having this terminology in the db, and choosing the proper one based on the user's account, company and facility) Could you point me in the direction of which portions of the code might be affected by this, or if it's at all possible?
Thanks in advance!