[jira] [Commented] (OFBIZ-6763) Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD
[ https://issues.apache.org/jira/browse/OFBIZ-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052372#comment-15052372 ] Michael Powacht commented on OFBIZ-6763: Sounds good Pierra, thanks! Sorry by the way for the triple post. I was facing some internet issues earlier when replying. > Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD > > > Key: OFBIZ-6763 > URL: https://issues.apache.org/jira/browse/OFBIZ-6763 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk >Reporter: Michael Powacht >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Trunk, 14.12.01, 13.07.03 > > Attachments: OFBIZ-6763-AccountingData.patch, screenshot-1.png > > > Hi there, > system incorrectly derives invoice item type INV_FPROD_ITEM (instead of > PINV_FPROD_ITEM, for example) in purchase invoices for purchase orders with > products of type RAW_MATERIAL and GOOD. As a result, the GL account > derivation is incorrect as well where a revenue GL account gets debited > instead of GL "Uninvoiced Shipment Receipts". > The incorrect accounting entry posted is: > DR Revenue (as a result of invoice item type INV_FPROD_ITEM) > CR A/P > The correct entry should be: > DR Uninvoiced Shipment Receipts (derived from PINV_FPROD_ITEM) > CR A/P > It seems the above is caused by missing entries in table > invoice_item_type_map where > INVOICE_ITEM_MAP_KEY should contain RAW_MATERIAL and GOOD and/or > PRODUCT_ORDER_ITEM. > The above symptom does not affect the Goods Receipt Transactions, which gets > correctly posted as: > DR Inventory > CR Uninvoiced Shipment Receipts > Any help is appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6763) Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD
[ https://issues.apache.org/jira/browse/OFBIZ-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052341#comment-15052341 ] Pierre Smits commented on OFBIZ-6763: - [~mpowacht]] You could create a new good type, say TGOOD (Trade Goods) with parentId=GOOD, and use that as the basis for all dependent entities related to inventory, orders, and accounting. > Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD > > > Key: OFBIZ-6763 > URL: https://issues.apache.org/jira/browse/OFBIZ-6763 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk >Reporter: Michael Powacht >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Trunk, 14.12.01, 13.07.03 > > Attachments: OFBIZ-6763-AccountingData.patch, screenshot-1.png > > > Hi there, > system incorrectly derives invoice item type INV_FPROD_ITEM (instead of > PINV_FPROD_ITEM, for example) in purchase invoices for purchase orders with > products of type RAW_MATERIAL and GOOD. As a result, the GL account > derivation is incorrect as well where a revenue GL account gets debited > instead of GL "Uninvoiced Shipment Receipts". > The incorrect accounting entry posted is: > DR Revenue (as a result of invoice item type INV_FPROD_ITEM) > CR A/P > The correct entry should be: > DR Uninvoiced Shipment Receipts (derived from PINV_FPROD_ITEM) > CR A/P > It seems the above is caused by missing entries in table > invoice_item_type_map where > INVOICE_ITEM_MAP_KEY should contain RAW_MATERIAL and GOOD and/or > PRODUCT_ORDER_ITEM. > The above symptom does not affect the Goods Receipt Transactions, which gets > correctly posted as: > DR Inventory > CR Uninvoiced Shipment Receipts > Any help is appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6765) Error on Accounting reports for Cash transactions.
[ https://issues.apache.org/jira/browse/OFBIZ-6765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Douet updated OFBIZ-6765: - Attachment: OFBIZ-6765.patch > Error on Accounting reports for Cash transactions. > -- > > Key: OFBIZ-6765 > URL: https://issues.apache.org/jira/browse/OFBIZ-6765 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk >Reporter: Francis Douet > Attachments: OFBIZ-6765.patch > > > An error is displayed on Accounting reports for Cash transactions: > _Error running script at location > component://accounting/webapp/accounting/WEB-INF/actions/reports/CashFlowStatement.groovy: > java.lang.IllegalArgumentException: argument type mismatch_ > How to reproduce: create a new cash transaction and go to the Cash Flow > Statement report. > eg > https://demo-trunk-ofbiz.apache.org/accounting/control/CashFlowStatement?organizationPartyId=Company > The attached patch addresses the issue. I believe this is related to > OFBIZ-5781. > It also contains another minor issue with the InventoryValuation screen which > we had troubles integrating in our own screens (the organizationPartyId > wasn't assigned correctly). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6765) Error on Accounting reports for Cash transactions.
Francis Douet created OFBIZ-6765: Summary: Error on Accounting reports for Cash transactions. Key: OFBIZ-6765 URL: https://issues.apache.org/jira/browse/OFBIZ-6765 Project: OFBiz Issue Type: Bug Components: accounting Affects Versions: Trunk Reporter: Francis Douet An error is displayed on Accounting reports for Cash transactions: _Error running script at location component://accounting/webapp/accounting/WEB-INF/actions/reports/CashFlowStatement.groovy: java.lang.IllegalArgumentException: argument type mismatch_ How to reproduce: create a new cash transaction and go to the Cash Flow Statement report. eg https://demo-trunk-ofbiz.apache.org/accounting/control/CashFlowStatement?organizationPartyId=Company The attached patch addresses the issue. I believe this is related to OFBIZ-5781. It also contains another minor issue with the InventoryValuation screen which we had troubles integrating in our own screens (the organizationPartyId wasn't assigned correctly). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6764) OrgPartyID in View-Entity AcctgTransEntrySums blank
[
https://issues.apache.org/jira/browse/OFBIZ-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052334#comment-15052334
]
Pierre Smits commented on OFBIZ-6764:
-
Changing the following lines of AcctgTransEntrySums in
/applications/accounting/entitydef/entitymodel.xml will show the desired result:
{code}
{code}
However, there still needs to be some investigation done on the result when
accounting is done for multiple organizationPartyIds both with isPosted values
Y and N.
> OrgPartyID in View-Entity AcctgTransEntrySums blank
>
>
> Key: OFBIZ-6764
> URL: https://issues.apache.org/jira/browse/OFBIZ-6764
> Project: OFBiz
> Issue Type: Bug
> Components: accounting
>Affects Versions: Trunk
> Environment: Win7, Derby DB
>Reporter: Michael Powacht
>Assignee: Pierre Smits
>Priority: Minor
> Labels: entityengine
> Attachments: AcctgTransEntrySums.png, Table Acctg_Trans_Entry.png
>
>
> I installed an OFBiz instance with seed but without demo data. I setup and
> completely configured a new company, organization party ID "ZTASL".
> Postings flow correctly into ACCTG_TRANS_ENTRY with company ZTASL shown in
> ORGANIZATION_PARTY_ID (see screenshot)
> In entity-view AcctgTransEntrySums, however, ORGANIZATION_PARTY_ID and
> IS_POSTED fields are blank (see screenshot)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (OFBIZ-6764) OrgPartyID in View-Entity AcctgTransEntrySums blank
[ https://issues.apache.org/jira/browse/OFBIZ-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6764: --- Assignee: Pierre Smits > OrgPartyID in View-Entity AcctgTransEntrySums blank > > > Key: OFBIZ-6764 > URL: https://issues.apache.org/jira/browse/OFBIZ-6764 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk > Environment: Win7, Derby DB >Reporter: Michael Powacht >Assignee: Pierre Smits >Priority: Minor > Labels: entityengine > Attachments: AcctgTransEntrySums.png, Table Acctg_Trans_Entry.png > > > I installed an OFBiz instance with seed but without demo data. I setup and > completely configured a new company, organization party ID "ZTASL". > Postings flow correctly into ACCTG_TRANS_ENTRY with company ZTASL shown in > ORGANIZATION_PARTY_ID (see screenshot) > In entity-view AcctgTransEntrySums, however, ORGANIZATION_PARTY_ID and > IS_POSTED fields are blank (see screenshot) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6763) Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD
[ https://issues.apache.org/jira/browse/OFBIZ-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052323#comment-15052323 ] Michael Powacht commented on OFBIZ-6763: Many thanks for your clarification Jacopo, I understand. Which product type would you suggest to be assigned to regular physical products for resale? The following product types don't classify in my opinion: Raw Material: Used as input materials for Mfg. Finished Good: The finished output from Mfg. Subassembly: Semifinished ouptput from Mfg. Assigning resale products to product type Finished Goods could lead to wrong requirements generated by MRP, i.e. internal requirements (and production runs) instead of product requirements in the form of proposed purchase orders or will that only happen if a BOM is defined for a Finished Good Product? Thanks, Michael > Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD > > > Key: OFBIZ-6763 > URL: https://issues.apache.org/jira/browse/OFBIZ-6763 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk >Reporter: Michael Powacht >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Trunk, 14.12.01, 13.07.03 > > Attachments: OFBIZ-6763-AccountingData.patch, screenshot-1.png > > > Hi there, > system incorrectly derives invoice item type INV_FPROD_ITEM (instead of > PINV_FPROD_ITEM, for example) in purchase invoices for purchase orders with > products of type RAW_MATERIAL and GOOD. As a result, the GL account > derivation is incorrect as well where a revenue GL account gets debited > instead of GL "Uninvoiced Shipment Receipts". > The incorrect accounting entry posted is: > DR Revenue (as a result of invoice item type INV_FPROD_ITEM) > CR A/P > The correct entry should be: > DR Uninvoiced Shipment Receipts (derived from PINV_FPROD_ITEM) > CR A/P > It seems the above is caused by missing entries in table > invoice_item_type_map where > INVOICE_ITEM_MAP_KEY should contain RAW_MATERIAL and GOOD and/or > PRODUCT_ORDER_ITEM. > The above symptom does not affect the Goods Receipt Transactions, which gets > correctly posted as: > DR Inventory > CR Uninvoiced Shipment Receipts > Any help is appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6763) Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD
[ https://issues.apache.org/jira/browse/OFBIZ-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052322#comment-15052322 ] Michael Powacht commented on OFBIZ-6763: Many thanks for your clarification Jacopo, I understand. Which product type would you suggest to be assigned to regular physical products for resale? The following product types don't classify in my opinion: Raw Material: Used as input materials for Mfg. Finished Good: The finished output from Mfg. Subassembly: Semifinished ouptput from Mfg. Assigning resale products to product type Finished Goods could lead to wrong requirements generated by MRP, i.e. internal requirements (and production runs) instead of product requirements in the form of proposed purchase orders or will that only happen if a BOM is defined for a Finished Good Product? Thanks, Michael > Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD > > > Key: OFBIZ-6763 > URL: https://issues.apache.org/jira/browse/OFBIZ-6763 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk >Reporter: Michael Powacht >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Trunk, 14.12.01, 13.07.03 > > Attachments: OFBIZ-6763-AccountingData.patch, screenshot-1.png > > > Hi there, > system incorrectly derives invoice item type INV_FPROD_ITEM (instead of > PINV_FPROD_ITEM, for example) in purchase invoices for purchase orders with > products of type RAW_MATERIAL and GOOD. As a result, the GL account > derivation is incorrect as well where a revenue GL account gets debited > instead of GL "Uninvoiced Shipment Receipts". > The incorrect accounting entry posted is: > DR Revenue (as a result of invoice item type INV_FPROD_ITEM) > CR A/P > The correct entry should be: > DR Uninvoiced Shipment Receipts (derived from PINV_FPROD_ITEM) > CR A/P > It seems the above is caused by missing entries in table > invoice_item_type_map where > INVOICE_ITEM_MAP_KEY should contain RAW_MATERIAL and GOOD and/or > PRODUCT_ORDER_ITEM. > The above symptom does not affect the Goods Receipt Transactions, which gets > correctly posted as: > DR Inventory > CR Uninvoiced Shipment Receipts > Any help is appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6763) Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD
[ https://issues.apache.org/jira/browse/OFBIZ-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052321#comment-15052321 ] Michael Powacht commented on OFBIZ-6763: Many thanks for your clarification Jacopo, I understand. Which product type would you suggest to be assigned to regular physical products for resale? The following product types don't classify in my opinion: Raw Material: Used as input materials for Mfg. Finished Good: The finished output from Mfg. Subassembly: Semifinished ouptput from Mfg. Assigning resale products to product type Finished Goods could lead to wrong requirements generated by MRP, i.e. internal requirements (and production runs) instead of product requirements in the form of proposed purchase orders or will that only happen if a BOM is defined for a Finished Good Product? Thanks, Michael > Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD > > > Key: OFBIZ-6763 > URL: https://issues.apache.org/jira/browse/OFBIZ-6763 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk >Reporter: Michael Powacht >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Trunk, 14.12.01, 13.07.03 > > Attachments: OFBIZ-6763-AccountingData.patch, screenshot-1.png > > > Hi there, > system incorrectly derives invoice item type INV_FPROD_ITEM (instead of > PINV_FPROD_ITEM, for example) in purchase invoices for purchase orders with > products of type RAW_MATERIAL and GOOD. As a result, the GL account > derivation is incorrect as well where a revenue GL account gets debited > instead of GL "Uninvoiced Shipment Receipts". > The incorrect accounting entry posted is: > DR Revenue (as a result of invoice item type INV_FPROD_ITEM) > CR A/P > The correct entry should be: > DR Uninvoiced Shipment Receipts (derived from PINV_FPROD_ITEM) > CR A/P > It seems the above is caused by missing entries in table > invoice_item_type_map where > INVOICE_ITEM_MAP_KEY should contain RAW_MATERIAL and GOOD and/or > PRODUCT_ORDER_ITEM. > The above symptom does not affect the Goods Receipt Transactions, which gets > correctly posted as: > DR Inventory > CR Uninvoiced Shipment Receipts > Any help is appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6764) OrgPartyID in View-Entity AcctgTransEntrySums blank
[ https://issues.apache.org/jira/browse/OFBIZ-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052318#comment-15052318 ] Pierre Smits commented on OFBIZ-6764: - I see the same occurring in demo-trunk-ofbiz.apache.org, see http://demo-trunk-ofbiz.apache.org/webtools/control/FindGeneric?entityName=AcctgTransEntrySums&find=true&searchOptions_collapsed=true&VIEW_SIZE=200&VIEW_INDEX=0 vs http://demo-trunk-ofbiz.apache.org/webtools/control/FindGeneric?entityName=AcctgTransEntry > OrgPartyID in View-Entity AcctgTransEntrySums blank > > > Key: OFBIZ-6764 > URL: https://issues.apache.org/jira/browse/OFBIZ-6764 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk > Environment: Win7, Derby DB >Reporter: Michael Powacht >Priority: Minor > Labels: entityengine > Attachments: AcctgTransEntrySums.png, Table Acctg_Trans_Entry.png > > > I installed an OFBiz instance with seed but without demo data. I setup and > completely configured a new company, organization party ID "ZTASL". > Postings flow correctly into ACCTG_TRANS_ENTRY with company ZTASL shown in > ORGANIZATION_PARTY_ID (see screenshot) > In entity-view AcctgTransEntrySums, however, ORGANIZATION_PARTY_ID and > IS_POSTED fields are blank (see screenshot) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6763) Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD
[ https://issues.apache.org/jira/browse/OFBIZ-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052299#comment-15052299 ] Jacopo Cappellato commented on OFBIZ-6763: -- Thanks for your work [~mpowacht]. As regards the type named "GOOD", it is a special type that is not supposed to be used in orders; in fact it is an "abstract" type that is parent type for several other types including physical and non physical items like "raw materials", "subassembly", "digital goods" etc.. In my opinion a better fix would be that of preventing to assign this type to a product directly: the check could be done when the product data is created/updated and when the product is added to an order (to catch wrong product data imported into the system with external tools). > Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD > > > Key: OFBIZ-6763 > URL: https://issues.apache.org/jira/browse/OFBIZ-6763 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk >Reporter: Michael Powacht >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Trunk, 14.12.01, 13.07.03 > > Attachments: OFBIZ-6763-AccountingData.patch, screenshot-1.png > > > Hi there, > system incorrectly derives invoice item type INV_FPROD_ITEM (instead of > PINV_FPROD_ITEM, for example) in purchase invoices for purchase orders with > products of type RAW_MATERIAL and GOOD. As a result, the GL account > derivation is incorrect as well where a revenue GL account gets debited > instead of GL "Uninvoiced Shipment Receipts". > The incorrect accounting entry posted is: > DR Revenue (as a result of invoice item type INV_FPROD_ITEM) > CR A/P > The correct entry should be: > DR Uninvoiced Shipment Receipts (derived from PINV_FPROD_ITEM) > CR A/P > It seems the above is caused by missing entries in table > invoice_item_type_map where > INVOICE_ITEM_MAP_KEY should contain RAW_MATERIAL and GOOD and/or > PRODUCT_ORDER_ITEM. > The above symptom does not affect the Goods Receipt Transactions, which gets > correctly posted as: > DR Inventory > CR Uninvoiced Shipment Receipts > Any help is appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6764) OrgPartyID in View-Entity AcctgTransEntrySums blank
[ https://issues.apache.org/jira/browse/OFBIZ-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Powacht updated OFBIZ-6764: --- Description: I installed an OFBiz instance with seed but without demo data. I setup and completely configured a new company, organization party ID "ZTASL". Postings flow correctly into ACCTG_TRANS_ENTRY with company ZTASL shown in ORGANIZATION_PARTY_ID (see screenshot) In entity-view AcctgTransEntrySums, however, ORGANIZATION_PARTY_ID and IS_POSTED fields are blank (see screenshot) was: I installed an OFBiz instance with seed but without demo data. I setup and completely configured a new company, organization party ID "ZTASL". Postings flow correctly into ACCTG_TRANS_ENTRY with company ZTASL shown in ORGANIZATION_PARTY_ID. In entity-view AcctgTransEntrySums, however, ORGANIZATION_PARTY_ID and IS_POSTED fields are blank. > OrgPartyID in View-Entity AcctgTransEntrySums blank > > > Key: OFBIZ-6764 > URL: https://issues.apache.org/jira/browse/OFBIZ-6764 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk > Environment: Win7, Derby DB >Reporter: Michael Powacht >Priority: Minor > Labels: entityengine > Attachments: AcctgTransEntrySums.png, Table Acctg_Trans_Entry.png > > > I installed an OFBiz instance with seed but without demo data. I setup and > completely configured a new company, organization party ID "ZTASL". > Postings flow correctly into ACCTG_TRANS_ENTRY with company ZTASL shown in > ORGANIZATION_PARTY_ID (see screenshot) > In entity-view AcctgTransEntrySums, however, ORGANIZATION_PARTY_ID and > IS_POSTED fields are blank (see screenshot) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6764) OrgPartyID in View-Entity AcctgTransEntrySums blank
[ https://issues.apache.org/jira/browse/OFBIZ-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Powacht updated OFBIZ-6764: --- Attachment: Table Acctg_Trans_Entry.png > OrgPartyID in View-Entity AcctgTransEntrySums blank > > > Key: OFBIZ-6764 > URL: https://issues.apache.org/jira/browse/OFBIZ-6764 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk > Environment: Win7, Derby DB >Reporter: Michael Powacht >Priority: Minor > Labels: entityengine > Attachments: AcctgTransEntrySums.png, Table Acctg_Trans_Entry.png > > > I installed an OFBiz instance with seed but without demo data. I setup and > completely configured a new company, organization party ID "ZTASL". > Postings flow correctly into ACCTG_TRANS_ENTRY with company ZTASL shown in > ORGANIZATION_PARTY_ID. > In entity-view AcctgTransEntrySums, however, ORGANIZATION_PARTY_ID and > IS_POSTED fields are blank. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6764) OrgPartyID in View-Entity AcctgTransEntrySums blank
[ https://issues.apache.org/jira/browse/OFBIZ-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Powacht updated OFBIZ-6764: --- Attachment: AcctgTransEntrySums.png > OrgPartyID in View-Entity AcctgTransEntrySums blank > > > Key: OFBIZ-6764 > URL: https://issues.apache.org/jira/browse/OFBIZ-6764 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk > Environment: Win7, Derby DB >Reporter: Michael Powacht >Priority: Minor > Labels: entityengine > Attachments: AcctgTransEntrySums.png > > > I installed an OFBiz instance with seed but without demo data. I setup and > completely configured a new company, organization party ID "ZTASL". > Postings flow correctly into ACCTG_TRANS_ENTRY with company ZTASL shown in > ORGANIZATION_PARTY_ID. > In entity-view AcctgTransEntrySums, however, ORGANIZATION_PARTY_ID and > IS_POSTED fields are blank. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6764) OrgPartyID in View-Entity AcctgTransEntrySums blank
Michael Powacht created OFBIZ-6764: -- Summary: OrgPartyID in View-Entity AcctgTransEntrySums blank Key: OFBIZ-6764 URL: https://issues.apache.org/jira/browse/OFBIZ-6764 Project: OFBiz Issue Type: Bug Components: accounting Affects Versions: Trunk Environment: Win7, Derby DB Reporter: Michael Powacht Priority: Minor I installed an OFBiz instance with seed but without demo data. I setup and completely configured a new company, organization party ID "ZTASL". Postings flow correctly into ACCTG_TRANS_ENTRY with company ZTASL shown in ORGANIZATION_PARTY_ID. In entity-view AcctgTransEntrySums, however, ORGANIZATION_PARTY_ID and IS_POSTED fields are blank. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6762) Show JGrowl alert when using ajax submit form
[ https://issues.apache.org/jira/browse/OFBIZ-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhang closed OFBIZ-6762. Resolution: Fixed Fix Version/s: Trunk > Show JGrowl alert when using ajax submit form > - > > Key: OFBIZ-6762 > URL: https://issues.apache.org/jira/browse/OFBIZ-6762 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Wei Zhang >Priority: Minor > Fix For: Trunk > > Attachments: ajaxSubmitFormAlert.png, ajaxSubmitFormJGrowlAlert.png > > > The current alert for ajax submit form is like below > !ajaxSubmitFormAlert.png! > and the improved alert should be > !ajaxSubmitFormJGrowlAlert.png! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6763) Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD
[ https://issues.apache.org/jira/browse/OFBIZ-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051982#comment-15051982 ] Michael Powacht commented on OFBIZ-6763: Thanks to all for your prompt actions, which is truly impressive! Products with product type ID "RAW_MATERIAL" work as expected now but I still face issues with products assigned to product_type_id "GOOD" where the purchase invoice still erroneously derives item type INV_FPROD_ITEM and thereby a revenue GL. I am planning to assign product_type_id GOOD to physical trading products (i.e they are not of type FINISHED_GOOD, DIGITAL_GOOD or FINDIG_GOOD) Did I miss something? Thanks again, Michael > Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD > > > Key: OFBIZ-6763 > URL: https://issues.apache.org/jira/browse/OFBIZ-6763 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk >Reporter: Michael Powacht >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Trunk, 14.12.01, 13.07.03 > > Attachments: OFBIZ-6763-AccountingData.patch, screenshot-1.png > > > Hi there, > system incorrectly derives invoice item type INV_FPROD_ITEM (instead of > PINV_FPROD_ITEM, for example) in purchase invoices for purchase orders with > products of type RAW_MATERIAL and GOOD. As a result, the GL account > derivation is incorrect as well where a revenue GL account gets debited > instead of GL "Uninvoiced Shipment Receipts". > The incorrect accounting entry posted is: > DR Revenue (as a result of invoice item type INV_FPROD_ITEM) > CR A/P > The correct entry should be: > DR Uninvoiced Shipment Receipts (derived from PINV_FPROD_ITEM) > CR A/P > It seems the above is caused by missing entries in table > invoice_item_type_map where > INVOICE_ITEM_MAP_KEY should contain RAW_MATERIAL and GOOD and/or > PRODUCT_ORDER_ITEM. > The above symptom does not affect the Goods Receipt Transactions, which gets > correctly posted as: > DR Inventory > CR Uninvoiced Shipment Receipts > Any help is appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-610) Remove all instances of 'required-permissions' usage in service definition files.
[ https://issues.apache.org/jira/browse/OFBIZ-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051633#comment-15051633 ] Jacques Le Roux commented on OFBIZ-610: --- Deprecation was only about using "required-permissions' in service definition files. It seems this idea has been abandonned, see at least OFBIZ-3632 > Remove all instances of 'required-permissions' usage in service definition > files. > - > > Key: OFBIZ-610 > URL: https://issues.apache.org/jira/browse/OFBIZ-610 > Project: OFBiz > Issue Type: Sub-task > Components: framework, order, product >Reporter: Andrew Zeneski >Assignee: Andrew Zeneski > Fix For: Trunk > > > There are currently 61 instances of service definitions which use the now > deprecated tag. These definitions should all be > updated and new permissions services implemented (as needed) to use the new > tag. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-610) Remove all instances of 'required-permissions' usage in service definition files.
[
https://issues.apache.org/jira/browse/OFBIZ-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051460#comment-15051460
]
Forrest Rae edited comment on OFBIZ-610 at 12/10/15 6:56 PM:
-
I know this is quite old, but did you ever consider a case where you'd need to
do:
{code:xml}
{code}
I just spent weeks implementing something like this, and then stumbled across
this, showing that is deprecated.
was (Author: f...@14x.net):
I know this is quite old, but did you ever consider a case where you'd need to
do:
{code|borderStyle=solid}
{code}
I just spent weeks implementing something like this, and then stumbled across
this, showing that is deprecated.
> Remove all instances of 'required-permissions' usage in service definition
> files.
> -
>
> Key: OFBIZ-610
> URL: https://issues.apache.org/jira/browse/OFBIZ-610
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework, order, product
>Reporter: Andrew Zeneski
>Assignee: Andrew Zeneski
> Fix For: Trunk
>
>
> There are currently 61 instances of service definitions which use the now
> deprecated tag. These definitions should all be
> updated and new permissions services implemented (as needed) to use the new
> tag.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-610) Remove all instances of 'required-permissions' usage in service definition files.
[
https://issues.apache.org/jira/browse/OFBIZ-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051460#comment-15051460
]
Forrest Rae commented on OFBIZ-610:
---
I know this is quite old, but did you ever consider a case where you'd need to
do:
{code|borderStyle=solid}
{code}
I just spent weeks implementing something like this, and then stumbled across
this, showing that is deprecated.
> Remove all instances of 'required-permissions' usage in service definition
> files.
> -
>
> Key: OFBIZ-610
> URL: https://issues.apache.org/jira/browse/OFBIZ-610
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework, order, product
>Reporter: Andrew Zeneski
>Assignee: Andrew Zeneski
> Fix For: Trunk
>
>
> There are currently 61 instances of service definitions which use the now
> deprecated tag. These definitions should all be
> updated and new permissions services implemented (as needed) to use the new
> tag.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (OFBIZ-6763) Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD
[ https://issues.apache.org/jira/browse/OFBIZ-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-6763. -- Resolution: Fixed Fix Version/s: 13.07.03 14.12.01 Thansk Michael, Rupert and Pierre, Pierre your patch is in trunk r1719094 R14.12 r1719095 R13.07 r1719095 R12.04 was confusing, I did not backport > Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD > > > Key: OFBIZ-6763 > URL: https://issues.apache.org/jira/browse/OFBIZ-6763 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk >Reporter: Michael Powacht >Assignee: Jacques Le Roux >Priority: Minor > Fix For: 14.12.01, 13.07.03, Trunk > > Attachments: OFBIZ-6763-AccountingData.patch, screenshot-1.png > > > Hi there, > system incorrectly derives invoice item type INV_FPROD_ITEM (instead of > PINV_FPROD_ITEM, for example) in purchase invoices for purchase orders with > products of type RAW_MATERIAL and GOOD. As a result, the GL account > derivation is incorrect as well where a revenue GL account gets debited > instead of GL "Uninvoiced Shipment Receipts". > The incorrect accounting entry posted is: > DR Revenue (as a result of invoice item type INV_FPROD_ITEM) > CR A/P > The correct entry should be: > DR Uninvoiced Shipment Receipts (derived from PINV_FPROD_ITEM) > CR A/P > It seems the above is caused by missing entries in table > invoice_item_type_map where > INVOICE_ITEM_MAP_KEY should contain RAW_MATERIAL and GOOD and/or > PRODUCT_ORDER_ITEM. > The above symptom does not affect the Goods Receipt Transactions, which gets > correctly posted as: > DR Inventory > CR Uninvoiced Shipment Receipts > Any help is appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-6763) Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD
[ https://issues.apache.org/jira/browse/OFBIZ-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-6763: -- Assignee: Jacques Le Roux (was: Pierre Smits) > Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD > > > Key: OFBIZ-6763 > URL: https://issues.apache.org/jira/browse/OFBIZ-6763 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk >Reporter: Michael Powacht >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-6763-AccountingData.patch, screenshot-1.png > > > Hi there, > system incorrectly derives invoice item type INV_FPROD_ITEM (instead of > PINV_FPROD_ITEM, for example) in purchase invoices for purchase orders with > products of type RAW_MATERIAL and GOOD. As a result, the GL account > derivation is incorrect as well where a revenue GL account gets debited > instead of GL "Uninvoiced Shipment Receipts". > The incorrect accounting entry posted is: > DR Revenue (as a result of invoice item type INV_FPROD_ITEM) > CR A/P > The correct entry should be: > DR Uninvoiced Shipment Receipts (derived from PINV_FPROD_ITEM) > CR A/P > It seems the above is caused by missing entries in table > invoice_item_type_map where > INVOICE_ITEM_MAP_KEY should contain RAW_MATERIAL and GOOD and/or > PRODUCT_ORDER_ITEM. > The above symptom does not affect the Goods Receipt Transactions, which gets > correctly posted as: > DR Inventory > CR Uninvoiced Shipment Receipts > Any help is appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6763) Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD
[ https://issues.apache.org/jira/browse/OFBIZ-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050959#comment-15050959 ] Michael Powacht commented on OFBIZ-6763: Thanks for your prompt action Rupert. Will check it out tomorrow. Sent from my Samsung Galaxy smartphone. Original message From: "Rupert Howell (JIRA)" Date: 12/10/2015 19:30 (GMT+07:00) To: Michael Powacht Subject: [jira] [Commented] (OFBIZ-6763) Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD [ https://issues.apache.org/jira/browse/OFBIZ-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050910#comment-15050910 ] Rupert Howell commented on OFBIZ-6763: -- Hi Michael It appears that there is some seed data missing. The below data will add a new invoice item type and map raw materials to the correct account. GOOD is already mapped however so that should be picking up PINV_FPROD_ITEM -- This message was sent by Atlassian JIRA (v6.3.4#6332) > Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD > > > Key: OFBIZ-6763 > URL: https://issues.apache.org/jira/browse/OFBIZ-6763 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk >Reporter: Michael Powacht >Assignee: Pierre Smits >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-6763-AccountingData.patch, screenshot-1.png > > > Hi there, > system incorrectly derives invoice item type INV_FPROD_ITEM (instead of > PINV_FPROD_ITEM, for example) in purchase invoices for purchase orders with > products of type RAW_MATERIAL and GOOD. As a result, the GL account > derivation is incorrect as well where a revenue GL account gets debited > instead of GL "Uninvoiced Shipment Receipts". > The incorrect accounting entry posted is: > DR Revenue (as a result of invoice item type INV_FPROD_ITEM) > CR A/P > The correct entry should be: > DR Uninvoiced Shipment Receipts (derived from PINV_FPROD_ITEM) > CR A/P > It seems the above is caused by missing entries in table > invoice_item_type_map where > INVOICE_ITEM_MAP_KEY should contain RAW_MATERIAL and GOOD and/or > PRODUCT_ORDER_ITEM. > The above symptom does not affect the Goods Receipt Transactions, which gets > correctly posted as: > DR Inventory > CR Uninvoiced Shipment Receipts > Any help is appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (OFBIZ-6677) Show out of stock products in STORE --- CATALOG Manager doesn't work
[ https://issues.apache.org/jira/browse/OFBIZ-6677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reopened OFBIZ-6677: > Show out of stock products in STORE --- CATALOG Manager doesn't work > > > Key: OFBIZ-6677 > URL: https://issues.apache.org/jira/browse/OFBIZ-6677 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/ecommerce >Affects Versions: Release Branch 14.12 >Reporter: Heidi Dehaes >Assignee: Divesh Dutta > > Show out of stock products > in STORE > in Catalog Manager > in Catalog > doesn't work. > No products at all are viewed when "out of stock products" is equal to "N". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6677) Show out of stock products in STORE --- CATALOG Manager doesn't work
[ https://issues.apache.org/jira/browse/OFBIZ-6677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-6677. -- Resolution: Not A Problem > Show out of stock products in STORE --- CATALOG Manager doesn't work > > > Key: OFBIZ-6677 > URL: https://issues.apache.org/jira/browse/OFBIZ-6677 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/ecommerce >Affects Versions: Release Branch 14.12 >Reporter: Heidi Dehaes >Assignee: Divesh Dutta > > Show out of stock products > in STORE > in Catalog Manager > in Catalog > doesn't work. > No products at all are viewed when "out of stock products" is equal to "N". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6760) Move all entity definitions from the applications components into a separate one
[ https://issues.apache.org/jira/browse/OFBIZ-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050938#comment-15050938 ] Jacques Le Roux commented on OFBIZ-6760: We should not forget to update https://cwiki.apache.org/confluence/display/OFBIZ > Move all entity definitions from the applications components into a separate > one > > > Key: OFBIZ-6760 > URL: https://issues.apache.org/jira/browse/OFBIZ-6760 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Jacques Le Roux > Fix For: Upcoming Branch > > > See this thread for a previous discussion: > http://markmail.org/message/sfdm22wfy3fulpyb -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6760) Move all entity definitions from the applications components into a separate one
[ https://issues.apache.org/jira/browse/OFBIZ-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050936#comment-15050936 ] Jacques Le Roux commented on OFBIZ-6760: Yes please do, that's my opinion > Move all entity definitions from the applications components into a separate > one > > > Key: OFBIZ-6760 > URL: https://issues.apache.org/jira/browse/OFBIZ-6760 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Jacques Le Roux > Fix For: Upcoming Branch > > > See this thread for a previous discussion: > http://markmail.org/message/sfdm22wfy3fulpyb -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6763) Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD
[ https://issues.apache.org/jira/browse/OFBIZ-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-6763: Attachment: OFBIZ-6763-AccountingData.patch This patch addresses the issue. > Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD > > > Key: OFBIZ-6763 > URL: https://issues.apache.org/jira/browse/OFBIZ-6763 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk >Reporter: Michael Powacht >Assignee: Pierre Smits >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-6763-AccountingData.patch, screenshot-1.png > > > Hi there, > system incorrectly derives invoice item type INV_FPROD_ITEM (instead of > PINV_FPROD_ITEM, for example) in purchase invoices for purchase orders with > products of type RAW_MATERIAL and GOOD. As a result, the GL account > derivation is incorrect as well where a revenue GL account gets debited > instead of GL "Uninvoiced Shipment Receipts". > The incorrect accounting entry posted is: > DR Revenue (as a result of invoice item type INV_FPROD_ITEM) > CR A/P > The correct entry should be: > DR Uninvoiced Shipment Receipts (derived from PINV_FPROD_ITEM) > CR A/P > It seems the above is caused by missing entries in table > invoice_item_type_map where > INVOICE_ITEM_MAP_KEY should contain RAW_MATERIAL and GOOD and/or > PRODUCT_ORDER_ITEM. > The above symptom does not affect the Goods Receipt Transactions, which gets > correctly posted as: > DR Inventory > CR Uninvoiced Shipment Receipts > Any help is appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-6763) Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD
[ https://issues.apache.org/jira/browse/OFBIZ-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6763: --- Assignee: Pierre Smits > Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD > > > Key: OFBIZ-6763 > URL: https://issues.apache.org/jira/browse/OFBIZ-6763 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk >Reporter: Michael Powacht >Assignee: Pierre Smits >Priority: Minor > Fix For: Trunk > > Attachments: screenshot-1.png > > > Hi there, > system incorrectly derives invoice item type INV_FPROD_ITEM (instead of > PINV_FPROD_ITEM, for example) in purchase invoices for purchase orders with > products of type RAW_MATERIAL and GOOD. As a result, the GL account > derivation is incorrect as well where a revenue GL account gets debited > instead of GL "Uninvoiced Shipment Receipts". > The incorrect accounting entry posted is: > DR Revenue (as a result of invoice item type INV_FPROD_ITEM) > CR A/P > The correct entry should be: > DR Uninvoiced Shipment Receipts (derived from PINV_FPROD_ITEM) > CR A/P > It seems the above is caused by missing entries in table > invoice_item_type_map where > INVOICE_ITEM_MAP_KEY should contain RAW_MATERIAL and GOOD and/or > PRODUCT_ORDER_ITEM. > The above symptom does not affect the Goods Receipt Transactions, which gets > correctly posted as: > DR Inventory > CR Uninvoiced Shipment Receipts > Any help is appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6763) Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD
[ https://issues.apache.org/jira/browse/OFBIZ-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050910#comment-15050910 ] Rupert Howell commented on OFBIZ-6763: -- Hi Michael It appears that there is some seed data missing. The below data will add a new invoice item type and map raw materials to the correct account. GOOD is already mapped however so that should be picking up PINV_FPROD_ITEM > Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD > > > Key: OFBIZ-6763 > URL: https://issues.apache.org/jira/browse/OFBIZ-6763 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk >Reporter: Michael Powacht >Priority: Minor > Fix For: Trunk > > Attachments: screenshot-1.png > > > Hi there, > system incorrectly derives invoice item type INV_FPROD_ITEM (instead of > PINV_FPROD_ITEM, for example) in purchase invoices for purchase orders with > products of type RAW_MATERIAL and GOOD. As a result, the GL account > derivation is incorrect as well where a revenue GL account gets debited > instead of GL "Uninvoiced Shipment Receipts". > The incorrect accounting entry posted is: > DR Revenue (as a result of invoice item type INV_FPROD_ITEM) > CR A/P > The correct entry should be: > DR Uninvoiced Shipment Receipts (derived from PINV_FPROD_ITEM) > CR A/P > It seems the above is caused by missing entries in table > invoice_item_type_map where > INVOICE_ITEM_MAP_KEY should contain RAW_MATERIAL and GOOD and/or > PRODUCT_ORDER_ITEM. > The above symptom does not affect the Goods Receipt Transactions, which gets > correctly posted as: > DR Inventory > CR Uninvoiced Shipment Receipts > Any help is appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6763) Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD
[ https://issues.apache.org/jira/browse/OFBIZ-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Powacht updated OFBIZ-6763: --- Attachment: screenshot-1.png > Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD > > > Key: OFBIZ-6763 > URL: https://issues.apache.org/jira/browse/OFBIZ-6763 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk >Reporter: Michael Powacht >Priority: Minor > Fix For: Trunk > > Attachments: screenshot-1.png > > > Hi there, > system incorrectly derives invoice item type INV_FPROD_ITEM (instead of > PINV_FPROD_ITEM, for example) in purchase invoices for purchase orders with > products of type RAW_MATERIAL and GOOD. As a result, the GL account > derivation is incorrect as well where a revenue GL account gets debited > instead of GL "Uninvoiced Shipment Receipts". > The incorrect accounting entry posted is: > DR Revenue (as a result of invoice item type INV_FPROD_ITEM) > CR A/P > The correct entry should be: > DR Uninvoiced Shipment Receipts (derived from PINV_FPROD_ITEM) > CR A/P > It seems the above is caused by missing entries in table > invoice_item_type_map where > INVOICE_ITEM_MAP_KEY should contain RAW_MATERIAL and GOOD and/or > PRODUCT_ORDER_ITEM. > The above symptom does not affect the Goods Receipt Transactions, which gets > correctly posted as: > DR Inventory > CR Uninvoiced Shipment Receipts > Any help is appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6763) Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD
[ https://issues.apache.org/jira/browse/OFBIZ-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Powacht updated OFBIZ-6763: --- Component/s: (was: order) accounting > Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD > > > Key: OFBIZ-6763 > URL: https://issues.apache.org/jira/browse/OFBIZ-6763 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk >Reporter: Michael Powacht >Priority: Minor > Fix For: Trunk > > > Hi there, > system incorrectly derives invoice item type INV_FPROD_ITEM (instead of > PINV_FPROD_ITEM, for example) in purchase invoices for purchase orders with > products of type RAW_MATERIAL and GOOD. As a result, the GL account > derivation is incorrect as well where a revenue GL account gets debited > instead of GL "Uninvoiced Shipment Receipts". > The incorrect accounting entry posted is: > DR Revenue (as a result of invoice item type INV_FPROD_ITEM) > CR A/P > The correct entry should be: > DR Uninvoiced Shipment Receipts (derived from PINV_FPROD_ITEM) > CR A/P > It seems the above is caused by missing entries in table > invoice_item_type_map where > INVOICE_ITEM_MAP_KEY should contain RAW_MATERIAL and GOOD and/or > PRODUCT_ORDER_ITEM. > The above symptom does not affect the Goods Receipt Transactions, which gets > correctly posted as: > DR Inventory > CR Uninvoiced Shipment Receipts > Any help is appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6763) Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD
Michael Powacht created OFBIZ-6763: -- Summary: Wrong purchase invoice item type for product type IDs RAW_MATERIAL, GOOD Key: OFBIZ-6763 URL: https://issues.apache.org/jira/browse/OFBIZ-6763 Project: OFBiz Issue Type: Bug Components: order Affects Versions: Trunk Reporter: Michael Powacht Priority: Minor Fix For: Trunk Hi there, system incorrectly derives invoice item type INV_FPROD_ITEM (instead of PINV_FPROD_ITEM, for example) in purchase invoices for purchase orders with products of type RAW_MATERIAL and GOOD. As a result, the GL account derivation is incorrect as well where a revenue GL account gets debited instead of GL "Uninvoiced Shipment Receipts". The incorrect accounting entry posted is: DR Revenue (as a result of invoice item type INV_FPROD_ITEM) CR A/P The correct entry should be: DR Uninvoiced Shipment Receipts (derived from PINV_FPROD_ITEM) CR A/P It seems the above is caused by missing entries in table invoice_item_type_map where INVOICE_ITEM_MAP_KEY should contain RAW_MATERIAL and GOOD and/or PRODUCT_ORDER_ITEM. The above symptom does not affect the Goods Receipt Transactions, which gets correctly posted as: DR Inventory CR Uninvoiced Shipment Receipts Any help is appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6760) Move all entity definitions from the applications components into a separate one
[ https://issues.apache.org/jira/browse/OFBIZ-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050637#comment-15050637 ] Jacopo Cappellato commented on OFBIZ-6760: -- I have been running my local instance for a while without noticing any issues; however I didn't share this work with others before nor I have used these modifications in any production instance. However, if we like the direction, I would be happy to commit it as I don't see big risks involved. > Move all entity definitions from the applications components into a separate > one > > > Key: OFBIZ-6760 > URL: https://issues.apache.org/jira/browse/OFBIZ-6760 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Jacques Le Roux > Fix For: Upcoming Branch > > > See this thread for a previous discussion: > http://markmail.org/message/sfdm22wfy3fulpyb -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-6696) Remove tooltip="${uiLabelMap.CommonNotModifRecreat}" from display fields
[
https://issues.apache.org/jira/browse/OFBIZ-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050593#comment-15050593
]
Jacques Le Roux edited comment on OFBIZ-6696 at 12/10/15 11:01 AM:
---
The risk is low, but the advantage is also low. Don't break the rule when it's
not really needed I'd say, you know the story of the wolf?
was (Author: jacques.le.roux):
The risk is low, but the advantage is also low. Don't break the rule when it's
not really neeed I'd say, you know the story of the wolf?
> Remove tooltip="${uiLabelMap.CommonNotModifRecreat}" from display fields
>
>
> Key: OFBIZ-6696
> URL: https://issues.apache.org/jira/browse/OFBIZ-6696
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL APPLICATIONS
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Nicolas Malin
>Priority: Trivial
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-6696-tooltip.patch
>
>
> Many display fields have the
> {code}tooltip="${uiLabelMap.CommonNotModifRecreat}"{code} associated to a id
> field. But this field is only informative when the user wants to create a new
> record. Every other time it is superfluous.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-6696) Remove tooltip="${uiLabelMap.CommonNotModifRecreat}" from display fields
[
https://issues.apache.org/jira/browse/OFBIZ-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050593#comment-15050593
]
Jacques Le Roux commented on OFBIZ-6696:
The risk is low, but the advantage is also low. Don't break the rule when it's
not really neeed I'd say, you know the story of the wolf?
> Remove tooltip="${uiLabelMap.CommonNotModifRecreat}" from display fields
>
>
> Key: OFBIZ-6696
> URL: https://issues.apache.org/jira/browse/OFBIZ-6696
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL APPLICATIONS
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Nicolas Malin
>Priority: Trivial
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-6696-tooltip.patch
>
>
> Many display fields have the
> {code}tooltip="${uiLabelMap.CommonNotModifRecreat}"{code} associated to a id
> field. But this field is only informative when the user wants to create a new
> record. Every other time it is superfluous.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-6696) Remove tooltip="${uiLabelMap.CommonNotModifRecreat}" from display fields
[
https://issues.apache.org/jira/browse/OFBIZ-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050585#comment-15050585
]
Pierre Smits commented on OFBIZ-6696:
-
Waiting to incorporate this in the next release (branch) and not in 14.12 means
that this won't be available to adopters within 2 years. That is a long time.
As we are still not having a release out regarding the 14.12 branch, I would
say: help our adopters to avoid addressing this themselves. The risk is low.
> Remove tooltip="${uiLabelMap.CommonNotModifRecreat}" from display fields
>
>
> Key: OFBIZ-6696
> URL: https://issues.apache.org/jira/browse/OFBIZ-6696
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL APPLICATIONS
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Nicolas Malin
>Priority: Trivial
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-6696-tooltip.patch
>
>
> Many display fields have the
> {code}tooltip="${uiLabelMap.CommonNotModifRecreat}"{code} associated to a id
> field. But this field is only informative when the user wants to create a new
> record. Every other time it is superfluous.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Removing Javolution and resolving sax implementation - OFBIZ-5169
Hi everyone, After studying EntitySaxReader.java to figure out a way to remove javolution dependency I realized that the whole interface is dependent on javolution, so even if I switch to xerces or other implementations I am still left with dependencies that require a major rewrite. What makes things even worse is that many parts of the framework depend on this class. I think the class implementation is really ugly and hard to comprehend with no docs to interpret the functionality. Furthermore, many of the public methods should not be public and the calls within the class are like spaghetti. Can anyone guide me as to whether changing the signature is a problem for the dependencies within the framework? I know for example EntityDataLoader, EntityData, and the web tools in WebToolsServices depend on it. So this will be a big change and I'm not sure if this might break something else. Any clue from the seniors here on how to approach this. I got a major headache looking at that darn thing? Taher Alkhateeb On Fri, Oct 23, 2015 at 5:42 PM, Adrian Crum < adrian.c...@sandglass-software.com> wrote: > https://docs.oracle.com/javase/tutorial/jaxp/sax/parsing.html > > https://issues.apache.org/jira/browse/OFBIZ-2390 > > Adrian Crum > Sandglass Software > www.sandglass-software.com > > On 10/23/2015 7:20 AM, Taher Alkhateeb wrote: > >> Hi Adrian, >> >> I believe xerces also already exists in the project. Which one should I >> prefer or use? Are there any existing utilities or things that would >> shortcut my work? >> >> Taher Alkhateeb >> >> - Original Message - >> >> From: "Adrian Crum" >> To: dev@ofbiz.apache.org >> Sent: Friday, 23 October, 2015 5:02:51 PM >> Subject: Re: Removing Javolution and resolving sax implementation - >> OFBIZ-5169 >> >> Xerces would be fine, but we already have a pull parser in the project >> (an XStream dependency): >> >> http://www.extreme.indiana.edu/xgws/xsoap/xpp/ >> >> Adrian Crum >> Sandglass Software >> www.sandglass-software.com >> >> On 10/23/2015 1:10 AM, Taher Alkhateeb wrote: >> >>> Hi everyone, >>> >>> I need some help and guidance. I removed all remaining references to >>> Javolution from the framework except for this one annoying dependency, and >>> we cannot remove the jar before getting a different implementation. >>> >>> So the code in EntitySaxReader.java depends on >>> _javolution.xml.sax.XMLReaderImpl_ for implementing the Sax parser for >>> importing data to the framework. And my question is, what is the >>> recommended library replacement? I am thinking of using >>> _org.apache.xerces.parsers.SAXParser_. Am I on the right path or do we have >>> other preferences for XML parsing in OFBiz? >>> >>> Thank you for your help! >>> >>> Taher Alkhateeb >>> >>> >> >>
[jira] [Commented] (OFBIZ-6760) Move all entity definitions from the applications components into a separate one
[ https://issues.apache.org/jira/browse/OFBIZ-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050465#comment-15050465 ] Jacques Le Roux commented on OFBIZ-6760: I of course made some manual tests (after the successul automated tests) and all smoohtly works, pretty neat solution! I guess you are already using it Jacopo, aren't you? > Move all entity definitions from the applications components into a separate > one > > > Key: OFBIZ-6760 > URL: https://issues.apache.org/jira/browse/OFBIZ-6760 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Jacques Le Roux > Fix For: Upcoming Branch > > > See this thread for a previous discussion: > http://markmail.org/message/sfdm22wfy3fulpyb -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6760) Move all entity definitions from the applications components into a separate one
[ https://issues.apache.org/jira/browse/OFBIZ-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050417#comment-15050417 ] Jacques Le Roux commented on OFBIZ-6760: This is indeed very simple. I see no reasons why we should not go this way. We should then update this page https://cwiki.apache.org/confluence/display/OFBIZ/Component+and+Component+Set+Dependencies when of course only data model dependencies are concerned > Move all entity definitions from the applications components into a separate > one > > > Key: OFBIZ-6760 > URL: https://issues.apache.org/jira/browse/OFBIZ-6760 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Jacques Le Roux > Fix For: Upcoming Branch > > > See this thread for a previous discussion: > http://markmail.org/message/sfdm22wfy3fulpyb -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6759) Improves HTTP header
[ https://issues.apache.org/jira/browse/OFBIZ-6759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050389#comment-15050389 ] Pierre Smits commented on OFBIZ-6759: - Maybe I must have been, but I guess it also has to do with getting used to a new pair of glasses... ;-) > Improves HTTP header > > > Key: OFBIZ-6759 > URL: https://issues.apache.org/jira/browse/OFBIZ-6759 > Project: OFBiz > Issue Type: Improvement > Components: framework, themes >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > > After looking at https://cyh.herokuapp.com/cyh and > https://www.owasp.org/index.php/List_of_useful_HTTP_headers and checking what > we currently use as/in HTTP header fields in themes and other places I think > it's time to update the header. > The idea is to create a new header FTL template in framework/image and to > include it "where needed" and possibly refactor what currently exist. > As there are many ways to define "where needed". I decided to keep things > simple. There are (case insensitive) 324 occurences of "", 112 > occurences of " focus on the not email templates cases among the 12 in FTL templates. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6762) Show JGrowl alert when using ajax submit form
[ https://issues.apache.org/jira/browse/OFBIZ-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhang updated OFBIZ-6762: - Description: The current alert for ajax submit form is like below !ajaxSubmitFormAlert.png! and the improved alert should be !ajaxSubmitFormJGrowlAlert.png! was: The current alert is like below !! > Show JGrowl alert when using ajax submit form > - > > Key: OFBIZ-6762 > URL: https://issues.apache.org/jira/browse/OFBIZ-6762 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Wei Zhang >Priority: Minor > Attachments: ajaxSubmitFormAlert.png, ajaxSubmitFormJGrowlAlert.png > > > The current alert for ajax submit form is like below > !ajaxSubmitFormAlert.png! > and the improved alert should be > !ajaxSubmitFormJGrowlAlert.png! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6762) Show JGrowl alert when using ajax submit form
[ https://issues.apache.org/jira/browse/OFBIZ-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhang updated OFBIZ-6762: - Attachment: ajaxSubmitFormJGrowlAlert.png ajaxSubmitFormAlert.png > Show JGrowl alert when using ajax submit form > - > > Key: OFBIZ-6762 > URL: https://issues.apache.org/jira/browse/OFBIZ-6762 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Wei Zhang >Priority: Minor > Attachments: ajaxSubmitFormAlert.png, ajaxSubmitFormJGrowlAlert.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6762) Show JGrowl alert when using ajax submit form
[ https://issues.apache.org/jira/browse/OFBIZ-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhang updated OFBIZ-6762: - Description: The current alert is like below !! > Show JGrowl alert when using ajax submit form > - > > Key: OFBIZ-6762 > URL: https://issues.apache.org/jira/browse/OFBIZ-6762 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Wei Zhang >Priority: Minor > Attachments: ajaxSubmitFormAlert.png, ajaxSubmitFormJGrowlAlert.png > > > The current alert is like below > !! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6762) Show JGrowl alert when using ajax submit form
Wei Zhang created OFBIZ-6762: Summary: Show JGrowl alert when using ajax submit form Key: OFBIZ-6762 URL: https://issues.apache.org/jira/browse/OFBIZ-6762 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Wei Zhang Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OFBIZ-6761) The action of EditExampleBackgroundSubmit form is not correct when creating a example
[ https://issues.apache.org/jira/browse/OFBIZ-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhang resolved OFBIZ-6761. -- Resolution: Fixed Fix Version/s: Trunk > The action of EditExampleBackgroundSubmit form is not correct when creating a > example > - > > Key: OFBIZ-6761 > URL: https://issues.apache.org/jira/browse/OFBIZ-6761 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/example >Affects Versions: Trunk >Reporter: Wei Zhang >Assignee: Wei Zhang >Priority: Minor > Fix For: Trunk > > Attachments: actionOfCreatingExample.png > > > See the wrong action in the attached screen > !actionOfCreatingExample.png! > The expected action is createExampleAjax -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6761) The action of EditExampleBackgroundSubmit form is not correct when creating a example
[ https://issues.apache.org/jira/browse/OFBIZ-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhang closed OFBIZ-6761. > The action of EditExampleBackgroundSubmit form is not correct when creating a > example > - > > Key: OFBIZ-6761 > URL: https://issues.apache.org/jira/browse/OFBIZ-6761 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/example >Affects Versions: Trunk >Reporter: Wei Zhang >Assignee: Wei Zhang >Priority: Minor > Fix For: Trunk > > Attachments: actionOfCreatingExample.png > > > See the wrong action in the attached screen > !actionOfCreatingExample.png! > The expected action is createExampleAjax -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6761) The action of EditExampleBackgroundSubmit form is not correct when creating a example
[ https://issues.apache.org/jira/browse/OFBIZ-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhang updated OFBIZ-6761: - Description: See the wrong action in the attached screen !actionOfCreatingExample.png! The expected action is createExampleAjax was: See the wrong action in the attache screen !actionOfCreatingExample.png! The expected action is createExampleAjax > The action of EditExampleBackgroundSubmit form is not correct when creating a > example > - > > Key: OFBIZ-6761 > URL: https://issues.apache.org/jira/browse/OFBIZ-6761 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/example >Affects Versions: Trunk >Reporter: Wei Zhang >Assignee: Wei Zhang >Priority: Minor > Attachments: actionOfCreatingExample.png > > > See the wrong action in the attached screen > !actionOfCreatingExample.png! > The expected action is createExampleAjax -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6761) The action of EditExampleBackgroundSubmit form is not correct when creating a example
[ https://issues.apache.org/jira/browse/OFBIZ-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhang updated OFBIZ-6761: - Description: See the wrong action in the attache screen !actionOfCreatingExample.png! The expected action is createExampleAjax was: See the wrong action in the attache screen The expected action is createExampleAjax > The action of EditExampleBackgroundSubmit form is not correct when creating a > example > - > > Key: OFBIZ-6761 > URL: https://issues.apache.org/jira/browse/OFBIZ-6761 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/example >Affects Versions: Trunk >Reporter: Wei Zhang >Assignee: Wei Zhang >Priority: Minor > Attachments: actionOfCreatingExample.png > > > See the wrong action in the attache screen > !actionOfCreatingExample.png! > The expected action is createExampleAjax -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6761) The action of EditExampleBackgroundSubmit form is not correct when creating a example
[ https://issues.apache.org/jira/browse/OFBIZ-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Zhang updated OFBIZ-6761: - Attachment: actionOfCreatingExample.png > The action of EditExampleBackgroundSubmit form is not correct when creating a > example > - > > Key: OFBIZ-6761 > URL: https://issues.apache.org/jira/browse/OFBIZ-6761 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/example >Affects Versions: Trunk >Reporter: Wei Zhang >Assignee: Wei Zhang >Priority: Minor > Attachments: actionOfCreatingExample.png > > > See the wrong action in the attache screen > The expected action is createExampleAjax -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6761) The action of EditExampleBackgroundSubmit form is not correct when creating a example
Wei Zhang created OFBIZ-6761: Summary: The action of EditExampleBackgroundSubmit form is not correct when creating a example Key: OFBIZ-6761 URL: https://issues.apache.org/jira/browse/OFBIZ-6761 Project: OFBiz Issue Type: Bug Components: specialpurpose/example Affects Versions: Trunk Reporter: Wei Zhang Assignee: Wei Zhang Priority: Minor See the wrong action in the attache screen The expected action is createExampleAjax -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6760) Move all entity definitions from the applications components into a separate one
[ https://issues.apache.org/jira/browse/OFBIZ-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050293#comment-15050293 ] Jacopo Cappellato commented on OFBIZ-6760: -- Here is the branch where you can review the changes I did: https://github.com/jacopoc/ofbiz/tree/datamodel > Move all entity definitions from the applications components into a separate > one > > > Key: OFBIZ-6760 > URL: https://issues.apache.org/jira/browse/OFBIZ-6760 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS >Affects Versions: Trunk >Reporter: Jacques Le Roux > Fix For: Upcoming Branch > > > See this thread for a previous discussion: > http://markmail.org/message/sfdm22wfy3fulpyb -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6696) Remove tooltip="${uiLabelMap.CommonNotModifRecreat}" from display fields
[
https://issues.apache.org/jira/browse/OFBIZ-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Malin closed OFBIZ-6696.
{quote}
Why ?
{quote}
Why not ! Because YES we can ^^ .
Your response to my ask, so I close only.
> Remove tooltip="${uiLabelMap.CommonNotModifRecreat}" from display fields
>
>
> Key: OFBIZ-6696
> URL: https://issues.apache.org/jira/browse/OFBIZ-6696
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL APPLICATIONS
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Nicolas Malin
>Priority: Trivial
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-6696-tooltip.patch
>
>
> Many display fields have the
> {code}tooltip="${uiLabelMap.CommonNotModifRecreat}"{code} associated to a id
> field. But this field is only informative when the user wants to create a new
> record. Every other time it is superfluous.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
