[
https://issues.apache.org/jira/browse/OFBIZ-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15643459#comment-15643459
]
Deepak Dixit commented on OFBIZ-8722:
-------------------------------------
I am saying the same Rishi, As per existing implementation if you only pass
the limited non-pk filed than service automatically set all remaining non-pk
fields to null this. To fix this issue here set-if-null it set to false. But it
introduced new difficulty or issue to mange the empty value case. and I propose
to fix this as well so that as a user we are free to manage it at service
calling level.
>>Before applying the fix as a user I will have option to get the records on
>>PKs and change the non PK as per my requirement.
I think here you are referring custom services, or wrapper services. But if we
call CRUD services directly from controller than this was not working as
expected and it set all the values to null.
> Update Services set non-pk fields to null, if only passed pks
> -------------------------------------------------------------
>
> Key: OFBIZ-8722
> URL: https://issues.apache.org/jira/browse/OFBIZ-8722
> Project: OFBiz
> Issue Type: Bug
> Components: ALL COMPONENTS
> Affects Versions: Trunk
> Reporter: Pawan Verma
> Assignee: Rishi Solanki
>
> When we pass only pks in some update services. All non-pk values are getting
> null.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
