Details
-
Sub-task
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
Trunk
-
None
-
None
-
Bug Crush Event - 21/2/2015
Description
This enhancement is useful when a entity is load by reader (ex: seed) and sometime, it could be modify in data file. If a field is change from a value to null, currently this modification will not be done in the next load.
When you are first importing new data, quite naturally all fields other than those specified in the file will be null. If, however, you're updating existing data, you might want any field not specified in the file to retain its current value, or you might want the contents of the file to specify everything about a record, in other words "take this data and null out the rest". The alternative to set-other-fields-to-null (or whatever else we might call it) would be a huge number of attribute="" in the file.
For portletWidget, entity PortalPortal have a lot of field with potential default value, so sometime, first release use some field and when it's reviewed and corrected, some field are changed to null to use the default value (to follow best practice).
This enhancement will be very useful for portletData file.
Attachments
Attachments
Issue Links
- is related to
-
OFBIZ-293 data import - nulling fields impossible
- Closed
- relates to
-
OFBIZ-293 data import - nulling fields impossible
- Closed
-
OFBIZ-5112 Adding unit test for new element to load data
- Closed
-
OFBIZ-5113 Update wiki documentation on load data
- Closed