#idempiere IRC log for Monday, 2015-10-05

« Sunday, 2015-10-04 Index Tuesday, 2015-10-06 »
*** xapiens has joined #idempiere01:37
Not-5e44[iDempiereDaily] jenkins built #458 completed (success) http://ci.idempiere.org/job/iDempiereDaily/458/03:09
*** xapiens has quit IRC03:10
*** riz_ has joined #idempiere05:06
riz_HI everybody05:06
riz_how are you?05:06
* riz_ slaps riz_ around a bit with a large fishbot05:09
*** nmicoud has joined #idempiere05:26
*** riz_ has quit IRC05:34
*** a42niem has joined #idempiere05:41
Not-5e44[IDEMPIERE] dantam updated IDEMPIERE-286206:41
Not-5e44[IDEMPIERE] Me and my clients are heavily dependent on JasperReports (and also uses multilingual support). I'll see what I can do with testing. Would you like me to test the upcoming release?06:41
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-286206:41
*** mbozem has joined #idempiere06:46
*** a42niem has quit IRC08:55
*** KermitTheFragger has joined #idempiere09:08
Not-5e44[IDEMPIERE] hieplq updated IDEMPIERE-286209:17
Not-5e44[IDEMPIERE] Hi [~dantam], what's way you deploy jasper report to idempiere? use source file or binary compile by ireport? it's best to deploy source file. also maybe add new configuration to set compatible level when idempiere compile jasper report.09:17
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-286209:17
Not-5e44[IDEMPIERE] hieplq updated IDEMPIERE-2640 status set to "Closed" -assignee set to "None"09:24
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-264009:24
Not-5e44[IDEMPIERE] hieplq updated IDEMPIERE-1820 status set to "Closed" -assignee set to "None"09:24
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-182009:24
Not-5e44[IDEMPIERE] dantam updated IDEMPIERE-286209:29
Not-5e44[IDEMPIERE] I actually mostly use binary compiled attachments. Thanks for the info. I'll start using sources from now on :-)09:29
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-286209:29
*** KermitTheFragger has quit IRC09:44
*** KermitTheFragger has joined #idempiere09:45
Not-5e44[IDEMPIERE] hieplq created IDEMPIERE-2876 unnecessary manual control timeout when get connection because it's support by c3p0 lib10:03
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-287610:03
*** norbertbede1 has joined #idempiere10:55
*** norbertbede1 has quit IRC11:26
*** CarlosRuiz has joined #idempiere11:34
*** ChanServ sets mode: +o CarlosRuiz11:34
Not-5e44[IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-286211:39
Not-5e44[IDEMPIERE] Yes [~dantam], will be great if you can help with tests for the upcoming release and maybe jasper 6.1.1 In my case I prefer to binaries instead of sources to avoid the overhead of compiling jasper every time. Regards, Carlos Ruiz11:39
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-286211:39
Not-5e44[IDEMPIERE] d_ruiz updated IDEMPIERE-2875 Attachment set to "IDEMPIERE-2875-2.patch"11:41
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-287511:41
*** norbertbede1 has joined #idempiere11:42
Not-5e44[IDEMPIERE] d_ruiz updated IDEMPIERE-2875 Attachment set to "None"11:49
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-287511:49
Not-5e44[IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-287611:51
Not-5e44[IDEMPIERE] Hi [~hieplq], can you please upload a patch with your proposal, and if possible you can point me to a test case where the difference can be tested. Regards, Carlos Ruiz11:51
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-287611:51
Not-5e44[IDEMPIERE] d_ruiz updated IDEMPIERE-2875 Attachment set to "IDEMPIERE-2875-2.patch"11:57
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-287511:57
*** xapiens has joined #idempiere12:16
Not-5e44[IDEMPIERE] tsvikruha updated IDEMPIERE-269212:55
Not-5e44[IDEMPIERE] Hi [~carlosruiz_globalqss], we have some customizations on taxes and pricing (as was presented in Krefeld). I think during testing our customizations we discovered this bug and we considered as important to report it to community. I think this is bug becuase if user creates Invoice in ORG A and then next one in ORG B and try to copy A to B then B will have header with A and lines with B - more logical12:55
Not-5e44sounds for us to have also on lines organization B. Maybe [~norbert.bede] remember more exact use cases when we found this issue (my opininon is that during setting taxes and calculation of global price from organization level)12:55
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-269212:55
*** norbertbede1 has quit IRC13:09
Not-5e44[IDEMPIERE] carlosruiz_globalqss created IDEMPIERE-2877 Adapt jasper reporting to latest (actually using deprecated methods)13:15
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-287713:15
Not-5e44[iDempiere] CarlosRuiz_globalqss pushed 1 commit to development [+0/-0/±1] https://bitbucket.org/idempiere/idempiere/commits/13:19
Not-5e44[iDempiere] globalqss 01e1595 - IDEMPIERE-2877 Adapt jasper reporting to latest (actually using deprecated methods) / thanks to Thomas Bayen (tbayen) - bringing his solution for deprecated methos to ReportStarter from https://bitbucket.org/tbayen_bxservice/de.bxservice.report.jasper/src/tip/de.bxservice.report/src/de/bxservice/report/ReportStarter.java13:19
Not-5e44[IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-287713:27
Not-5e44[IDEMPIERE] Committed solution from [~tbayen] in his ReportStarter: https://bitbucket.org/tbayen_bxservice/de.bxservice.report.jasper/src/tip/de.bxservice.report/src/de/bxservice/report/ReportStarter.java For the class ZkJRViewer - we have discussed with [~d_ruiz] and it seems the approach of that viewer is very wrong. ZkJRViewer is not just a viewer class - but is creating the report (a model class), a better13:27
Not-5e44approach would be to refactor ZkJRViewer to call the ReportStarter - and make viewer just that -> a viewer of files rendered in another class. This is inline with IDEMPIERE-2684 and allowing jasper to be a replaceable plugin as [~tbayen] has proposed and is trying with his de.bxservice.report.jasper plugin (but ZkJRViewer is making it difficult). WDYT? Regards, Carlos Ruiz13:27
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-287713:28
Not-5e44[iDempiere] CarlosRuiz_globalqss pushed 1 commit to development [+0/-0/±1] https://bitbucket.org/idempiere/idempiere/commits/13:31
Not-5e44[iDempiere] druiz_bxservice 66c76a4 - IDEMPIERE-2875 GridTabCSVImporter code refactoring13:31
Not-5e44[IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-2672 status set to "Reopened" -resolution set to "None"13:31
Not-5e44[IDEMPIERE] This ticket is creating issues reported with many users using multiple organizations.13:31
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-267213:32
Not-5e44[IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-2672 priority set to "Blocker"13:32
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-267213:32
Not-5e44[iDempiere] jenkins built #1746 completed (success) http://ci.idempiere.org/job/iDempiere/1746/13:33
Not-5e44[IDEMPIERE] MZI updated IDEMPIERE-286713:39
Not-5e44[IDEMPIERE] Hi [~carlosruiz_globalqss] , I tried to create test case on demo , but actually at this moment I am not able ( gardenAdmin) to select account in Accounting Fact Reconcilation (manual). The use case was on payment. Name for Match code in payment allocation and payment reconciliation is created same way : Auto C_Payment: "C_Payment_ID". So we have 2 transactions with same Matchcode. If one of that matchcode13:39
Not-5e44is not reconciled, we are seeing also the other one as not reconciled. Steps to reproduce : Payment is allocated to invoice but not reconciled on bank statement. If we use filter for B_UnallocatedCash_Acct we will get this transaction as unreconciled , even allocation is done and we can see total of matchcode for the account is balanced. In report "Unreconciled accounting facts" its correct. Enhanced solution is also13:39
Not-5e44to modify rule that creates name of matchcode for Allocation, but Tomas patch is also necessary13:39
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-286713:39
Not-5e44[iDempiere] jenkins built #1747 completed (success) http://ci.idempiere.org/job/iDempiere/1747/13:40
*** mon has joined #idempiere13:49
Not-5e44[IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-286714:22
Not-5e44[IDEMPIERE] > at this moment I am not able ( gardenAdmin) to select account in Accounting Fact Reconcilation (manual) Hi [~MZI], that's already fixed but not arrived to dev, workaround is to clear the accounting schema field, move to another field, and then select again the schema, then you can select the account.14:22
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-286714:22
*** CarlosRuiz has quit IRC14:23
*** norbertbede1 has joined #idempiere14:48
*** norbertbede1 has quit IRC15:05
*** KermitTheFragger has quit IRC15:33
Not-5e44[IDEMPIERE] d_ruiz created IDEMPIERE-2878 Allow single trx in CSV Importer15:39
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-287815:39
Not-5e44[IDEMPIERE] d_ruiz updated IDEMPIERE-2878 Attachment set to "IDEMPIERE-2878.patch"15:41
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-287815:41
Not-5e44[IDEMPIERE] d_ruiz updated IDEMPIERE-287815:42
Not-5e44[IDEMPIERE] In the attached file you can find the patch that allows to choose a single trx option. To be able to do it, the header of the file must have a /KT. T indicating that it will be a single trx file. When a record fails it stops there and rollback all the previous records. Please any feedback will be highly appreciated. Kind Regards, Diego Ruiz15:42
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-287815:42
*** norbertbede1 has joined #idempiere16:05
*** nmicoud has left #idempiere16:08
Not-5e44[IDEMPIERE] norbert.bede updated IDEMPIERE-269216:16
Not-5e44[IDEMPIERE] [~carlosruiz_globalqss]. sure remember. use case: orgA = company 1 and orgB = Company 2. so they are different companies not departments. process: user create sales invoice in orgA, complete it, then user creates invoice 2 in orgB and copy invoice lines from orgA invoice to orgB invoice. Organization are inherited from orgA lines to orgB invoice lines. So we got an invoice with orgB header and orgA lines.16:16
Not-5e44After completing orgB invoice, invoice Tax was calculated to orgA instead orgB. this cause inconsistent data. We fixed it and working properly now.16:16
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-269216:16
*** xapiens_ has joined #idempiere16:18
*** xapiens has quit IRC16:19
*** mbozem has quit IRC16:20
*** norbertbede1 has quit IRC16:57
*** mbozem has joined #idempiere17:34
*** Ash___ has joined #idempiere17:48
Ash___hi17:48
*** paul__ has joined #idempiere17:51
paul__hello17:51
*** paul__ has quit IRC17:52
Ash___hi18:02
*** Ash___ has quit IRC18:03
*** mbozem has quit IRC20:45
*** ChuckBoecking has joined #idempiere22:04
Not-5e44[IDEMPIERE] cboecking updated IDEMPIERE-281122:49
Not-5e44[IDEMPIERE] This Section exists in the attache "primary key steps 01.sql" attachment 1. SQL - Drop current compound primary key 2. SQL - create new column NOT!! as primary key (example: M_ProductPrice_ID) 3. SQL - create sequence 4. SQL - update new column with sequence 5. SQL - make column the primary key execute attached SQL This section will be captured in a Log Migration Script 1. Enter Dictionary Maintenance22:49
Not-5e44username and password 2. Turn on Dictionary Maintenance and Log Migration Script 3. Find M_ProductPrice 4. Enable Change Log 5. Create M_ProductPrice_ID System Element ##. set Entity Type = Dictionary 6. Create M_ProductPrice_ID ##. make mandatory ##. do not allow copy 7. Find out every tab where table used (use AD_Client_ID -> Used in Field sub-tab) 8. Add key to every WT&F using the Create Fields process setting22:49
Not-5e44the Created Since date to yesterday To run migration script in a test environment: psql -U adempiere -d idempiere -f /tmp/mig....postgres.sql Test to make sure all worked as expected - set GWAdmin role to isChangeLog = y and change a product->price Create new patch in code. * regenerate model for M_ProductPrice * Update MProductPrice.java to remove "multi-key" exception Attach patch to ticket Test cases: * make sure22:49
Not-5e44new record get created and updated values * make sure updated records get correct details (updated and updatedby) * make sure records that existed before this change act correctly. * create a run Price Schema pass to make sure all works as expected * upgrade an existing system that is configured to use native sequences Discussion Notes: * If 'Enable Native Sequence' was run before this ticket is released, the22:49
Not-5e44'm_productprice_sq' sequence will already exist (even though not previously used). Challenge: we need a way to update the sequence nextval if the above script created more than 900K primary key values. FYI - the m_productprice_sq nextval is 1,000,000.22:49
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-281122:49
Not-5e44[IDEMPIERE] cboecking updated IDEMPIERE-281122:54
Not-5e44[IDEMPIERE] Section 1 Attached "primary key steps 01.sql" 1. SQL - Drop current compound primary key 2. SQL - create new column NOT!! as primary key (example: M_ProductPrice_ID) 3. SQL - create temporary sequence 4. SQL - update new column with sequence 5. SQL - make column the primary key Section 2: execute attached SQL This section will be captured in a Log Migration Script 1. Enter Dictionary Maintenance username22:54
Not-5e44and password 2. Turn on Dictionary Maintenance and Log Migration Script 3. Find M_ProductPrice 4. Enable Change Log 5. Create M_ProductPrice_ID System Element ##. set Entity Type = Dictionary 6. Create M_ProductPrice_ID ##. make mandatory ##. do not allow copy 7. Find out every tab where table used (use AD_Client_ID -> Used in Field sub-tab) 8. Add key to every WT&F using the Create Fields process setting the Created22:54
Not-5e44Since date to yesterday To run migration script in a test environment: psql -U adempiere -d idempiere -f /tmp/mig....postgres.sql Test to make sure all worked as expected - set GWAdmin role to isChangeLog = y and change a product->price Create new patch in code. * regenerate model for M_ProductPrice * Update MProductPrice.java to remove "multi-key" exception Attach patch to ticket * Update M_PriceList_Create to22:54
Not-5e44include nextId Test cases: * make sure new record get created and updated values * make sure updated records get correct details (updated and updatedby) * make sure records that existed before this change act correctly. * create a run Price Schema pass to make sure all works as expected * upgrade an existing system that is configured to use native sequences Discussion Notes: * If 'Enable Native Sequence' was run22:54
Not-5e44before this ticket is released, the 'm_productprice_sq' sequence will already exist (even though not previously used). Challenge: we need a way to update the sequence nextval if the above script created more than 900K primary key values. FYI - the m_productprice_sq nextval is 1,000,000.22:54
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-281122:54
Not-5e44[IDEMPIERE] cboecking updated IDEMPIERE-281123:06
Not-5e44[IDEMPIERE] Section 1 Attached "primary key steps 01.sql" 1. SQL - Drop current compound primary key 2. SQL - create new column NOT!! as primary key (example: M_ProductPrice_ID) 3. SQL - create temporary sequence 4. SQL - update new column with sequence 5. SQL - make column the primary key Section 2: execute attached SQL This section will be captured in a Log Migration Script 1. Enter Dictionary Maintenance username23:06
Not-5e44and password 2. Turn on Dictionary Maintenance and Log Migration Script 3. Find M_ProductPrice 4. Enable Change Log 5. Create M_ProductPrice_ID System Element ##. set Entity Type = Dictionary 6. Create M_ProductPrice_ID ##. make mandatory ##. do not allow copy 7. Find out every tab where table used (use AD_Client_ID -> Used in Field sub-tab) 8. Add key to every WT&F using the Create Fields process setting the Created23:06
Not-5e44Since date to yesterday To run migration script in a test environment: psql -U adempiere -d idempiere -f /tmp/mig....postgres.sql Section 3: update AD_Sequence just in case the count went above the default. Section 4: Create new patch in code. * regenerate model for M_ProductPrice * Update MProductPrice.java to remove "multi-key" exception Attach patch to ticket * Update M_PriceList_Create to include nextId Test23:06
Not-5e44cases: * Test to make sure all worked as expected - set GWAdmin role to isChangeLog = y and change a product->price * make sure new record get created and updated values * make sure updated records get correct details (updated and updatedby) * make sure records that existed before this change act correctly. * create a run Price Schema pass to make sure all works as expected * upgrade an existing system that is23:06
Not-5e44configured to use native sequences Discussion Notes: * If 'Enable Native Sequence' was run before this ticket is released, the 'm_productprice_sq' sequence will already exist (even though not previously used). Challenge: we need a way to update the sequence nextval if the above script created more than 900K primary key values. FYI - the m_productprice_sq nextval is 1,000,000.23:06
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-281123:06
Not-5e44[IDEMPIERE] cboecking updated IDEMPIERE-281123:07
Not-5e44[IDEMPIERE] Section 1 Attached "primary key steps 01.sql" 1. SQL - Drop current compound primary key 2. SQL - create new column NOT!! as primary key (example: M_ProductPrice_ID) 3. SQL - create temporary sequence 4. SQL - update new column with sequence 5. SQL - make column the primary key Section 2: execute attached SQL This section will be captured in a Log Migration Script 1. Enter Dictionary Maintenance username23:08
Not-5e44and password 2. Turn on Dictionary Maintenance and Log Migration Script 3. Find M_ProductPrice 4. Enable Change Log 5. Create M_ProductPrice_ID System Element ##. set Entity Type = Dictionary 6. Create M_ProductPrice_ID ##. make mandatory ##. do not allow copy 7. Find out every tab where table used (use AD_Client_ID -> Used in Field sub-tab) 8. Add key to every WT&F using the Create Fields process setting the Created23:08
Not-5e44Since date to yesterday To run migration script in a test environment: psql -U adempiere -d idempiere -f /tmp/mig....postgres.sql Section 3: update AD_Sequence just in case the count went above the default. Section 4: Create new patch in code. * regenerate model for M_ProductPrice * Update MProductPrice.java to remove "multi-key" exception Attach patch to ticket * Update M_PriceList_Create to include nextId Test23:08
Not-5e44cases: * Test to make sure all worked as expected - set GWAdmin role to isChangeLog = y and change a product->price * make sure new record get created and updated values * make sure updated records get correct details (updated and updatedby) * make sure records that existed before this change act correctly. * create a run Price Schema pass to make sure all works as expected * upgrade an existing system that is23:08
Not-5e44configured to use native sequences Discussion Notes: * If 'Enable Native Sequence' was run before this ticket is released, the 'm_productprice_sq' sequence will already exist (even though not previously used). Challenge: we need a way to update the sequence nextval if the above script created more than 900K primary key values. FYI - the m_productprice_sq nextval is 1,000,000.23:08
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-281123:08
Not-5e44[IDEMPIERE] cboecking updated IDEMPIERE-281123:14
Not-5e44[IDEMPIERE] Section 1 Attached "primary key steps 01.sql" 1. SQL - Drop current compound primary key 2. SQL - create new column NOT!! as primary key (example: M_ProductPrice_ID) 3. SQL - create temporary sequence 4. SQL - update new column with sequence 5. SQL - make column the primary key Section 2: execute attached SQL This section will be captured in a Log Migration Script 1. Enter Dictionary Maintenance username23:14
Not-5e44and password 2. Turn on Dictionary Maintenance and Log Migration Script 3. Find M_ProductPrice 4. Enable Change Log 5. Create M_ProductPrice_ID System Element ##. set Entity Type = Dictionary 6. Create M_ProductPrice_ID ##. make mandatory ##. do not allow copy 7. Find out every tab where table used (use AD_Client_ID -> Used in Field sub-tab) 8. Add key to every WT&F using the Create Fields process setting the Created23:14
Not-5e44Since date to yesterday To run migration script in a test environment: psql -U adempiere -d idempiere -f /tmp/mig....postgres.sql Section 3: update AD_Sequence just in case the count went above the default. Section 4: Create new patch in code. * regenerate model for M_ProductPrice * Update MProductPrice.java to remove "multi-key" exception Attach patch to ticket * Update M_PriceList_Create to include nextId Test23:14
Not-5e44cases: * Test to make sure all worked as expected - set GWAdmin role to isChangeLog = y and change a product->price * make sure new record get created and updated values * make sure updated records get correct details (updated and updatedby) * make sure records that existed before this change act correctly. * create a run Price Schema pass to make sure all works as expected * upgrade an existing system that is23:14
Not-5e44configured to use native sequences Discussion Notes: * If 'Enable Native Sequence' was run before this ticket is released, the 'm_productprice_sq' sequence will already exist. This means using the nextID function will work regardless of whether the system uses native of AD_Sequence values for IDs.23:14
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-281123:14
Not-5e44[IDEMPIERE] cboecking updated IDEMPIERE-281123:48
Not-5e44[IDEMPIERE] The purpose of this ticket is to create a single primary key for m_productprice. Doing so gives m_productprice the same abilities as other tables with a single primary key. These abilities include: * accepting attachments * maintaining change log * etc... There are quite a few examples of of these tables. It is my hope that this ticket provides the model for doing the same to other tables if needed. Here23:48
Not-5e44is sql to help identify these tables: {{select t.tablename from ad_table t where 0= (select count (*) from ad_column c where c.ad_table_id = t.ad_table_id and c.iskey = 'Y' ) and t.isview='N' and lower(t.tablename) not like '%trl' and lower(t.tablename) not like 't_%' and lower(t.tablename) not like 'm_%ma' and lower(t.tablename) not like 'm_storage%' order by lower(t.tablename);}} The steps are described below. You23:48
Not-5e44will take the results of the below steps to hand-create the final migration script. Section 1 Attached "primary key steps 01.sql" 1. SQL - Drop current compound primary key 2. SQL - create new column NOT!! as primary key (example: M_ProductPrice_ID) 3. SQL - create temporary sequence 4. SQL - update new column with sequence 5. SQL - make column the primary key Section 2: execute attached SQL This section will be23:48
Not-5e44captured in a Log Migration Script 1. Enter Dictionary Maintenance username and password 2. Turn on Dictionary Maintenance and Log Migration Script 3. Find M_ProductPrice 4. Enable Change Log 5. Create M_ProductPrice_ID System Element ##. set Entity Type = Dictionary 6. Create M_ProductPrice_ID ##. make mandatory ##. do not allow copy 7. Find out every tab where table used (use AD_Client_ID -> Used in Field sub-tab)23:48
Not-5e448. Add key to every WT&F using the Create Fields process setting the Created Since date to yesterday To run migration script in a test environment: psql -U adempiere -d idempiere -f /tmp/mig....postgres.sql Section 3: update AD_Sequence just in case the count went above the default. Section 4: Create new patch in code. * regenerate model for M_ProductPrice * Update MProductPrice.java to remove "multi-key" exception23:48
Not-5e44Attach patch to ticket * Update M_PriceList_Create to include nextId Test cases: * Test to make sure all worked as expected - set GWAdmin role to isChangeLog = y and change a product->price * make sure new record get created and updated values * make sure updated records get correct details (updated and updatedby) * make sure records that existed before this change act correctly. * create a run Price Schema pass to23:48
Not-5e44make sure all works as expected * upgrade an existing system that is configured to use native sequences Discussion Notes: * If 'Enable Native Sequence' was run before this ticket is released, the 'm_productprice_sq' sequence will already exist. This means using the nextID function will work regardless of whether the system uses native of AD_Sequence values for IDs.23:48
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-281123:48
Not-5e44[IDEMPIERE] cboecking updated IDEMPIERE-281123:48
Not-5e44[IDEMPIERE] The purpose of this ticket is to create a single primary key for m_productprice. Doing so gives m_productprice the same abilities as other tables with a single primary key. These abilities include: * accepting attachments * maintaining change log * etc... There are quite a few examples of of these tables. It is my hope that this ticket provides the model for doing the same to other tables if needed. Here23:48
Not-5e44is sql to help identify these tables: select t.tablename from ad_table t where 0= (select count (*) from ad_column c where c.ad_table_id = t.ad_table_id and c.iskey = 'Y' ) and t.isview='N' and lower(t.tablename) not like '%trl' and lower(t.tablename) not like 't_%' and lower(t.tablename) not like 'm_%ma' and lower(t.tablename) not like 'm_storage%' order by lower(t.tablename); The steps are described below. You will23:48
Not-5e44take the results of the below steps to hand-create the final migration script. Section 1 Attached "primary key steps 01.sql" 1. SQL - Drop current compound primary key 2. SQL - create new column NOT!! as primary key (example: M_ProductPrice_ID) 3. SQL - create temporary sequence 4. SQL - update new column with sequence 5. SQL - make column the primary key Section 2: execute attached SQL This section will be captured23:48
Not-5e44in a Log Migration Script 1. Enter Dictionary Maintenance username and password 2. Turn on Dictionary Maintenance and Log Migration Script 3. Find M_ProductPrice 4. Enable Change Log 5. Create M_ProductPrice_ID System Element ##. set Entity Type = Dictionary 6. Create M_ProductPrice_ID ##. make mandatory ##. do not allow copy 7. Find out every tab where table used (use AD_Client_ID -> Used in Field sub-tab) 8. Add23:48
Not-5e44key to every WT&F using the Create Fields process setting the Created Since date to yesterday To run migration script in a test environment: psql -U adempiere -d idempiere -f /tmp/mig....postgres.sql Section 3: update AD_Sequence just in case the count went above the default. Section 4: Create new patch in code. * regenerate model for M_ProductPrice * Update MProductPrice.java to remove "multi-key" exception Attach23:48
Not-5e44patch to ticket * Update M_PriceList_Create to include nextId Test cases: * Test to make sure all worked as expected - set GWAdmin role to isChangeLog = y and change a product->price * make sure new record get created and updated values * make sure updated records get correct details (updated and updatedby) * make sure records that existed before this change act correctly. * create a run Price Schema pass to make23:48
Not-5e44sure all works as expected * upgrade an existing system that is configured to use native sequences Discussion Notes: * If 'Enable Native Sequence' was run before this ticket is released, the 'm_productprice_sq' sequence will already exist. This means using the nextID function will work regardless of whether the system uses native of AD_Sequence values for IDs.23:48
Not-5e44[IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-281123:48
« Sunday, 2015-10-04 Index Tuesday, 2015-10-06 »

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!