Post a custom field to VendTrans/CustTrans through journal
Link Help
Here is the scenario
It is not that complicated really, we just need to know what happens during the posting process. Let us assume we want to add a new field called VGRWeBelieve (type Enum NoYes) to VendTrans.
- You have added a custom field to your Customer/Vendor transactions table.
- You want to capture this field during the posting of a Customer/Vendor transaction from General Journal and post it to CustTrans/VendTrans.
It is not that complicated really, we just need to know what happens during the posting process. Let us assume we want to add a new field called VGRWeBelieve (type Enum NoYes) to VendTrans.
- First we need to capture the fields on journal lines. So we need to add the same field to the table LedgerJournalTrans.
- Next we need to expose this new field on the journal lines form. If you are modifying the General Journal then you would modify the form LedgerJournalTransDaily.
- Next we need to move it from LedgerJournalTrans to the voucher that posts the lines to VendTrans.
- This is done in the class VendVoucher.
- The method newVendVoucherJournal of VendVoucher allows us to pull data from LedgerJournalTrans to VendVoucher.
- VendVoucher extends CustVendVoucher so let us add the field VGRWeBelieve (and the parmVGRWeBelieve method) to the class CustVendVoucher.
- And then basically populate this field in newVendVoucherJournal method.
- Now that we have the data in a class property, we then need to transfer this to VendTrans record.
- VendTrans record is created in the method CustVendVoucher.initCustVendTrans.
- CustVendVoucher class basically transfers all local class field data to a map called CustVendTrans. This map is common to both CustTrans and VendTrans. Since our custom field only exists on VendTrans table, we also need to add it to CustVendTrans map and map it only under VendTrans to the corresponding VendTrans custom field.
- Now we are ready to assign the parmVGRWeBelieve property of CustVendVoucher to CustVendTrans.VGRWeBelieve in the method initCustVendTrans. Here we need to be a bit careful. Since this method is called for both CustTrans and VendTrans (basically customer and vendor account types) we have to only assign it if CustVendTrans is of type VendTrans. We can find that out by using the following condition if(custVendTrans.TabelId == tableNum(VendTrans)) then assign.
Type | Name | Changes |
Table | VendTrans | New field VGRWeBelieve |
Table | LedgerJournalTrans | New field VGRWeBelieve |
Form | LedgerJournalTransDaily | Add the field VGRWeBelieve to the form at appropriate location |
Map | CustVendTrans | Add a new field called VGRWeBelieve Create a mapping under VendTrans node between this field and the field added on vendTrans |
Class | CustVendVoucher | Add the new field vgrWeBelieve to class declaration Add a new parm method as follows public VGRWeBelieve parmVGRWeBelieve(VGRWeBelieve _vgrWeBelieve = vgrWeBelieve) { vgrWeBelieve = _vgrWeBelieve; return vgrWeBelieve; } Modify method initCustVendTrans and add the following code to it If(custVendTrans.TableId == tableNum(VendTrans)) { custVendTrans.VGRWeBelieve = vgrWeBelieve; } |
Class | VendVoucher | Modify the method newVendVoucherJournal and add the following code to it. vendVoucher.parmVGRWeBelieve(_ledgerJournalTrans.VGRWeBelieve) |