Determine Zoom window depending on record
Description
Environment
Attachments
- 07 Mar 2013, 03:32 AM
- 07 Mar 2013, 03:32 AM
- 28 Feb 2013, 02:42 PM
- 28 Feb 2013, 02:42 PM
- 25 Jan 2013, 09:25 PM
- 07 Dec 2012, 09:37 PM
relates to
testing discovered
Activity
Dirk Niemeyer April 16, 2016 at 7:08 AM
Just for the records: a working link to the commit is https://bitbucket.org/idempiere/idempiere-historic/commits/5c956db
Regards,
Dirk Niemeyer
Carlos Ruiz July 23, 2013 at 8:40 PM
Peer reviewed and approved https://bitbucket.org/trekglobal/idempiere/commits/5c956db
Must we include in this ticket the fixes for:
The RMA documents that share table with shipments/receipts
The table discount schema that share table with price list schema
Or open a new ticket to fix those?
Regards,
Carlos Ruiz
Nicolas Micoud March 7, 2013 at 2:07 PM
Hi Carlos,
Yes, we talked about this evolution in a meeting, but i thought it could be an evolution (it is "only" a different way to select the new destination window).
That is why i did not update the fields.
Anyway, using a value from another record would be really cool, especially for DisplayLogic (ATM, you must use a virtual column to achieve it).
Regards,
Nicolas
Carlos Ruiz March 7, 2013 at 3:32 AM
Hi Nicolas - I tried to integrate this ticket - but I think we need to design it to manage context or sql conditions instead of table.column+operator. (I think we talked about this in a meeting).
Also I think as precondition maybe we need to expand the context parsing and evaluation to allow indirect references. I mean instead of just using @AD_User_ID@ I would like to be able to use something like @AD_User_ID.Password@ for the context meaning that we want to get the AD_User.Password based on AD_User_ID - this could be applicable for all the "logic" fields (display, readonly, mandatory, default) and that would make it very powerful.
Will postpone this until we find time to design those two options.
NOTE:
I'm attaching 01_IDEMPIERE-528.patch as the integration of your two patches and as my peer review for best practices and creating a missing SeqNo column.
Regards,
Carlos Ruiz
Following :
https://groups.google.com/forum/#!topic/idempiere/dq8M9W_zT4s
http://www.globalqss.com/wiki/index.php/IDempiere/FullMeeting20121205