Re: Demos are down
Yes not able to access demo instances. -- Nameet Jain On Sat, Apr 25, 2020 at 12:50 PM Ravi Lodhi wrote: > Yes, I am facing the same problem. Demo Trunk > <https://demo-trunk.ofbiz.apache.org/> and Demo Stable > <https://demo-stable.ofbiz.apache.org/> both are not accessible. > > Thanks and regards, > Ravi Lodhi > > On Sat, Apr 25, 2020 at 12:44 PM Pawan Verma wrote: > > > Hello Devs, > > > > I am not able to access demo instances > > https://ofbiz.apache.org/ofbiz-demos.html > > > > Is anyone facing the same issue, thank you! > > -- > > Thanks & Regards > > Pawan Verma > > ofbiz.apache.org > > >
Upgrading the Authorize.net AIM API
Hello Team, While researching around Advanced Integration Method (AIM) Authorize.net API, I found that the AIM API has now been deprecated. Authorize.net suggest upgrading the AIM support to XML or JSON based support. Please let me know your thoughts. Here is the link for your reference https://developer.authorize.net/api/upgrade_guide/ https://developer.authorize.net/api/reference/index.html Thanks -- Regards, Nameet Jain
Re: invoke method create
Hi Ismail, You can find the source code in EntityAutoEngine.java file. Thanks. Regards Nameet Jain On Thu, Feb 9, 2017 at 6:04 PM, Ismail Al Kouz <ialk...@bi-bst.com> wrote: > Hello Dears , > > > : > invoke="create" auth="true"> > > test service > > > > > > > > > > kindly ,There anyone can explain for me where I can find the source code > for this statement invoke=”create” and where this invoke will be go ,and > “create” in engine =“entity-auto” is a java method ? > > > > > > *Best Regards,* > > > > *Ismail Alkouz* > > Java Developer > > > > [image: Description: Logo for Office-4] > > > > [image: Description: bi email-3-02] > > > > P.O.Box 3516 Amman, 11821 > > The Hashemite Kingdom of Jordan > > *Tel.* +962 (6) 556 2620 > > *Mob (Jordan).* +962 79 282 2098 > > [image: Description: bi email-3-04] > > [image: Description: bi email-3-05] > > /biict > > @biict > > > > >
[jira] [Updated] (OFBIZ-7814) Console Warning : No parameter found for override parameter named
[ https://issues.apache.org/jira/browse/OFBIZ-7814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7814: --- Attachment: OFBIZ-7814.patch Found "fromDate" and "productPriceChangeId" field which was overridden in service, is not part of default-entity-name used in the service definition. > Console Warning : No parameter found for override parameter named > - > > Key: OFBIZ-7814 > URL: https://issues.apache.org/jira/browse/OFBIZ-7814 > Project: OFBiz > Issue Type: Bug > Components: product >Reporter: Nameet Jain >Priority: Minor > Attachments: OFBIZ-7814.patch > > > Found few warning in the console logs on ofbiz start saying > 1. No parameter found for override parameter named: productPriceChangeId in > service saveProductPriceChange > 2. No parameter found for override parameter named: fromDate in service > createProductConfigProduct -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7814) Console Warning : No parameter found for override parameter named
Nameet Jain created OFBIZ-7814: -- Summary: Console Warning : No parameter found for override parameter named Key: OFBIZ-7814 URL: https://issues.apache.org/jira/browse/OFBIZ-7814 Project: OFBiz Issue Type: Bug Components: product Reporter: Nameet Jain Priority: Minor Found few warning in the console logs on ofbiz start saying 1. No parameter found for override parameter named: productPriceChangeId in service saveProductPriceChange 2. No parameter found for override parameter named: fromDate in service createProductConfigProduct -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7621) Add "changeByUserLoginId" field for RequirementStatus
[ https://issues.apache.org/jira/browse/OFBIZ-7621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7621: --- Attachment: OFBIZ-7621.patch Updated the patch to promote the proper use of entity-auto. > Add "changeByUserLoginId" field for RequirementStatus > - > > Key: OFBIZ-7621 > URL: https://issues.apache.org/jira/browse/OFBIZ-7621 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Nameet Jain > Attachments: OFBIZ-7621.patch, OFBIZ-7621.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7619) Add "changeByUserLoginId" field for BudgetStatus
[ https://issues.apache.org/jira/browse/OFBIZ-7619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7619: --- Attachment: OFBIZ-7619.patch Hello [~soledad] Please find updated patch attached. > Add "changeByUserLoginId" field for BudgetStatus > > > Key: OFBIZ-7619 > URL: https://issues.apache.org/jira/browse/OFBIZ-7619 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Nameet Jain > Attachments: OFBIZ-7619.patch, OFBIZ-7619.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7622) Add "changeByUserLoginId" field for CustRequestStatus
[ https://issues.apache.org/jira/browse/OFBIZ-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372739#comment-15372739 ] Nameet Jain commented on OFBIZ-7622: Totally agree with Rishi > Add "changeByUserLoginId" field for CustRequestStatus > - > > Key: OFBIZ-7622 > URL: https://issues.apache.org/jira/browse/OFBIZ-7622 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Nameet Jain >Assignee: Julien NICOLAS > Attachments: OFBIZ-7622.patch, OFBIZ-7622.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7622) Add "changeByUserLoginId" field for CustRequestStatus
[ https://issues.apache.org/jira/browse/OFBIZ-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372691#comment-15372691 ] Nameet Jain commented on OFBIZ-7622: My main concern to add this task was, as most of the business process / workflow are triggered at status change. So tracking user for the status change makes sense. As it helps to know which business user made changes in related tables also. I don't find the reason to have tracking field on all the tables. Also, it will create additional data. > Add "changeByUserLoginId" field for CustRequestStatus > - > > Key: OFBIZ-7622 > URL: https://issues.apache.org/jira/browse/OFBIZ-7622 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Nameet Jain >Assignee: Julien NICOLAS > Attachments: OFBIZ-7622.patch, OFBIZ-7622.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7611) Track userlogin for status change
[ https://issues.apache.org/jira/browse/OFBIZ-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15363629#comment-15363629 ] Nameet Jain commented on OFBIZ-7611: Thank you [~soledad], I will review all the subtask and update patches to use this concept. > Track userlogin for status change > - > > Key: OFBIZ-7611 > URL: https://issues.apache.org/jira/browse/OFBIZ-7611 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk > Reporter: Nameet Jain >Assignee: Nicolas Malin > Attachments: OFBIZ-7611.patch, OFBIZ-7611.patch > > > Currently in OFBiz, 'changedByUserLoginId' field is missing from status > entities (like: ShipmentStatus). Using this field we can maintain the history > for each status change made by user. > Update all respective service and events to ensure this field gets updated. > Here is the list of entities with missing this field. > 1. BudgetStatus > 2. ContactListCommStatus > 3. CustRequestStatus > 4. ExampleStatus > 5. FinAccountStatus > 6. InventoryItemStatus > 7. InvoiceStatus > 8. PartyStatus > 9. RequirementStatus > 10. ShipmentStatus -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7751) Ignoring invalid field name [parentTypeId] found for the entity: DeductionType with value
[ https://issues.apache.org/jira/browse/OFBIZ-7751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7751: --- Attachment: OFBIZ-7751.patch Found missing field "parentTypeId" in the type entity DeductionType. While in data file passes the "parentTypeId" field. > Ignoring invalid field name [parentTypeId] found for the entity: > DeductionType with value > - > > Key: OFBIZ-7751 > URL: https://issues.apache.org/jira/browse/OFBIZ-7751 > Project: OFBiz > Issue Type: Improvement > Components: datamodel >Reporter: Nameet Jain >Priority: Minor > Attachments: OFBIZ-7751.patch > > > While data loading found warning with message > |W| Ignoring invalid field name [parentTypeId] found for the entity: > DeductionType with value -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7751) Ignoring invalid field name [parentTypeId] found for the entity: DeductionType with value
Nameet Jain created OFBIZ-7751: -- Summary: Ignoring invalid field name [parentTypeId] found for the entity: DeductionType with value Key: OFBIZ-7751 URL: https://issues.apache.org/jira/browse/OFBIZ-7751 Project: OFBiz Issue Type: Improvement Components: datamodel Reporter: Nameet Jain Priority: Minor While data loading found warning with message |W| Ignoring invalid field name [parentTypeId] found for the entity: DeductionType with value -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7750) Error adding foreign key: ModelEntity was null for related entity name Tenant
[
https://issues.apache.org/jira/browse/OFBIZ-7750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nameet Jain updated OFBIZ-7750:
---
Attachment: OFBIZ-7750.patch
> Error adding foreign key: ModelEntity was null for related entity name Tenant
> -
>
> Key: OFBIZ-7750
> URL: https://issues.apache.org/jira/browse/OFBIZ-7750
> Project: OFBiz
> Issue Type: Bug
> Components: datamodel
>Affects Versions: Trunk
> Reporter: Nameet Jain
>Priority: Minor
> Attachments: OFBIZ-7750.patch
>
>
> While data loading with derby database found console error
> {quote}
> Error adding foreign key: ModelEntity was null for related entity name Tenant
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OFBIZ-7750) Error adding foreign key: ModelEntity was null for related entity name Tenant
Nameet Jain created OFBIZ-7750:
--
Summary: Error adding foreign key: ModelEntity was null for
related entity name Tenant
Key: OFBIZ-7750
URL: https://issues.apache.org/jira/browse/OFBIZ-7750
Project: OFBiz
Issue Type: Bug
Components: datamodel
Affects Versions: Trunk
Reporter: Nameet Jain
Priority: Minor
While data loading with derby database found console error
{quote}
Error adding foreign key: ModelEntity was null for related entity name Tenant
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7611) Track userlogin for status change
[ https://issues.apache.org/jira/browse/OFBIZ-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15362013#comment-15362013 ] Nameet Jain commented on OFBIZ-7611: Sure make sense. > Track userlogin for status change > - > > Key: OFBIZ-7611 > URL: https://issues.apache.org/jira/browse/OFBIZ-7611 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk > Reporter: Nameet Jain >Assignee: Nicolas Malin > Attachments: OFBIZ-7611.patch, OFBIZ-7611.patch > > > Currently in OFBiz, 'changedByUserLoginId' field is missing from status > entities (like: ShipmentStatus). Using this field we can maintain the history > for each status change made by user. > Update all respective service and events to ensure this field gets updated. > Here is the list of entities with missing this field. > 1. BudgetStatus > 2. ContactListCommStatus > 3. CustRequestStatus > 4. ExampleStatus > 5. FinAccountStatus > 6. InventoryItemStatus > 7. InvoiceStatus > 8. PartyStatus > 9. RequirementStatus > 10. ShipmentStatus -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-7699) Invalid content was found starting with element 'xls'
[ https://issues.apache.org/jira/browse/OFBIZ-7699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360055#comment-15360055 ] Nameet Jain edited comment on OFBIZ-7699 at 7/2/16 8:00 AM: Yes it worked Thanks [~jamesyong] was (Author: nj): Yes it worked. > Invalid content was found starting with element 'xls' > - > > Key: OFBIZ-7699 > URL: https://issues.apache.org/jira/browse/OFBIZ-7699 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk > Reporter: Nameet Jain >Priority: Minor > Attachments: OFBIZ-7699.patch > > > If found this in console logs: > XmlFileLoader: File > file:/home/ofbizDemo/trunk/framework/common/widget/CommonScreens.xml process > error. Line: 491. Error message: cvc-complex-type.2.4.d: Invalid content was > found starting with element 'xls'. No child element is expected at this point. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7699) Invalid content was found starting with element 'xls'
[ https://issues.apache.org/jira/browse/OFBIZ-7699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360055#comment-15360055 ] Nameet Jain commented on OFBIZ-7699: Yes it worked. > Invalid content was found starting with element 'xls' > - > > Key: OFBIZ-7699 > URL: https://issues.apache.org/jira/browse/OFBIZ-7699 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk > Reporter: Nameet Jain >Priority: Minor > Attachments: OFBIZ-7699.patch > > > If found this in console logs: > XmlFileLoader: File > file:/home/ofbizDemo/trunk/framework/common/widget/CommonScreens.xml process > error. Line: 491. Error message: cvc-complex-type.2.4.d: Invalid content was > found starting with element 'xls'. No child element is expected at this point. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7611) Track userlogin for status change
[ https://issues.apache.org/jira/browse/OFBIZ-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360018#comment-15360018 ] Nameet Jain commented on OFBIZ-7611: On a second thought, should we enforce to have these two fields "changeByUserLoginId" and "statusDate" compulsory for the status entities? Also, we have multiple fields for the same purpose. Can we do something about it in the scope of another task? > Track userlogin for status change > - > > Key: OFBIZ-7611 > URL: https://issues.apache.org/jira/browse/OFBIZ-7611 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Nameet Jain >Assignee: Nicolas Malin > Attachments: OFBIZ-7611.patch, OFBIZ-7611.patch > > > Currently in OFBiz, 'changedByUserLoginId' field is missing from status > entities (like: ShipmentStatus). Using this field we can maintain the history > for each status change made by user. > Update all respective service and events to ensure this field gets updated. > Here is the list of entities with missing this field. > 1. BudgetStatus > 2. ContactListCommStatus > 3. CustRequestStatus > 4. ExampleStatus > 5. FinAccountStatus > 6. InventoryItemStatus > 7. InvoiceStatus > 8. PartyStatus > 9. RequirementStatus > 10. ShipmentStatus -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7611) Track userlogin for status change
[ https://issues.apache.org/jira/browse/OFBIZ-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360014#comment-15360014 ] Nameet Jain commented on OFBIZ-7611: Hi [~soledad] I am perfectly ok with the patch. Only to confirm my understanding, with the patch we are enforcing here that if someone is using "entity-auto" and has "changeByUserLoginId" then he cannot update or delete the status entity record. With the previous patch also we cannot update the "changeByUserLoginId" field :-). Thanks > Track userlogin for status change > - > > Key: OFBIZ-7611 > URL: https://issues.apache.org/jira/browse/OFBIZ-7611 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS > Affects Versions: Trunk >Reporter: Nameet Jain >Assignee: Nicolas Malin > Attachments: OFBIZ-7611.patch, OFBIZ-7611.patch > > > Currently in OFBiz, 'changedByUserLoginId' field is missing from status > entities (like: ShipmentStatus). Using this field we can maintain the history > for each status change made by user. > Update all respective service and events to ensure this field gets updated. > Here is the list of entities with missing this field. > 1. BudgetStatus > 2. ContactListCommStatus > 3. CustRequestStatus > 4. ExampleStatus > 5. FinAccountStatus > 6. InventoryItemStatus > 7. InvoiceStatus > 8. PartyStatus > 9. RequirementStatus > 10. ShipmentStatus -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7699) Invalid content was found starting with element 'xls'
[ https://issues.apache.org/jira/browse/OFBIZ-7699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7699: --- Description: If found this in console logs: XmlFileLoader: File file:/home/ofbizDemo/trunk/framework/common/widget/CommonScreens.xml process error. Line: 491. Error message: cvc-complex-type.2.4.d: Invalid content was found starting with element 'xls'. No child element is expected at this point. was: If found this in console logs: |UtilXml |E| XmlFileLoader: File file:/home/ofbizDemo/trunk/framework/common/widget/CommonScreens.xml process error. Line: 491. Error message: cvc-complex-type.2.4.d: Invalid content was found starting with element 'xls'. No child element is expected at this point. > Invalid content was found starting with element 'xls' > - > > Key: OFBIZ-7699 > URL: https://issues.apache.org/jira/browse/OFBIZ-7699 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk > Reporter: Nameet Jain >Priority: Minor > > If found this in console logs: > XmlFileLoader: File > file:/home/ofbizDemo/trunk/framework/common/widget/CommonScreens.xml process > error. Line: 491. Error message: cvc-complex-type.2.4.d: Invalid content was > found starting with element 'xls'. No child element is expected at this point. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7699) Invalid content was found starting with element 'xls'
Nameet Jain created OFBIZ-7699: -- Summary: Invalid content was found starting with element 'xls' Key: OFBIZ-7699 URL: https://issues.apache.org/jira/browse/OFBIZ-7699 Project: OFBiz Issue Type: Bug Affects Versions: Trunk Reporter: Nameet Jain Priority: Minor If found this in console logs: |UtilXml |E| XmlFileLoader: File file:/home/ofbizDemo/trunk/framework/common/widget/CommonScreens.xml process error. Line: 491. Error message: cvc-complex-type.2.4.d: Invalid content was found starting with element 'xls'. No child element is expected at this point. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7611) Track userlogin for status change
[ https://issues.apache.org/jira/browse/OFBIZ-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15358768#comment-15358768 ] Nameet Jain commented on OFBIZ-7611: Sure :) > Track userlogin for status change > - > > Key: OFBIZ-7611 > URL: https://issues.apache.org/jira/browse/OFBIZ-7611 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk > Reporter: Nameet Jain >Assignee: Nicolas Malin > Attachments: OFBIZ-7611.patch > > > Currently in OFBiz, 'changedByUserLoginId' field is missing from status > entities (like: ShipmentStatus). Using this field we can maintain the history > for each status change made by user. > Update all respective service and events to ensure this field gets updated. > Here is the list of entities with missing this field. > 1. BudgetStatus > 2. ContactListCommStatus > 3. CustRequestStatus > 4. ExampleStatus > 5. FinAccountStatus > 6. InventoryItemStatus > 7. InvoiceStatus > 8. PartyStatus > 9. RequirementStatus > 10. ShipmentStatus -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7611) Track userlogin for status change
[ https://issues.apache.org/jira/browse/OFBIZ-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7611: --- Attachment: OFBIZ-7611.patch Hi [~soledad] I already had a patch for 'entity-auto' and now attaching it to this task. Only concern I am having is that other status entities (like OrderStatus) do not have 'changeByUserLoginId' field. They have fields with the diferent name for the same purpose. So do we need to do something about it? Please take a look at the patch and share your inputs. > Track userlogin for status change > - > > Key: OFBIZ-7611 > URL: https://issues.apache.org/jira/browse/OFBIZ-7611 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk > Reporter: Nameet Jain >Assignee: Nicolas Malin > Attachments: OFBIZ-7611.patch > > > Currently in OFBiz, 'changedByUserLoginId' field is missing from status > entities (like: ShipmentStatus). Using this field we can maintain the history > for each status change made by user. > Update all respective service and events to ensure this field gets updated. > Here is the list of entities with missing this field. > 1. BudgetStatus > 2. ContactListCommStatus > 3. CustRequestStatus > 4. ExampleStatus > 5. FinAccountStatus > 6. InventoryItemStatus > 7. InvoiceStatus > 8. PartyStatus > 9. RequirementStatus > 10. ShipmentStatus -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7621) Add "changeByUserLoginId" field for RequirementStatus
[ https://issues.apache.org/jira/browse/OFBIZ-7621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7621: --- Attachment: OFBIZ-7621.patch Cannot found any reference in the system so adding only 'changeByUserloginId' field. > Add "changeByUserLoginId" field for RequirementStatus > - > > Key: OFBIZ-7621 > URL: https://issues.apache.org/jira/browse/OFBIZ-7621 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Nameet Jain > Attachments: OFBIZ-7621.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7622) Add "changeByUserLoginId" field for CustRequestStatus
[ https://issues.apache.org/jira/browse/OFBIZ-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7622: --- Attachment: OFBIZ-7622.patch > Add "changeByUserLoginId" field for CustRequestStatus > - > > Key: OFBIZ-7622 > URL: https://issues.apache.org/jira/browse/OFBIZ-7622 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Nameet Jain > Attachments: OFBIZ-7622.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7620) Add "changeByUserLoginId" field for ContactListCommStatus
[ https://issues.apache.org/jira/browse/OFBIZ-7620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7620: --- Attachment: OFBIZ-7620.patch > Add "changeByUserLoginId" field for ContactListCommStatus > - > > Key: OFBIZ-7620 > URL: https://issues.apache.org/jira/browse/OFBIZ-7620 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Nameet Jain > Attachments: OFBIZ-7620.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7619) Add "changeByUserLoginId" field for BudgetStatus
[ https://issues.apache.org/jira/browse/OFBIZ-7619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7619: --- Attachment: OFBIZ-7619.patch > Add "changeByUserLoginId" field for BudgetStatus > > > Key: OFBIZ-7619 > URL: https://issues.apache.org/jira/browse/OFBIZ-7619 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Nameet Jain > Attachments: OFBIZ-7619.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-7611) Track userlogin for status change
[ https://issues.apache.org/jira/browse/OFBIZ-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356286#comment-15356286 ] Nameet Jain edited comment on OFBIZ-7611 at 6/30/16 2:59 AM: - Hi [~utcb], You are right "enable-audit-log" is also a candidate used for tracking. If we set "enable-audit-log" on the field to true, it will create a record in entity "EntityAuditLog" from where we track which entity or field was changed, what was the previous value, what is the updated value, who changed it, when it was changed and so on. What I understand about using "enable-audit-log" setting majorly with entity fields whose data is very crucial and sensitive. Also, - Using "enable-audit-log" adds overhead and performance degradation. - When we want to show status history (same as Order status history shown on order overview screen) on respective overview screen using "EntityAuditLog" is an additional work to do. - By the time when data will grow fetching details from this entity will also be a heavy job for the system. I think that's the reason why we have "changeByUserLogin", "lastModifiedByUserLogin" and such other field on multiple entities, to show information to the user. was (Author: nj): Hi [~utcb], You are right "enable-audit-log" is also a candidate used for tracking. If we set "enable-audit-log" on the field to true, it will create a record in entity "EntityAuditLog" from where we track which entity or field was changed, what was the previous value, what is the updated value, who changed it, when it was changed and so on. What I understand about using this setting majorly with entity fields whose data is very crucial and sensitive. Also, - Using "enable-audit-log" adds overhead and performance degradation. - When we want to show status history (same as Order history shown on orderview screen) on respective overview screen using "EntityAuditLog" is an additional work to do. - By the time when data will grow fetching details from this entity will also be a heavy job for the system. I think that's the reason why we have "changeByUserLogin", "lastModifiedByUserLogin" and such other field on multiple entities to show information to user. > Track userlogin for status change > - > > Key: OFBIZ-7611 > URL: https://issues.apache.org/jira/browse/OFBIZ-7611 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Nameet Jain >Assignee: Nicolas Malin > > Currently in OFBiz, 'changedByUserLoginId' field is missing from status > entities (like: ShipmentStatus). Using this field we can maintain the history > for each status change made by user. > Update all respective service and events to ensure this field gets updated. > Here is the list of entities with missing this field. > 1. BudgetStatus > 2. ContactListCommStatus > 3. CustRequestStatus > 4. ExampleStatus > 5. FinAccountStatus > 6. InventoryItemStatus > 7. InvoiceStatus > 8. PartyStatus > 9. RequirementStatus > 10. ShipmentStatus -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7611) Track userlogin for status change
[ https://issues.apache.org/jira/browse/OFBIZ-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356286#comment-15356286 ] Nameet Jain commented on OFBIZ-7611: Hi [~utcb], You are right "enable-audit-log" is also a candidate used for tracking. If we set "enable-audit-log" on the field to true, it will create a record in entity "EntityAuditLog" from where we track which entity or field was changed, what was the previous value, what is the updated value, who changed it, when it was changed and so on. What I understand about using this setting majorly with entity fields whose data is very crucial and sensitive. Also, - Using "enable-audit-log" adds overhead and performance degradation. - When we want to show status history (same as Order history shown on orderview screen) on respective overview screen using "EntityAuditLog" is an additional work to do. - By the time when data will grow fetching details from this entity will also be a heavy job for the system. I think that's the reason why we have "changeByUserLogin", "lastModifiedByUserLogin" and such other field on multiple entities to show information to user. > Track userlogin for status change > - > > Key: OFBIZ-7611 > URL: https://issues.apache.org/jira/browse/OFBIZ-7611 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Nameet Jain >Assignee: Nicolas Malin > > Currently in OFBiz, 'changedByUserLoginId' field is missing from status > entities (like: ShipmentStatus). Using this field we can maintain the history > for each status change made by user. > Update all respective service and events to ensure this field gets updated. > Here is the list of entities with missing this field. > 1. BudgetStatus > 2. ContactListCommStatus > 3. CustRequestStatus > 4. ExampleStatus > 5. FinAccountStatus > 6. InventoryItemStatus > 7. InvoiceStatus > 8. PartyStatus > 9. RequirementStatus > 10. ShipmentStatus -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7618) Add "changeByUserLoginId" field for ShipmentStatus
[ https://issues.apache.org/jira/browse/OFBIZ-7618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7618: --- Attachment: OFBIZ-7618.patch > Add "changeByUserLoginId" field for ShipmentStatus > -- > > Key: OFBIZ-7618 > URL: https://issues.apache.org/jira/browse/OFBIZ-7618 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Nameet Jain > Attachments: OFBIZ-7618.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7617) Add "changeByUserLoginId" field for InvoiceStatus
[ https://issues.apache.org/jira/browse/OFBIZ-7617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7617: --- Attachment: OFBIZ-7617.patch > Add "changeByUserLoginId" field for InvoiceStatus > - > > Key: OFBIZ-7617 > URL: https://issues.apache.org/jira/browse/OFBIZ-7617 > Project: OFBiz > Issue Type: Sub-task > Components: accounting >Affects Versions: Trunk >Reporter: Nameet Jain > Attachments: OFBIZ-7617.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7616) Add "changeByUserLoginId" field for PartyStatus
[ https://issues.apache.org/jira/browse/OFBIZ-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7616: --- Attachment: OFBIZ-7616.patch > Add "changeByUserLoginId" field for PartyStatus > --- > > Key: OFBIZ-7616 > URL: https://issues.apache.org/jira/browse/OFBIZ-7616 > Project: OFBiz > Issue Type: Sub-task > Components: party >Affects Versions: Trunk >Reporter: Nameet Jain > Attachments: OFBIZ-7616.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7611) Track userlogin for status change
[ https://issues.apache.org/jira/browse/OFBIZ-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15352981#comment-15352981 ] Nameet Jain commented on OFBIZ-7611: I have started on this task and will upload the patches soon in the child task. > Track userlogin for status change > - > > Key: OFBIZ-7611 > URL: https://issues.apache.org/jira/browse/OFBIZ-7611 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk > Reporter: Nameet Jain >Assignee: Nicolas Malin > > Currently in OFBiz, 'changedByUserLoginId' field is missing from status > entities (like: ShipmentStatus). Using this field we can maintain the history > for each status change made by user. > Update all respective service and events to ensure this field gets updated. > Here is the list of entities with missing this field. > 1. BudgetStatus > 2. ContactListCommStatus > 3. CustRequestStatus > 4. ExampleStatus > 5. FinAccountStatus > 6. InventoryItemStatus > 7. InvoiceStatus > 8. PartyStatus > 9. RequirementStatus > 10. ShipmentStatus -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Track user for status change
Thanks Nicolas for the suggestion. Created a parent ticket OFBIZ-7611 <https://issues.apache.org/jira/browse/OFBIZ-7611> to track the progress. For this parent task added entity wise sub tickets. Regards, Nameet Jain On Mon, Jun 27, 2016 at 3:25 PM, Nicolas Malin <nicolas.ma...@nereide.fr> wrote: > I agree with proposal but like Taher I suggest to : > * check all crud service for these entities are under entity-auto engine > * Improve entity-auto engine to manage this field by automatic process (I > realized this for create/lastModification field) > * Complete unit test > * propage entity definition > > Nicolas > > > Le 25/06/2016 07:47, Taher Alkhateeb a écrit : > >> Hi Nameet, >> >> I am assuming that you will not just change the entities but everything >> like the services and events where necessary to ensure updating this >> field. >> Am I correct in my understanding? >> >> Taher Alkhateeb >> >> On Saturday, 25 June 2016, Jacques Le Roux <jacques.le.r...@les7arts.com> >> wrote: >> >> +1 >>> >>> Jacques >>> >>> >>> Le 24/06/2016 à 15:26, Nameet Jain a écrit : >>> >>> Hello everyone, >>>> >>>> Currently in OFBiz, 'changedByUserLoginId' field is missing from status >>>> entities (like: ShipmentStatus). Using this field we can maintain the >>>> history for each status change made by user. >>>> >>>> I will recommend here to add 'changedByUserLoginId' field to track the >>>> userlogin detail. Here is the list of entities with missing such type of >>>> field. >>>> >>>> 1. BudgetStatus >>>> 2. ContactListCommStatus >>>> 3. CustRequestStatus >>>> 4. ExampleStatus >>>> 5. FinAccountStatus >>>> 6. InventoryItemStatus >>>> 7. InvoiceStatus >>>> 8. PartyStatus >>>> 9. RequirementStatus >>>> 10. ShipmentStatus >>>> >>>> Please let me know your thoughts. If it looks good I will open a ticket >>>> for >>>> the same. >>>> >>>> Thanks >>>> >>>> -- >>>> Regards, >>>> Nameet Jain >>>> >>>> >>>> >
[jira] [Created] (OFBIZ-7625) Add "changeByUserLoginId" field for ExampleStatus
Nameet Jain created OFBIZ-7625: -- Summary: Add "changeByUserLoginId" field for ExampleStatus Key: OFBIZ-7625 URL: https://issues.apache.org/jira/browse/OFBIZ-7625 Project: OFBiz Issue Type: Sub-task Affects Versions: Trunk Reporter: Nameet Jain -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7623) Add "changeByUserLoginId" field for FinAccountStatus
Nameet Jain created OFBIZ-7623: -- Summary: Add "changeByUserLoginId" field for FinAccountStatus Key: OFBIZ-7623 URL: https://issues.apache.org/jira/browse/OFBIZ-7623 Project: OFBiz Issue Type: Sub-task Affects Versions: Trunk Reporter: Nameet Jain -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7624) Add "changeByUserLoginId" field for InventoryItemStatus
Nameet Jain created OFBIZ-7624: -- Summary: Add "changeByUserLoginId" field for InventoryItemStatus Key: OFBIZ-7624 URL: https://issues.apache.org/jira/browse/OFBIZ-7624 Project: OFBiz Issue Type: Sub-task Affects Versions: Trunk Reporter: Nameet Jain -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7621) Add "changeByUserLoginId" field for RequirementStatus
Nameet Jain created OFBIZ-7621: -- Summary: Add "changeByUserLoginId" field for RequirementStatus Key: OFBIZ-7621 URL: https://issues.apache.org/jira/browse/OFBIZ-7621 Project: OFBiz Issue Type: Sub-task Affects Versions: Trunk Reporter: Nameet Jain -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7622) Add "changeByUserLoginId" field for CustRequestStatus
Nameet Jain created OFBIZ-7622: -- Summary: Add "changeByUserLoginId" field for CustRequestStatus Key: OFBIZ-7622 URL: https://issues.apache.org/jira/browse/OFBIZ-7622 Project: OFBiz Issue Type: Sub-task Affects Versions: Trunk Reporter: Nameet Jain -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7620) Add "changeByUserLoginId" field for ContactListCommStatus
Nameet Jain created OFBIZ-7620: -- Summary: Add "changeByUserLoginId" field for ContactListCommStatus Key: OFBIZ-7620 URL: https://issues.apache.org/jira/browse/OFBIZ-7620 Project: OFBiz Issue Type: Sub-task Affects Versions: Trunk Reporter: Nameet Jain -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7619) Add "changeByUserLoginId" field for BudgetStatus
Nameet Jain created OFBIZ-7619: -- Summary: Add "changeByUserLoginId" field for BudgetStatus Key: OFBIZ-7619 URL: https://issues.apache.org/jira/browse/OFBIZ-7619 Project: OFBiz Issue Type: Sub-task Affects Versions: Trunk Reporter: Nameet Jain -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7618) Add "changeByUserLoginId" field for ShipmentStatus
Nameet Jain created OFBIZ-7618: -- Summary: Add "changeByUserLoginId" field for ShipmentStatus Key: OFBIZ-7618 URL: https://issues.apache.org/jira/browse/OFBIZ-7618 Project: OFBiz Issue Type: Sub-task Affects Versions: Trunk Reporter: Nameet Jain -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7617) Add "changeByUserLoginId" field for InvoiceStatus
Nameet Jain created OFBIZ-7617: -- Summary: Add "changeByUserLoginId" field for InvoiceStatus Key: OFBIZ-7617 URL: https://issues.apache.org/jira/browse/OFBIZ-7617 Project: OFBiz Issue Type: Sub-task Components: accounting Affects Versions: Trunk Reporter: Nameet Jain -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7616) Add "changeByUserLoginId" field for PartyStatus
Nameet Jain created OFBIZ-7616: -- Summary: Add "changeByUserLoginId" field for PartyStatus Key: OFBIZ-7616 URL: https://issues.apache.org/jira/browse/OFBIZ-7616 Project: OFBiz Issue Type: Sub-task Components: party Affects Versions: Trunk Reporter: Nameet Jain -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7611) Track userlogin for status change
Nameet Jain created OFBIZ-7611: -- Summary: Track userlogin for status change Key: OFBIZ-7611 URL: https://issues.apache.org/jira/browse/OFBIZ-7611 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: Trunk Reporter: Nameet Jain Currently in OFBiz, 'changedByUserLoginId' field is missing from status entities (like: ShipmentStatus). Using this field we can maintain the history for each status change made by user. Update all respective service and events to ensure this field gets updated. Here is the list of entities with missing this field. 1. BudgetStatus 2. ContactListCommStatus 3. CustRequestStatus 4. ExampleStatus 5. FinAccountStatus 6. InventoryItemStatus 7. InvoiceStatus 8. PartyStatus 9. RequirementStatus 10. ShipmentStatus -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7602) Hide product sub menus while creating new product
[ https://issues.apache.org/jira/browse/OFBIZ-7602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7602: --- Attachment: CreateProduct.png > Hide product sub menus while creating new product > - > > Key: OFBIZ-7602 > URL: https://issues.apache.org/jira/browse/OFBIZ-7602 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk > Reporter: Nameet Jain > Attachments: CreateProduct.png > > > 1. Open Catalog Manager > 2. Click "New Product" > 3. All the Sub Menus are visible. > If we navigate to any sub menu (say: Content) and try to create it, system > returns error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7602) Hide product sub menus while creating new product
[ https://issues.apache.org/jira/browse/OFBIZ-7602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7602: --- Priority: Minor (was: Major) > Hide product sub menus while creating new product > - > > Key: OFBIZ-7602 > URL: https://issues.apache.org/jira/browse/OFBIZ-7602 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: Trunk > Reporter: Nameet Jain >Priority: Minor > Attachments: CreateProduct.png > > > 1. Open Catalog Manager > 2. Click "New Product" > 3. All the Sub Menus are visible. > If we navigate to any sub menu (say: Content) and try to create it, system > returns error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7602) Hide product sub menus while creating new product
Nameet Jain created OFBIZ-7602: -- Summary: Hide product sub menus while creating new product Key: OFBIZ-7602 URL: https://issues.apache.org/jira/browse/OFBIZ-7602 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: Trunk Reporter: Nameet Jain 1. Open Catalog Manager 2. Click "New Product" 3. All the Sub Menus are visible. If we navigate to any sub menu (say: Content) and try to create it, system returns error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Track user for status change
Hello everyone, Currently in OFBiz, 'changedByUserLoginId' field is missing from status entities (like: ShipmentStatus). Using this field we can maintain the history for each status change made by user. I will recommend here to add 'changedByUserLoginId' field to track the userlogin detail. Here is the list of entities with missing such type of field. 1. BudgetStatus 2. ContactListCommStatus 3. CustRequestStatus 4. ExampleStatus 5. FinAccountStatus 6. InventoryItemStatus 7. InvoiceStatus 8. PartyStatus 9. RequirementStatus 10. ShipmentStatus Please let me know your thoughts. If it looks good I will open a ticket for the same. Thanks -- Regards, Nameet Jain
[jira] [Created] (OFBIZ-7592) Show price column in supplier product lookup during PO creation
Nameet Jain created OFBIZ-7592: -- Summary: Show price column in supplier product lookup during PO creation Key: OFBIZ-7592 URL: https://issues.apache.org/jira/browse/OFBIZ-7592 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Trunk Reporter: Nameet Jain Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7289) Monthly "Sales Report" PDF is not rendering details
[ https://issues.apache.org/jira/browse/OFBIZ-7289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7289: --- Issue Type: Sub-task (was: Bug) Parent: OFBIZ-7312 > Monthly "Sales Report" PDF is not rendering details > --- > > Key: OFBIZ-7289 > URL: https://issues.apache.org/jira/browse/OFBIZ-7289 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk >Reporter: Nameet Jain >Assignee: Deepak Dixit > Fix For: 14.12.01, 15.12.01 > > Attachments: OFBIZ-7289.patch > > > Steps: > 1) Go to Order Manager > 2) Open the Report Menu. > 3) Run the Sales Report with From Date, Month and PDF option selected. > Nothing is shown even if OLAP data has all the data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7273) Report "Sale Orders By Channel" is not rendering details
[ https://issues.apache.org/jira/browse/OFBIZ-7273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7273: --- Issue Type: Sub-task (was: Bug) Parent: OFBIZ-7312 > Report "Sale Orders By Channel" is not rendering details > > > Key: OFBIZ-7273 > URL: https://issues.apache.org/jira/browse/OFBIZ-7273 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk >Reporter: Nameet Jain >Assignee: Deepak Dixit > Fix For: 14.12.01, 15.12.01 > > Attachments: OFBIZ-7273.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7289) Monthly "Sales Report" PDF is not rendering details
[ https://issues.apache.org/jira/browse/OFBIZ-7289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7289: --- Attachment: OFBIZ-7289.patch Removing the duplicate line of setting quantity and added the code for fetching the countOrder from the schema. > Monthly "Sales Report" PDF is not rendering details > --- > > Key: OFBIZ-7289 > URL: https://issues.apache.org/jira/browse/OFBIZ-7289 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Nameet Jain > Attachments: OFBIZ-7289.patch > > > Steps: > 1) Go to Order Manager > 2) Open the Report Menu. > 3) Run the Sales Report with From Date, Month and PDF option selected. > Nothing is shown even if OLAP data has all the data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7289) Monthly "Sales Report" PDF is not rendering details
Nameet Jain created OFBIZ-7289: -- Summary: Monthly "Sales Report" PDF is not rendering details Key: OFBIZ-7289 URL: https://issues.apache.org/jira/browse/OFBIZ-7289 Project: OFBiz Issue Type: Bug Components: order Affects Versions: Trunk Reporter: Nameet Jain Steps: 1) Go to Order Manager 2) Open the Report Menu. 3) Run the Sales Report with From Date, Month and PDF option selected. Nothing is shown even if OLAP data has all the data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7273) Report "Sale Orders By Channel" is not rendering details
[ https://issues.apache.org/jira/browse/OFBIZ-7273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7273: --- Attachment: OFBIZ-7273.patch Issue was becuase of incorrect parameters names used. > Report "Sale Orders By Channel" is not rendering details > > > Key: OFBIZ-7273 > URL: https://issues.apache.org/jira/browse/OFBIZ-7273 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Nameet Jain > Attachments: OFBIZ-7273.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7273) Report Sale Orders By Channel is not rendering data
Nameet Jain created OFBIZ-7273: -- Summary: Report Sale Orders By Channel is not rendering data Key: OFBIZ-7273 URL: https://issues.apache.org/jira/browse/OFBIZ-7273 Project: OFBiz Issue Type: Bug Components: order Affects Versions: Trunk Reporter: Nameet Jain -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7273) Report "Sale Orders By Channel" is not rendering details
[ https://issues.apache.org/jira/browse/OFBIZ-7273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7273: --- Summary: Report "Sale Orders By Channel" is not rendering details (was: Report Sale Orders By Channel is not rendering data) > Report "Sale Orders By Channel" is not rendering details > > > Key: OFBIZ-7273 > URL: https://issues.apache.org/jira/browse/OFBIZ-7273 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk >Reporter: Nameet Jain > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7269) Error while importing party
[
https://issues.apache.org/jira/browse/OFBIZ-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nameet Jain updated OFBIZ-7269:
---
Attachment: OFBIZ-7269.patch
> Error while importing party
> ---
>
> Key: OFBIZ-7269
> URL: https://issues.apache.org/jira/browse/OFBIZ-7269
> Project: OFBiz
> Issue Type: Bug
> Components: party
>Affects Versions: Trunk
> Reporter: Nameet Jain
> Attachments: OFBIZ-7269.patch
>
>
> The following errors occurred while importing party from import/export screen
> https://localhost:8443/partymgr/control/ImportExport
> {quote}
> Error calling event: org.ofbiz.webapp.event.EventHandlerException: Service
> invocation error (Mapping for midleName not found, expected one of [partyId,
> preferredCurrencyUomId, groupName, firstName, middleName, lastName,
> companyPartyId, companyName, roleTypeId, contactMechPurposeTypeId,
> contactMechTypeId, emailAddress, telCountryCode, telAreaCode,
> telContactNumber, address1, address2, city, stateProvinceGeoId, postalCode,
> countryGeoId, ])
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OFBIZ-7269) Error while importing party
[
https://issues.apache.org/jira/browse/OFBIZ-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nameet Jain updated OFBIZ-7269:
---
Description:
The following errors occurred while importing party from import/export screen
https://localhost:8443/partymgr/control/ImportExport
{quote}
Error calling event: org.ofbiz.webapp.event.EventHandlerException: Service
invocation error (Mapping for midleName not found, expected one of [partyId,
preferredCurrencyUomId, groupName, firstName, middleName, lastName,
companyPartyId, companyName, roleTypeId, contactMechPurposeTypeId,
contactMechTypeId, emailAddress, telCountryCode, telAreaCode, telContactNumber,
address1, address2, city, stateProvinceGeoId, postalCode, countryGeoId, ])
{quote}
was:
The Following Errors Occurred
{quote}
Error calling event: org.ofbiz.webapp.event.EventHandlerException: Service
invocation error (Mapping for midleName not found, expected one of [partyId,
preferredCurrencyUomId, groupName, firstName, middleName, lastName,
companyPartyId, companyName, roleTypeId, contactMechPurposeTypeId,
contactMechTypeId, emailAddress, telCountryCode, telAreaCode, telContactNumber,
address1, address2, city, stateProvinceGeoId, postalCode, countryGeoId, ])
{quote}
> Error while importing party
> ---
>
> Key: OFBIZ-7269
> URL: https://issues.apache.org/jira/browse/OFBIZ-7269
> Project: OFBiz
> Issue Type: Bug
> Components: party
>Affects Versions: Trunk
> Reporter: Nameet Jain
>
> The following errors occurred while importing party from import/export screen
> https://localhost:8443/partymgr/control/ImportExport
> {quote}
> Error calling event: org.ofbiz.webapp.event.EventHandlerException: Service
> invocation error (Mapping for midleName not found, expected one of [partyId,
> preferredCurrencyUomId, groupName, firstName, middleName, lastName,
> companyPartyId, companyName, roleTypeId, contactMechPurposeTypeId,
> contactMechTypeId, emailAddress, telCountryCode, telAreaCode,
> telContactNumber, address1, address2, city, stateProvinceGeoId, postalCode,
> countryGeoId, ])
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OFBIZ-7269) Error while importing party
Nameet Jain created OFBIZ-7269:
--
Summary: Error while importing party
Key: OFBIZ-7269
URL: https://issues.apache.org/jira/browse/OFBIZ-7269
Project: OFBiz
Issue Type: Bug
Components: party
Affects Versions: Trunk
Reporter: Nameet Jain
The Following Errors Occurred
{quote}
Error calling event: org.ofbiz.webapp.event.EventHandlerException: Service
invocation error (Mapping for midleName not found, expected one of [partyId,
preferredCurrencyUomId, groupName, firstName, middleName, lastName,
companyPartyId, companyName, roleTypeId, contactMechPurposeTypeId,
contactMechTypeId, emailAddress, telCountryCode, telAreaCode, telContactNumber,
address1, address2, city, stateProvinceGeoId, postalCode, countryGeoId, ])
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7089) Cash Flow Statement report is broken
[ https://issues.apache.org/jira/browse/OFBIZ-7089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322289#comment-15322289 ] Nameet Jain commented on OFBIZ-7089: Thanks Ravi for reporting it. > Cash Flow Statement report is broken > > > Key: OFBIZ-7089 > URL: https://issues.apache.org/jira/browse/OFBIZ-7089 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk > Reporter: Nameet Jain >Assignee: Deepak Dixit > Fix For: Upcoming Branch > > Attachments: OFBIZ-7089.patch > > > Console Logs: > [java] 2016-05-21 09:52:55,079 |http-nio-8443-exec-5 |EntityExpr >|W| =-=-=-=-=-=-=-=-= Database type warning in EntityExpr > =-=-=-=-=-=-=-=-= In entity field [CustomTimePeriod.thruDate] set the value > passed in [java.sql.Date] is not compatible with the Java type of the field > [java.sql.Timestamp] > [java] java.lang.Exception: Location of database type warning -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7104) CMS throws error on clicking Find button
[ https://issues.apache.org/jira/browse/OFBIZ-7104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320032#comment-15320032 ] Nameet Jain commented on OFBIZ-7104: Thanks Jacques, James > CMS throws error on clicking Find button > > > Key: OFBIZ-7104 > URL: https://issues.apache.org/jira/browse/OFBIZ-7104 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Trunk > Reporter: Nameet Jain >Assignee: Jacques Le Roux >Priority: Minor > Fix For: 14.12.01, 15.12.01 > > Attachments: OFBIZ-7104.patch, OFBizContentManagerCMSSearchPage.png > > > Steps to regenerate > 1. Open the content app > 2. Click the CMS menu or user the link >https://localhost:8443/content/control/CMSContentFind > 3. Click on Find submenu or use link > https://localhost:8443/content/control/AdminSearch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7213) Override allow-html attribute do not work in service implementing any interface
[
https://issues.apache.org/jira/browse/OFBIZ-7213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nameet Jain updated OFBIZ-7213:
---
Description:
To test I used an interface say "testInterface". Try as shown below
=Add test interface and service =
===
Add service definition for the service "checkAllowHtmlForOverride" in
"org.ofbiz.order.order.OrderServices".
public static Map<String, Object> checkAllowHtmlForOverride(DispatchContext
dctx, Map<String, ? extends Object> context) {
String testData = (String) context.get("testData");
Debug.log("==" + testData);
return ServiceUtil.returnSuccess();
}
Run service "checkAllowHtmlForOverride" from service engine.
*Exception :*
[java] 2016-06-07 19:07:38,429 |http-nio-8443-exec-9 |ServiceDispatcher
|E| Incoming context (in runSync : checkAllowHtmlForOverride) does not
match expected requirements
[java] org.ofbiz.service.ServiceValidationException: In field [testData]
less-than (<) and greater-than (>) symbols are not allowed.
[java] at
org.ofbiz.service.ModelService.validate(ModelService.java:597)
~[ofbiz-service.jar:?]
[java] at
org.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:376)
[ofbiz-service.jar:?]
was:
To test I used an interface say "testInterface". Try as shown below
=Add test interface and service =
===
Add service definition for the service "checkAllowHtmlForOverride" in
"org.ofbiz.order.order.OrderServices".
public static Map<String, Object> checkAllowHtmlForOverride(DispatchContext
dctx, Map<String, ? extends Object> context) {
String testData = (String) context.get("testData");
Debug.log("==" + testData);
return ServiceUtil.returnSuccess();
}
Run service "checkAllowHtmlForOverride" from service engine.
Exception :
[java] 2016-06-07 19:07:38,429 |http-nio-8443-exec-9 |ServiceDispatcher
|E| Incoming context (in runSync : checkAllowHtmlForOverride) does not
match expected requirements
[java] org.ofbiz.service.ServiceValidationException: In field [testData]
less-than (<) and greater-than (>) symbols are not allowed.
[java] at
org.ofbiz.service.ModelService.validate(ModelService.java:597)
~[ofbiz-service.jar:?]
[java] at
org.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:376)
[ofbiz-service.jar:?]
> Override allow-html attribute do not work in service implementing any
> interface
> ---
>
> Key: OFBIZ-7213
> URL: https://issues.apache.org/jira/browse/OFBIZ-7213
> Project: OFBiz
> Issue Type: Bug
> Components: framework
>Affects Versions: Trunk
>Reporter: Nameet Jain
>Priority: Critical
> Attachments: OFBIZ-7213.patch
>
>
> To test I used an interface say "testInterface". Try as shown below
> =Add test interface and service =
>
>
>
> location="org.ofbiz.order.order.OrderServices"
> invoke="checkAllowHtmlForOverride">
>
>
>
> ===
> Add service definition for the service "checkAllowHtmlForOverride" in
> "org.ofbiz.order.order.OrderServices".
> public static Map<String, Object> checkAllowHtmlForOverride(DispatchContext
> dctx, Map<String, ? extends Object> context) {
> String testData = (String) context.get("testData");
> Debug.log("==" + testData);
> return ServiceUtil.returnSuccess();
> }
> Run service "checkAllowHtmlForOverride" from service engine.
> *Exception :*
> [java] 2016-06-07 19:07:38,429 |http-nio-8443-exec-9 |ServiceDispatcher
>|E| Incoming context (in runSync : checkAllowHtmlForOverride) does
> not match expected requirements
> [java] org.ofbiz.service.ServiceValidationException: In field [testData]
> less-than (<) and greater-than (>) symbols are not allowed.
> [java] at
> org.ofbiz.service.ModelService.validate(ModelService.java:597)
> ~[ofbiz-service.jar:?]
> [java] at
> org.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:376)
> [ofbiz-service.jar:?]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OFBIZ-7104) CMS throws error on clicking Find button
[ https://issues.apache.org/jira/browse/OFBIZ-7104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7104: --- Description: Steps to regenerate 1. Open the content app 2. Click the CMS menu or user the link https://localhost:8443/content/control/CMSContentFind 3. Click on Find submenu or use link https://localhost:8443/content/control/AdminSearch was: Steps to regenerate 1. Open the content app 2. Click the CMS menu or user the link https://localhost:8443/content/control/CMSContentFind 3. Click on Find sub menu or use link https://localhost:8443/content/control/AdminSearch > CMS throws error on clicking Find button > > > Key: OFBIZ-7104 > URL: https://issues.apache.org/jira/browse/OFBIZ-7104 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Trunk > Reporter: Nameet Jain >Assignee: Jacques Le Roux >Priority: Minor > Attachments: OFBIZ-7104.patch, OFBizContentManagerCMSSearchPage.png > > > Steps to regenerate > 1. Open the content app > 2. Click the CMS menu or user the link >https://localhost:8443/content/control/CMSContentFind > 3. Click on Find submenu or use link > https://localhost:8443/content/control/AdminSearch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7104) CMS throws error on clicking Find button
[ https://issues.apache.org/jira/browse/OFBIZ-7104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7104: --- Description: Steps to regenerate 1. Open the content app 2. Click the CMS menu or user the link https://localhost:8443/content/control/CMSContentFind 3. Click on Find sub menu or use link https://localhost:8443/content/control/AdminSearch was: Steps to regenerate 1. Open the content app 2. Click the CMS tab or user the link https://localhost:8443/content/control/CMSContentFind 3. Click in Find tab or use link https://localhost:8443/content/control/AdminSearch > CMS throws error on clicking Find button > > > Key: OFBIZ-7104 > URL: https://issues.apache.org/jira/browse/OFBIZ-7104 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Trunk > Reporter: Nameet Jain >Assignee: Jacques Le Roux >Priority: Minor > Attachments: OFBIZ-7104.patch, OFBizContentManagerCMSSearchPage.png > > > Steps to regenerate > 1. Open the content app > 2. Click the CMS menu or user the link >https://localhost:8443/content/control/CMSContentFind > 3. Click on Find sub menu or use link > https://localhost:8443/content/control/AdminSearch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7213) Override allow-html attribute do not work in service implementing any interface
[
https://issues.apache.org/jira/browse/OFBIZ-7213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nameet Jain updated OFBIZ-7213:
---
Attachment: OFBIZ-7213.patch
> Override allow-html attribute do not work in service implementing any
> interface
> ---
>
> Key: OFBIZ-7213
> URL: https://issues.apache.org/jira/browse/OFBIZ-7213
> Project: OFBiz
> Issue Type: Bug
> Components: framework
>Affects Versions: Trunk
>Reporter: Nameet Jain
>Priority: Critical
> Attachments: OFBIZ-7213.patch
>
>
> To test I used an interface say "testInterface". Try as shown below
> =Add test interface and service =
>
>
>
> location="org.ofbiz.order.order.OrderServices"
> invoke="checkAllowHtmlForOverride">
>
>
>
> ===
> Add service definition for the service "checkAllowHtmlForOverride" in
> "org.ofbiz.order.order.OrderServices".
> public static Map<String, Object> checkAllowHtmlForOverride(DispatchContext
> dctx, Map<String, ? extends Object> context) {
> String testData = (String) context.get("testData");
> Debug.log("==" + testData);
> return ServiceUtil.returnSuccess();
> }
> Run service "checkAllowHtmlForOverride" from service engine.
> Exception :
> [java] 2016-06-07 19:07:38,429 |http-nio-8443-exec-9 |ServiceDispatcher
>|E| Incoming context (in runSync : checkAllowHtmlForOverride) does
> not match expected requirements
> [java] org.ofbiz.service.ServiceValidationException: In field [testData]
> less-than (<) and greater-than (>) symbols are not allowed.
> [java] at
> org.ofbiz.service.ModelService.validate(ModelService.java:597)
> ~[ofbiz-service.jar:?]
> [java] at
> org.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:376)
> [ofbiz-service.jar:?]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OFBIZ-7213) Override allow-html attribute do not work in service implementing any interface
Nameet Jain created OFBIZ-7213:
--
Summary: Override allow-html attribute do not work in service
implementing any interface
Key: OFBIZ-7213
URL: https://issues.apache.org/jira/browse/OFBIZ-7213
Project: OFBiz
Issue Type: Bug
Components: framework
Affects Versions: Trunk
Reporter: Nameet Jain
Priority: Critical
Attachments: OFBIZ-7213.patch
To test I used an interface say "testInterface". Try as shown below
=Add test interface and service =
===
Add service definition for the service "checkAllowHtmlForOverride" in
"org.ofbiz.order.order.OrderServices".
public static Map<String, Object> checkAllowHtmlForOverride(DispatchContext
dctx, Map<String, ? extends Object> context) {
String testData = (String) context.get("testData");
Debug.log("==" + testData);
return ServiceUtil.returnSuccess();
}
Run service "checkAllowHtmlForOverride" from service engine.
Exception :
[java] 2016-06-07 19:07:38,429 |http-nio-8443-exec-9 |ServiceDispatcher
|E| Incoming context (in runSync : checkAllowHtmlForOverride) does not
match expected requirements
[java] org.ofbiz.service.ServiceValidationException: In field [testData]
less-than (<) and greater-than (>) symbols are not allowed.
[java] at
org.ofbiz.service.ModelService.validate(ModelService.java:597)
~[ofbiz-service.jar:?]
[java] at
org.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:376)
[ofbiz-service.jar:?]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7104) CMS throws error on clicking Find button
[ https://issues.apache.org/jira/browse/OFBIZ-7104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15317988#comment-15317988 ] Nameet Jain commented on OFBIZ-7104: [~jacques.le.roux] I actually tried with the fresh setup and followed the step described in the ticket description. No console error but error can be seen on the UI (as shown in snapshot). I have provided the patch. > CMS throws error on clicking Find button > > > Key: OFBIZ-7104 > URL: https://issues.apache.org/jira/browse/OFBIZ-7104 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Trunk > Reporter: Nameet Jain >Priority: Minor > Attachments: OFBIZ-7104.patch, OFBizContentManagerCMSSearchPage.png > > > Steps to regenerate > 1. Open the content app > 2. Click the CMS tab or user the link >https://localhost:8443/content/control/CMSContentFind > 3. Click in Find tab or use link > https://localhost:8443/content/control/AdminSearch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7104) CMS throws error on clicking Find button
[ https://issues.apache.org/jira/browse/OFBIZ-7104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7104: --- Attachment: OFBIZ-7104.patch > CMS throws error on clicking Find button > > > Key: OFBIZ-7104 > URL: https://issues.apache.org/jira/browse/OFBIZ-7104 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Trunk > Reporter: Nameet Jain >Priority: Minor > Attachments: OFBIZ-7104.patch, OFBizContentManagerCMSSearchPage.png > > > Steps to regenerate > 1. Open the content app > 2. Click the CMS tab or user the link >https://localhost:8443/content/control/CMSContentFind > 3. Click in Find tab or use link > https://localhost:8443/content/control/AdminSearch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7166) Return process fails on receiving
[ https://issues.apache.org/jira/browse/OFBIZ-7166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7166: --- Priority: Critical (was: Major) > Return process fails on receiving > - > > Key: OFBIZ-7166 > URL: https://issues.apache.org/jira/browse/OFBIZ-7166 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk > Reporter: Nameet Jain >Assignee: Deepak Dixit >Priority: Critical > Attachments: OFBIZ-7166.patch, ReturnPage.png > > > This issue will not regenerate with the test processors. > I actually tried with test account of Authorize.net and setup > "ProductStorePaymentSetting" with aimCCAuth, aimCCCapture, aimCCRefund etc. > Steps to Regenerate: > 1. Create order and quick ship entire order. > 2. Create return from order screen. > 3. Accept Return. > 4. Try to Receive return. > Issue: > Page is broken with error message > "Error in Service [aimCCRefund]: No authorization transaction found; cannot > refund". Also see the attach screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7199) Incorrect "Required for SO" when adding same product with different desired delivery date
Nameet Jain created OFBIZ-7199: -- Summary: Incorrect "Required for SO" when adding same product with different desired delivery date Key: OFBIZ-7199 URL: https://issues.apache.org/jira/browse/OFBIZ-7199 Project: OFBiz Issue Type: Bug Components: order Affects Versions: Trunk Reporter: Nameet Jain Steps to regenerate: 1) Add a product, quantity 1 and (say Rainbow Gizmo) with some delivery date. 2) Add again the same product with 2 quantity with the different delivery date. 3) Place the order. Items will be added as separate line item When we look "Required for SO" field for the line items, they shows 3. Actually, it should show 1 and 2 respectively. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7166) Return process fails on receiving
[ https://issues.apache.org/jira/browse/OFBIZ-7166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15314459#comment-15314459 ] Nameet Jain commented on OFBIZ-7166: On research found that refund for return was made for new / cloned order payment preference in place of actual preference. Because new preference in not authorized do not contain the transaction reference number. > Return process fails on receiving > - > > Key: OFBIZ-7166 > URL: https://issues.apache.org/jira/browse/OFBIZ-7166 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk > Reporter: Nameet Jain >Assignee: Deepak Dixit > Attachments: OFBIZ-7166.patch, ReturnPage.png > > > This issue will not regenerate with the test processors. > I actually tried with test account of Authorize.net and setup > "ProductStorePaymentSetting" with aimCCAuth, aimCCCapture, aimCCRefund etc. > Steps to Regenerate: > 1. Create order and quick ship entire order. > 2. Create return from order screen. > 3. Accept Return. > 4. Try to Receive return. > Issue: > Page is broken with error message > "Error in Service [aimCCRefund]: No authorization transaction found; cannot > refund". Also see the attach screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7166) Return process fails on receiving
[ https://issues.apache.org/jira/browse/OFBIZ-7166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7166: --- Attachment: OFBIZ-7166.patch > Return process fails on receiving > - > > Key: OFBIZ-7166 > URL: https://issues.apache.org/jira/browse/OFBIZ-7166 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk > Reporter: Nameet Jain > Attachments: OFBIZ-7166.patch, ReturnPage.png > > > This issue will not regenerate with the test processors. > I actually tried with test account of Authorize.net and setup > "ProductStorePaymentSetting" with aimCCAuth, aimCCCapture, aimCCRefund etc. > Steps to Regenerate: > 1. Create order and quick ship entire order. > 2. Create return from order screen. > 3. Accept Return. > 4. Try to Receive return. > Issue: > Page is broken with error message > "Error in Service [aimCCRefund]: No authorization transaction found; cannot > refund". Also see the attach screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7166) Return process fails on receiving
[ https://issues.apache.org/jira/browse/OFBIZ-7166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7166: --- Attachment: ReturnPage.png > Return process fails on receiving > - > > Key: OFBIZ-7166 > URL: https://issues.apache.org/jira/browse/OFBIZ-7166 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk > Reporter: Nameet Jain > Attachments: ReturnPage.png > > > This issue will not regenerate with the test processors. > I actually tried with test account of Authorize.net and setup > "ProductStorePaymentSetting" with aimCCAuth, aimCCCapture, aimCCRefund etc. > Steps to Regenerate: > 1. Create order and quick ship entire order. > 2. Create return from order screen. > 3. Accept Return. > 4. Try to Receive return. > Issue: > Page is broken with error message > "Error in Service [aimCCRefund]: No authorization transaction found; cannot > refund". Also see the attach screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7166) Return process fails on receiving
[ https://issues.apache.org/jira/browse/OFBIZ-7166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7166: --- Description: This issue will not regenerate with the test processors. I actually tried with test account of Authorize.net and setup "ProductStorePaymentSetting" with aimCCAuth, aimCCCapture, aimCCRefund etc. Steps to Regenerate: 1. Create order and quick ship entire order. 2. Create return from order screen. 3. Accept Return. 4. Try to Receive return. Issue: Page is broken with error message "Error in Service [aimCCRefund]: No authorization transaction found; cannot refund". Also see the attach screenshot was: This issue will not regenerate with the test processors. I actually tried with test account of Authorize.net and setup "ProductStorePaymentSetting" with aimCCAuth, aimCCCapture, aimCCRefund etc. Steps to Regenerate: 1. Create order and quick ship entire order. 2. Create return from order screen. 3. Accept Return. 4. Try to Receive return. Issue: Page is broken with error message "Error in Service [aimCCRefund]: No authorization transaction found; cannot refund" > Return process fails on receiving > - > > Key: OFBIZ-7166 > URL: https://issues.apache.org/jira/browse/OFBIZ-7166 > Project: OFBiz > Issue Type: Bug >Affects Versions: Trunk >Reporter: Nameet Jain > > This issue will not regenerate with the test processors. > I actually tried with test account of Authorize.net and setup > "ProductStorePaymentSetting" with aimCCAuth, aimCCCapture, aimCCRefund etc. > Steps to Regenerate: > 1. Create order and quick ship entire order. > 2. Create return from order screen. > 3. Accept Return. > 4. Try to Receive return. > Issue: > Page is broken with error message > "Error in Service [aimCCRefund]: No authorization transaction found; cannot > refund". Also see the attach screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7166) Return process fails on receiving
Nameet Jain created OFBIZ-7166: -- Summary: Return process fails on receiving Key: OFBIZ-7166 URL: https://issues.apache.org/jira/browse/OFBIZ-7166 Project: OFBiz Issue Type: Bug Affects Versions: Trunk Reporter: Nameet Jain This issue will not regenerate with the test processors. I actually tried with test account of Authorize.net and setup "ProductStorePaymentSetting" with aimCCAuth, aimCCCapture, aimCCRefund etc. Steps to Regenerate: 1. Create order and quick ship entire order. 2. Create return from order screen. 3. Accept Return. 4. Try to Receive return. Issue: Page is broken with error message "Error in Service [aimCCRefund]: No authorization transaction found; cannot refund" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7104) CMS throws error on clicking Find button
[ https://issues.apache.org/jira/browse/OFBIZ-7104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297720#comment-15297720 ] Nameet Jain commented on OFBIZ-7104: [~jacques.le.roux], thanks for looking into it. The error is due to missing content index. I think we can improve the error message to guide user to index the content first. > CMS throws error on clicking Find button > > > Key: OFBIZ-7104 > URL: https://issues.apache.org/jira/browse/OFBIZ-7104 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Trunk > Reporter: Nameet Jain >Priority: Minor > Attachments: OFBizContentManagerCMSSearchPage.png > > > Steps to regenerate > 1. Open the content app > 2. Click the CMS tab or user the link >https://localhost:8443/content/control/CMSContentFind > 3. Click in Find tab or use link > https://localhost:8443/content/control/AdminSearch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7104) CMS throws error on clicking Find button
[ https://issues.apache.org/jira/browse/OFBIZ-7104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7104: --- Attachment: OFBizContentManagerCMSSearchPage.png > CMS throws error on clicking Find button > > > Key: OFBIZ-7104 > URL: https://issues.apache.org/jira/browse/OFBIZ-7104 > Project: OFBiz > Issue Type: Bug > Components: content >Affects Versions: Trunk > Reporter: Nameet Jain >Priority: Minor > Attachments: OFBizContentManagerCMSSearchPage.png > > > Steps to regenerate > 1. Open the content app > 2. Click the CMS tab or user the link >https://localhost:8443/content/control/CMSContentFind > 3. Click in Find tab or use link > https://localhost:8443/content/control/AdminSearch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7092) Backordered flag should not be shown for service product
[ https://issues.apache.org/jira/browse/OFBIZ-7092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7092: --- Attachment: OFBIZ-7092.patch Updated the patch and attached. > Backordered flag should not be shown for service product > > > Key: OFBIZ-7092 > URL: https://issues.apache.org/jira/browse/OFBIZ-7092 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Akash Jain >Priority: Minor > Fix For: Trunk > > Attachments: Backordered.png, OFBIZ-7092.patch, OFBIZ-7092.patch > > > These are the steps: > -- Initiate sales order. > -- Add service product (ex. sv-1000) in the cart > Backordered flag (attached screen-shot) should not be shown for service > product. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7093) Remaining quantity should be ZERO for completed order items
[ https://issues.apache.org/jira/browse/OFBIZ-7093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294965#comment-15294965 ] Nameet Jain commented on OFBIZ-7093: Added patch. > Remaining quantity should be ZERO for completed order items > --- > > Key: OFBIZ-7093 > URL: https://issues.apache.org/jira/browse/OFBIZ-7093 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Release Branch 14.12, Trunk >Reporter: Akash Jain >Priority: Minor > Fix For: Release Branch 14.12, Trunk > > Attachments: OFBIZ-7093.patch, Remaining.png > > > There are the steps: > -- Initiate sales order. > -- Add service product (ex. sv-1000) in the cart > -- Place order and mark approved. > -- Order item of service product will be completed but Remaining quantity > still ONE (attaching screen-shot). > Expected Result: > -- Order item of service product should be completed (working) > -- Remaining quantity should be ZERO (need to fix) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7093) Remaining quantity should be ZERO for completed order items
[ https://issues.apache.org/jira/browse/OFBIZ-7093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7093: --- Attachment: OFBIZ-7093.patch Added the patch > Remaining quantity should be ZERO for completed order items > --- > > Key: OFBIZ-7093 > URL: https://issues.apache.org/jira/browse/OFBIZ-7093 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Release Branch 14.12, Trunk >Reporter: Akash Jain >Priority: Minor > Fix For: Release Branch 14.12, Trunk > > Attachments: OFBIZ-7093.patch, Remaining.png > > > There are the steps: > -- Initiate sales order. > -- Add service product (ex. sv-1000) in the cart > -- Place order and mark approved. > -- Order item of service product will be completed but Remaining quantity > still ONE (attaching screen-shot). > Expected Result: > -- Order item of service product should be completed (working) > -- Remaining quantity should be ZERO (need to fix) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (OFBIZ-7093) Remaining quantity should be ZERO for completed order items
[ https://issues.apache.org/jira/browse/OFBIZ-7093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7093: --- Comment: was deleted (was: Added the patch) > Remaining quantity should be ZERO for completed order items > --- > > Key: OFBIZ-7093 > URL: https://issues.apache.org/jira/browse/OFBIZ-7093 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Release Branch 14.12, Trunk >Reporter: Akash Jain >Priority: Minor > Fix For: Release Branch 14.12, Trunk > > Attachments: OFBIZ-7093.patch, Remaining.png > > > There are the steps: > -- Initiate sales order. > -- Add service product (ex. sv-1000) in the cart > -- Place order and mark approved. > -- Order item of service product will be completed but Remaining quantity > still ONE (attaching screen-shot). > Expected Result: > -- Order item of service product should be completed (working) > -- Remaining quantity should be ZERO (need to fix) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7104) CMS throws error on clicking Find button
Nameet Jain created OFBIZ-7104: -- Summary: CMS throws error on clicking Find button Key: OFBIZ-7104 URL: https://issues.apache.org/jira/browse/OFBIZ-7104 Project: OFBiz Issue Type: Bug Components: content Affects Versions: Trunk Reporter: Nameet Jain Priority: Minor Steps to regenerate 1. Open the content app 2. Click the CMS tab or user the link https://localhost:8443/content/control/CMSContentFind 3. Click in Find tab or use link https://localhost:8443/content/control/AdminSearch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7092) Backordered flag should not be shown for service product
[ https://issues.apache.org/jira/browse/OFBIZ-7092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7092: --- Attachment: OFBIZ-7092.patch Added Patch. In place of checking "DIGTAL_PRODUCT" OR "SERVICE" product type added check for product is not physical. > Backordered flag should not be shown for service product > > > Key: OFBIZ-7092 > URL: https://issues.apache.org/jira/browse/OFBIZ-7092 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: Trunk >Reporter: Akash Jain >Priority: Minor > Fix For: Trunk > > Attachments: Backordered.png, OFBIZ-7092.patch > > > These are the steps: > -- Initiate sales order. > -- Add service product (ex. sv-1000) in the cart > Backordered flag (attached screen-shot) should not be shown for service > product. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7089) Cash Flow Statement report is broken
[ https://issues.apache.org/jira/browse/OFBIZ-7089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294828#comment-15294828 ] Nameet Jain commented on OFBIZ-7089: Fixed service "findLastClosedDate" and updated the reference code. Please see the attached patch. > Cash Flow Statement report is broken > > > Key: OFBIZ-7089 > URL: https://issues.apache.org/jira/browse/OFBIZ-7089 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk >Reporter: Nameet Jain > Attachments: OFBIZ-7089.patch > > > Console Logs: > [java] 2016-05-21 09:52:55,079 |http-nio-8443-exec-5 |EntityExpr >|W| =-=-=-=-=-=-=-=-= Database type warning in EntityExpr > =-=-=-=-=-=-=-=-= In entity field [CustomTimePeriod.thruDate] set the value > passed in [java.sql.Date] is not compatible with the Java type of the field > [java.sql.Timestamp] > [java] java.lang.Exception: Location of database type warning -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7089) Cash Flow Statement report is broken
[ https://issues.apache.org/jira/browse/OFBIZ-7089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7089: --- Attachment: OFBIZ-7089.patch > Cash Flow Statement report is broken > > > Key: OFBIZ-7089 > URL: https://issues.apache.org/jira/browse/OFBIZ-7089 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Trunk > Reporter: Nameet Jain > Attachments: OFBIZ-7089.patch > > > Console Logs: > [java] 2016-05-21 09:52:55,079 |http-nio-8443-exec-5 |EntityExpr >|W| =-=-=-=-=-=-=-=-= Database type warning in EntityExpr > =-=-=-=-=-=-=-=-= In entity field [CustomTimePeriod.thruDate] set the value > passed in [java.sql.Date] is not compatible with the Java type of the field > [java.sql.Timestamp] > [java] java.lang.Exception: Location of database type warning -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7090) Return Pdf is throwing exception
[ https://issues.apache.org/jira/browse/OFBIZ-7090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7090: --- Summary: Return Pdf is throwing exception (was: Return Pdf is throwing exception.) > Return Pdf is throwing exception > > > Key: OFBIZ-7090 > URL: https://issues.apache.org/jira/browse/OFBIZ-7090 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Trunk > Reporter: Nameet Jain >Priority: Blocker > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7090) Return Pdf is throwing exception.
Nameet Jain created OFBIZ-7090: -- Summary: Return Pdf is throwing exception. Key: OFBIZ-7090 URL: https://issues.apache.org/jira/browse/OFBIZ-7090 Project: OFBiz Issue Type: Bug Components: order Affects Versions: Trunk Reporter: Nameet Jain Priority: Blocker -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7088) Balance Sheet Screen is broken
[ https://issues.apache.org/jira/browse/OFBIZ-7088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nameet Jain updated OFBIZ-7088: --- Summary: Balance Sheet Screen is broken (was: Balance Sheet Screen is broken.) > Balance Sheet Screen is broken > -- > > Key: OFBIZ-7088 > URL: https://issues.apache.org/jira/browse/OFBIZ-7088 > Project: OFBiz > Issue Type: Bug > Components: accounting > Reporter: Nameet Jain >Priority: Critical > > Console Logs > [java] 2016-05-21 09:24:44,989 |http-nio-8443-exec-7 |EntityExpr >|W| =-=-=-=-=-=-=-=-= Database type warning in EntityExpr > =-=-=-=-=-=-=-=-= In entity field [CustomTimePeriod.thruDate] set the value > passed in [java.sql.Date] is not compatible with the Java type of the field > [java.sql.Timestamp] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7089) Cash Flow Statement report is broken
Nameet Jain created OFBIZ-7089: -- Summary: Cash Flow Statement report is broken Key: OFBIZ-7089 URL: https://issues.apache.org/jira/browse/OFBIZ-7089 Project: OFBiz Issue Type: Bug Components: accounting Affects Versions: Trunk Reporter: Nameet Jain Console Logs: [java] 2016-05-21 09:52:55,079 |http-nio-8443-exec-5 |EntityExpr |W| =-=-=-=-=-=-=-=-= Database type warning in EntityExpr =-=-=-=-=-=-=-=-= In entity field [CustomTimePeriod.thruDate] set the value passed in [java.sql.Date] is not compatible with the Java type of the field [java.sql.Timestamp] [java] java.lang.Exception: Location of database type warning -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7088) Balance Sheet Screen is broken.
Nameet Jain created OFBIZ-7088: -- Summary: Balance Sheet Screen is broken. Key: OFBIZ-7088 URL: https://issues.apache.org/jira/browse/OFBIZ-7088 Project: OFBiz Issue Type: Bug Components: accounting Reporter: Nameet Jain Priority: Critical Console Logs [java] 2016-05-21 09:24:44,989 |http-nio-8443-exec-7 |EntityExpr |W| =-=-=-=-=-=-=-=-= Database type warning in EntityExpr =-=-=-=-=-=-=-=-= In entity field [CustomTimePeriod.thruDate] set the value passed in [java.sql.Date] is not compatible with the Java type of the field [java.sql.Timestamp] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
