[ 
https://issues.apache.org/jira/browse/OFBIZ-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18057275#comment-18057275
 ] 

Jacques Le Roux commented on OFBIZ-13359:
-----------------------------------------

Hi Pierre,

Could you please create the patch with Git from root? For now I get that:

C:\projectsASF\Git\ofbiz-framework>git apply OFBIZ-13359.patch
error: patch failed: 
applications/accounting/src/main/groovy/org/apache/ofbiz/accounting/invoice/InvoiceServicesScript.groovy:180
error: 
applications/accounting/src/main/groovy/org/apache/ofbiz/accounting/invoice/InvoiceServicesScript.groovy:
 patch does not apply

BTW, maybe the same for patch_OFBIZ-13350-1.patch

TIA

> Updating certain fields on invoices and invoice items does not allow you to 
> enter a blank value.
> ------------------------------------------------------------------------------------------------
>
>                 Key: OFBIZ-13359
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-13359
>             Project: OFBiz
>          Issue Type: Bug
>          Components: accounting/invoice
>    Affects Versions: 24.09.05
>            Reporter: Gaudin Pierre
>            Priority: Major
>         Attachments: OFBIZ-13359.patch
>
>
> On an invoice or invoice line, it is not possible to set certain fields to 
> null.
> For example, if the Invoice.invoiceMessage field contains a message and if 
> you want to delete this message by setting it to empty, the update service 
> ignores null fields and the message remains.
> This is also the case for invoice items.
> To reproduce the problem, edit the invoice header with the in progress 
> status, add a message in the invoice message field, save, then edit the 
> invoice header again, delete the text in the invoice message field, and save. 
> When you view the invoice, the invoice message field is not empty and has not 
> been updated.
> The same test can be performed on invoice lines.
> The attached patch corrects the problem.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to