You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Sharan Foga (JIRA)" <ji...@apache.org> on 2015/02/21 08:38:58 UTC
[jira] [Updated] (OFBIZ-3421) Allow data load to support explicit
"null" values for entity update
[ https://issues.apache.org/jira/browse/OFBIZ-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sharan Foga updated OFBIZ-3421:
-------------------------------
Sprint: Bug Crush Event - 21/2/2015
> Allow data load to support explicit "null" values for entity update
> -------------------------------------------------------------------
>
> Key: OFBIZ-3421
> URL: https://issues.apache.org/jira/browse/OFBIZ-3421
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Reporter: Bob Morley
> Priority: Minor
> Attachments: OFBIZ-3421_AllowNullInDataLoad.patch, entity.patch
>
>
> We required the ability to be able to have the data load update existing entities with a null value on existing records. The reason for this was that we had a site in production where a product subscription resource was set to only allow 1 use. We wanted to change this record to unlimited uses, so we wanted to have the entity change its value back to "null" in the database. This change may be a bit of a hack; as it looks for "null" specifically in the data load file and then replaces that on the newly loaded entity with null to ensure backwards compatibility.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)