asked on September 9, 2022
I have mapping with hierarchy:
"DateY": {
"caption": "Metai",
"type": "number",
"hierarchy": "Perdavimo registravimo data",
"level": "Metai"
},
"DateQ": {
"caption": "Ketvirtis",
"type": "string",
"hierarchy": "Perdavimo registravimo data",
"level": "Ketvirtis",
"parent": "DateY"
},
"DateM": {
"caption": "Mėnuo",
"type": "string",
"hierarchy": "Perdavimo registravimo data",
"level": "Mėnuo",
"parent": "DateQ"
},
"DateD": {
"caption": "Diena",
"type": "string",
"hierarchy": "Perdavimo registravimo data",
"level": "Diena",
"parent": "DateM"
},
In some analysis I want only year and month, in some only month, in some only month and day (if filtered by year). I try selecting checkbox on year from GUI. In that case I can not select anything else. If I select month - then year is not selectable. Same with day - only one option from hierarchy is available. It is possible to use several criteria from hierarchy?
⋅ September 9, 2022
Also, one more irritating think - in fields search input box there is no autocomplete="off", so in few days it shows a lot of autocomplete options, and real search results are not visible anymore:
<input class="fm-ui-element fm-ui fm-ui-text-input fm-search-inp fm-ui-prompt" type="text" data-placeholder="" aria-label="Paieška" data-com.bitwarden.browser.user-edited="yes">
⋅ September 9, 2022
Here is the screen dump of original problem
⋅ September 9, 2022
Last irritating thing with fields search - if I search for date, I find field. If that field is hierarchy - I can not expand it. If I need only month in the hierarchy, I need to search that field manually, because search shows only top hierarchy field value
⋅ September 9, 2022
Here is good example of crazy behaviour: https://jsfiddle.net/flexmonster/o4jywt38/
If you select Item/Color, you'll get same color many times instead of grouping by color. And you can not limit only category in there (by checkboxing only category) - you'll get color anyway.
⋅ September 9, 2022
Hello, Mantas!
Thank you for your questions and for providing us with the attachments. They were very helpful in understanding the matter.
Please, find our comments for each case below:
1. It is possible to use several criteria from hierarchy?
Kindly note that hierarchies have a strict structure by design.
For the use case you have described, we suggest trying the folder property instead.
It allows to logically group fields on the Field List, which remain the functionality of the regular fields.
Here is an example for visualization: https://jsfiddle.net/flexmonster/zfmLyk7b/.
2. In fields search input box there is no autocomplete="off"
Thank you for sharing your experience with us.
We will add the ability to turn off the autocomplete with our minor release on the ETA October 3rd.
Our team will notify you about the update.
3. If I search for date, I find field. If that field is hierarchy - I can not expand it.
Thank you for reporting this issue.
We have added a task for improving the search in the FieldList to our customers' wishlist. Our team will notify you about any updates on the matter.
Hope you will find our answer helpful.
Feel free to contact us in case of any other questions.
Regards,
Solomiia
⋅ September 9, 2022
Thank you for you answer.
⋅ September 12, 2022
Hello, Mantas!
Thank you for your response.
Indeed, using folders is a workaround for your case, which helps to achieve the desired behavior on the grid.
There are differences between hierarchies and folders from the Fields List perspective. With folders, the whole folder structure can not be selected with one click, but any field combination can be defined.
Kindly note that checkbox logic is the following for all fields, not considering if they are in hierarchies/folders or not:
Hope it helps.
As we have promised, our team will notify you when the issue with autocomplete is fixed.
Feel free to contact us in case of any other questions.
Regards,
Solomiia
⋅ September 13, 2022
Thank you
⋅ October 4, 2022
Hello, Mantas!
Hope you are having a great week.
We are glad to inform you that the autocomplete option for input fields in Flexmonster was disabled.
This update is included in the 2.9.35 version of Flexmonster: https://www.flexmonster.com/release-notes/version-2-9-35/.
You are welcome to update the component. Here is our upgrading guide for assistance: https://www.flexmonster.com/doc/updating-to-the-latest-version/.
Please let us know if the fix works fine for you.
Best regards,
Solomiia
⋅ October 11, 2022
Hello, Mantas!
Hope you are doing well.
Our team is wondering if you had some time to try the fix, which disables the autocomplete option for input fields in Flexmonster.
Could you please let us know if the fix works well for you?
Looking forward to hearing from you.
Regards,
Solomiia
⋅ October 11, 2022
Hello, yes, that helped a lot.
Now there is one more problem, but I do not know if it is solvable (attached file) - if field text is longer, it is hidden. There is no way to make left side wider. Is there any way to make popup use 90% of the screen, or full screen, or add splitter/divider, to make column wider on request?
⋅ October 11, 2022
Hello, Mantas!
Thank you for your feedback.
We are glad to hear that the fix works well for you.
We have also moved your new question to a separate ticket for clarity: https://www.flexmonster.com/question/how-to-make-the-long-names-visible-on-the-field-list.
Feel free to contact us in case of any other questions.
Best regards,
Solomiia