[MGNLUI-5903] Column Filter: Improve the JCR data providers to be able to work with Nodes as filter Created: 28/May/20  Updated: 06/Dec/22  Resolved: 08/Feb/22

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.2.1
Fix Version/s: 6.2.17

Type: Bug Priority: Neutral
Reporter: Mercedes Iruela Assignee: Antonín Juran
Resolution: Fixed Votes: 2
Labels: nucleus
Remaining Estimate: Not Specified
Time Spent: 0.5d
Original Estimate: Not Specified

Attachments: Zip Archive pruebas.zip    
Issue Links:
Relates
relates to MGNLUI-5806 Possible performance issue while filt... Closed
relates to MGNLUI-7669 Support column filter for nodes using... Open
relates to DOCU-2187 Provide a more accurate description f... Closed
relates to MGNLUI-6364 Column Filter: comboBoxField with opt... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Epic Link: Datasource filtering
Sprint: Nucleus 3
Story Points: 3
Team: Nucleus

 Description   

Column Filters: ComboBox Field and list Select Field are not returning results when datasource is pointing to a workspace . Basically, combobox holds whole JCR nodes, filtering tries to search Node.toString()…which is not what we expect in this case (we expect something like Node#getProperty(“title”)).

Steps to reproduce:

  • Include the attached light-module in your instance.
  • Open any of the apps
  • Include content
  • Try to filter via combobox or listSelectField

Expected result

  • You get the correct results

Current Result:

  • Empty results

Workaround: use textField instead

The example is just a basic example to reproduce the issue, not a real one. However if, for example you reference to another workspace, such us Categories, or Segments, this behaviour would be helpfull for editors.

Dev notes: As a comment, I think that maybe this could lead to performance issues if the filtered workspace is to big.

Comment from Roman: we could improve the JCR data providers so in case a Node is used as filter, its UUID is used to match the property
Example of possible use-case: In Tours app, we want to add destination column with filter pointing to a category workspace.



 Comments   
Comment by Roman Kovařík [ 16/Jun/21 ]

For docu: update examples https://docs.magnolia-cms.com/product-docs/6.2/Apps/App-configuration/Column-definition.html

Comment by Roman Kovařík [ 09/Feb/22 ]

^Could we do the above as part of the ticket?

Comment by Antonín Juran [ 09/Feb/22 ]

PR for documentation update: https://git.magnolia-cms.com/projects/DOCUMENTATION/repos/product-docs/pull-requests/899/overview. Reviewed and merged.

Comment by Adam Siska [ 15/Feb/22 ]

For RN: ComboBox field within browser column filter could be configured to use JCR datasource.

Generated at Mon Feb 12 09:31:12 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.