-
-
Notifications
You must be signed in to change notification settings - Fork 133
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
Status field is dependent on state field but it not responding to changes #323
Labels
Area: Frontend
Priority:Important
Issues & PRs that are important; broken functions; errors; there are workarounds
Status: Fix Proposed
A issue that has a PR related to it that provides a possible resolution
Status:Requires Updates
Issues & PRs which requires input or update from the author
Type: Bug
Something isn't working
Comments
yunusyerli1
added a commit
to yunusyerli1/SuiteCRM-Core
that referenced
this issue
Aug 18, 2023
6 tasks
johnM2401
added
Priority:Important
Issues & PRs that are important; broken functions; errors; there are workarounds
Status:Requires Updates
Issues & PRs which requires input or update from the author
Status: Fix Proposed
A issue that has a PR related to it that provides a possible resolution
Area: Frontend
labels
Aug 31, 2023
yunusyerli1
added a commit
to yunusyerli1/SuiteCRM-Core
that referenced
this issue
Oct 5, 2023
yunusyerli1
added a commit
to yunusyerli1/SuiteCRM-Core
that referenced
this issue
Nov 7, 2023
6 tasks
yunusyerli1
added a commit
to yunusyerli1/SuiteCRM-Core
that referenced
this issue
Nov 7, 2023
mpuyosa91
pushed a commit
to yunusyerli1/SuiteCRM-Core
that referenced
this issue
Nov 9, 2023
mpuyosa91
pushed a commit
to mpuyosa91/SuiteCRM-Core
that referenced
this issue
Nov 15, 2023
mpuyosa91
pushed a commit
to yunusyerli1/SuiteCRM-Core
that referenced
this issue
Nov 15, 2023
6 tasks
mpuyosa91
pushed a commit
to mpuyosa91/SuiteCRM-Core
that referenced
this issue
Dec 27, 2023
AlexMyddleware
added a commit
to AlexMyddleware/SuiteCRM-Core-fix-323
that referenced
this issue
Feb 28, 2024
Hey @yunusyerli1 As of the most recent release, (8.6.0), the issues with Dynamic Dropdowns should now be resolved. See gif, showing the behaviour: I will close this ticket off for now, but please get back in touch if you are experiencing further issues with this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area: Frontend
Priority:Important
Issues & PRs that are important; broken functions; errors; there are workarounds
Status: Fix Proposed
A issue that has a PR related to it that provides a possible resolution
Status:Requires Updates
Issues & PRs which requires input or update from the author
Type: Bug
Something isn't working
Issue
he status field in the Cases module is showing all values no matter what value is selected in the State field.
Expected Behavior
“New” and “In progress” Status drop-down values will be displayed when the State field is set to “Open”.
“Resolved” and “Cancelled” Status field drop-down values will be displayed when the State field is set to “Closed”.
Actual Behavior
The status field in the Cases module is showing all values no matter what value is selected in the State field.
Possible Fix
checkAndInitAsDynamicEnum() method need to be added to dropdownenum.component. Because the method checks the values depending on a dependant field.
Steps to Reproduce
From :
'enum.detail': EnumDetailFieldComponent,
'enum.edit': EnumEditFieldComponent,
To:
'enum.detail': DropdownEnumDetailFieldComponent,
'enum.edit': DropdownEnumEditFieldComponent,
3.Select another value in State, and still you will see all the values
Context
Status needs to be dynamic dependent on State field. This is a low priority.
Your Environment
The text was updated successfully, but these errors were encountered: