On 09/16/2011 12:27 AM, Ferdinand @ Camptocamp wrote: > Thanks for the explanation, but IMHO this is a real desaster for > multi stock locations where certain locations are used only for a > few products ( as I explained already frequently ) if we can not > filter (efficiently) for !=0 we get the complete list of products for > every location.
That's a valid but different and more specific topic, one that can be discussed without having to put it in a global "function fields" package. > and of course it was necessary to increase the limit in v5 to see > all records (which was sort of slow) and sort/filter them afterwards, > but it was possible, now it's not any more. A very bad practice indeed, and that obviously does not scale: hitting every single stock move line in the database, multiple times. That's just a bad solution for function fields in general, no matter how you look at it. Instead of supporting this kind of broken solution, it's much better to offer better alternatives for specific needs. > suppress "zero" lines is (was) a general usability issue in OpenERP. > Nobody is interested to see endless lists and reports with zeros. One possible alternative for inventory per location: have you tried to use the "Warehouse>Reporting>Inventory Analysis" view? If you group/filter per location, you should only see the products that have ever been in the specific location (some could still have 0 qty if the products are all gone, but for specialized locations this would work well enough). That analysis view should suffer much less of performance issues, because you can drill-down to zoom only on what you care for, and it has been optimized to hit the database less. For the generic Products lists I don't think we need this, most users will expect to see the complete list of products anyway (See bug 636215 where this was already discussed - almost a duplicate) One more alternative for location inventory views: the wizard that opens the inventory for a location could have an option to show only available products - very simple and much more scalable, I think. This is all a different wishlist improvement, though. Might be good to put this on feedback.openerp.com if it's not there yet? Wishlist bug 677454 might also be considered there, a bit different but probably doable efficiently too. > please check how Koo did it. What does Koo improve in the computation of function fields? -- You received this bug notification because you are a member of C2C OERPScenario, which is subscribed to OpenERP Project Group. https://bugs.launchpad.net/bugs/850752 Title: fnct_search missing for many function fields Status in OpenERP Addons (modules): Won't Fix Bug description: according to https://bugs.launchpad.net/bugs/823049 it will be possible to search for function fields store = false if fnct_search is defined a quick search shows 280 function fields in addons 14 fnct_search it would enhance the user experience a lot if at least for the most important function a searech could be defined for 6.1 as it is the rebirth of a lost feature available in v5 it would also easy migration. will you implement search functions if we / the community nominates some important candidates ? like * product stock available / on hand To manage notifications about this bug go to: https://bugs.launchpad.net/openobject-addons/+bug/850752/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~c2c-oerpscenario Post to : [email protected] Unsubscribe : https://launchpad.net/~c2c-oerpscenario More help : https://help.launchpad.net/ListHelp
