Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DF Reference (to any object) with settings Dropdown + Multi Value (Multivalue) + Empty Value creates a superficial mandatory field #3730

Closed
StefanAbel-OTOBO opened this issue Aug 26, 2024 · 3 comments · Fixed by #3757 or #3967
Assignees
Labels
bug Something isn't working as intended
Milestone

Comments

@StefanAbel-OTOBO
Copy link
Contributor

StefanAbel-OTOBO commented Aug 26, 2024

When you create any DF Reference (Referenced Object Type doesn't matter) and set up the following settings:
Input mode: Dropdown (I did not test it with Multiselect, but it is not reproducable with AutoComplete)
Add empty value: yes (It is not reproducable with No)
Multiple Values: Yes (I think it is not reproducable with No, but I'm not sure anymore)

When you now fill out all mandatory fields and don't fill out your DF Reference (which is not a mandatory field), then you get an error message: "One or more errors occured.", as if you didn't fill out a mandatory field:
image

Action=AdminLog doesn't tell you more information.
It doesn't matter if you use e.g. AgentTicketPhone or CustomerTicketMessage.
I reproduced this on ov270 with OTOBO 11.0.5
I also reproduced this with a DF Reference CI with a CMDB on ov275), but as this is not CMDB exclusive, I created this in the OTOBO Framework repository)

Maybe this is somehow connected to Issue#3719:
#3719

@StefanAbel-OTOBO StefanAbel-OTOBO changed the title DF Reference (to any object) with settings Dropdown DF Reference (to any object) with settings Dropdown + Multi Value (Multivalue) + Empty Value creates a superficial mandatory field Aug 26, 2024
@StefanAbel-OTOBO StefanAbel-OTOBO added the bug Something isn't working as intended label Aug 26, 2024
@bschmalhofer bschmalhofer added this to the OTOBO 11.0.6 milestone Sep 25, 2024
@stefanhaerter
Copy link
Contributor

At least a similar bug has been observed again with dynamic field Contract-Distributor (CustomerUser reference df) in CMDB Ready2Adopt classes.

@stefanhaerter stefanhaerter reopened this Dec 5, 2024
@stefanhaerter stefanhaerter self-assigned this Dec 5, 2024
@stefanhaerter
Copy link
Contributor

Additional bug description: The bug occurs again when typing into the field, focussing on another field, clearing the reference field again and submitting the form.

@stefanhaerter
Copy link
Contributor

Reason for the buggy behavior is related to #3078 (and, thus, #3064 and #2298), where the FormCache mechanism was introduced for reference dynamic fields.

stefanhaerter added a commit that referenced this issue Dec 6, 2024
…AutoComplete reference field to prevent interferences when validating an empty AutoComplete field.
svenoe pushed a commit that referenced this issue Dec 12, 2024
…AutoComplete reference field to prevent interferences when validating an empty AutoComplete field.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment