Openbravo Issue Tracking System - POS2
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0057240POS2POSpublic2024-11-21 16:532024-11-21 17:54
Reportersofidossant 
Assigned ToRetail 
PriorityhighSeverityminorReproducibilityalways
StatusclosedResolutioninvalid 
PlatformOS5OS Version
Product Versionpi 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0057240: NULL in address with CRM
DescriptionWhen we remove the mandatory from some fields in the CRM of address, when we save a record, we get the null in all the fields that are not filled.
Steps To Reproduce1 - Change the configuration in CRM (attached video)
2- Open the webpos2, and create a new customer
3 - Create a new address for the new customer

See the address with NULL
VIDEO https://drive.google.com/file/d/1EtQB7uevOJfm9Ky79GlbuVxrtFxPMK6V/view?usp=sharing [^]
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2024-11-21 16:53sofidossantNew Issue
2024-11-21 16:53sofidossantAssigned To => Retail
2024-11-21 16:53sofidossantTriggers an Emergency Pack => No
2024-11-21 17:54guilleaerNote Added: 0172442
2024-11-21 17:54guilleaerStatusnew => closed
2024-11-21 17:54guilleaerResolutionopen => invalid

Notes
(0172442)
guilleaer   
2024-11-21 17:54   
Firts of all, issues should not be reported in a video. Video can be used as an additional resource but not the main one.

I reject the issue because i consider a wrong configuration:

This happens because in your configuration the name is marked to be "used as record identifier". If the value of the property is empty null is shown.
Same for the title of the dialog which shows the details of the address.

If a field can be null it is not recommended to put it as a record identifier. In that case select other field.

By the way, working with openbravo CRM connector is not a good idea to make not mandatory some properties, because they are needd for openbravo to work.
Take into account that CRM configuration is aimed to be done by a consultant who knows how internally works the CRM so not all configurations are valid.