Pricing changes are coming in January. Contact our Sales team to secure the current price for your desired license.
Get Free Trial
Get Free Trial

Expected Hiearchy Behavior with Custom DataSource Api

posted on December 18th, 2020

Answered
Henry asked on December 18, 2020

Hello,
 
We are starting to support Hierarchies with our Custom DataSource Api implementation. We followed some jsFiddles to get an idea of what the request and response structures are like and we noticed some behaviors that we weren't sure of. We've prepared some videos and fiddles to better ask our questions:

  1. When we put a hierarchy in the rows, we noticed that we are not able to expand out rows if the item in the top of the hierarchy is selected. However, if we put the entire hierarchy, or select an item lower in the hierarchy, we are able to expand out rows. Is this the expected behavior? If so, what is the difference between putting the entire hierarchy into a row and putting the item at the top of the hierarchy into a row that would cause this behavior?
  2. When we put a hierarchy in the columns, we noticed that some cells are blank if the entire hierarchy is selected. However, if we put a specific level in the hierarchy, e.g., the top item, into the columns, some of the cells that were previously blank are now populated with data. Is this the expected behavior? If so, what is the difference between putting the entire hierarchy into a column and putting a specific level of the hierarchy into the column that would cause this behavior?

 
Kind regards,
Henry
 

13 answers

Public
Vera Didenko Vera Didenko ⋅ Flexmonster ⋅ December 21, 2020

Hello, Henry, 
 
Thank you for reaching out to us and for explaining the case in such detail. 
The JSFiddle examples and video explanations helped our team to understand the situation better.
 
We would like to explain that when no hierarchy level is specified, the hierarchy's top level is selected.
Therefore, there should be no difference between putting the entire hierarchy into a column/row and putting the hierarchy's top level into the column/row. 
 

  1. We would like to confirm that this is not the expected behavior: the rows should be expandable in both cases.
    Our team will provide the fix to this issue in the minor release with the ETA 11th of January.
     
  2. We would like to confirm that this is not the expected behavior: the result on the grid should be the same in both cases.
    Our team will provide the fix to this issue in the minor release with the ETA 11th of January.

 
Please let us know if this would work for you.
If any additional questions arise, please feel free to reach out.
 
Kind regards, 
Vera

Public
Henry ⋅ December 21, 2020

Hello, Vera,
 
That will work for us, thank-you for adding this to the next minor release!
 
Kind regards,
Henry

Public
Vera Didenko Vera Didenko ⋅ Flexmonster ⋅ January 11, 2021

Hello, Henry, 
 
We are happy to inform you that the issue with expand/collapse in the hierarchical fields with the specified active level was fixed.
Also, the issue with blank cells when several hierarchies are drilled down was fixed.
 
This is available in the latest minor release of Flexmonster: https://www.flexmonster.com/release-notes/.
You are welcome to update the component. Here is our updating to the latest version tutorial for guidance.
 
Please let us know if the fix works fine for you.
We would be grateful for your feedback.
 
Kind regards, 
Vera

Public
Henry ⋅ January 11, 2021

Hi, Vera,
 
Looks like it's working on on the jsFiddles! I do have one question, however. I noticed that while inspecting the requests, the filters attribute in the /members request no longer exists and has been replaced by a singular filter attribute (see attached image). Is there any documentation on the new filter attribute and how to best handle it?
 
Kind regards,
Henry

Attachments:
members.PNG

Public
Vera Didenko Vera Didenko ⋅ Flexmonster ⋅ January 12, 2021

Hello, Henry, 
 
Thank you for your feedback.
Our team is happy to hear that the fix works for you.
 
Regarding the changes to the filters: 
Recently, our team added a new filter structure to improve and add more functionality to multi-level hierarchies.
The new filter structure will come into effect (will be sent in the request) if advanced filters are enabled (if the advanced property is set to true in the /fields response) and if the API version is specified as 2.8.22+ (in the /handshake response).
Otherwise, the old filter structure will be used.
 
We would like to kindly explain that the new filter structure documentation is currently in progress, and it will be available shortly.
We will notify you as soon as it is ready.
 
In the meantime, please feel free to reach out to us if any questions arise.
 
Kind regards, 
Vera

Public
Vera Didenko Vera Didenko ⋅ Flexmonster ⋅ January 14, 2021

Hello, Henry,
 
We are happy to inform you that we have updated the custom data source API documentation with the new filter structure.
The new filter structure is described in detail in the Filter Group Object guide.
 
If any questions arise, please feel free to contact us.
 
Kind regards,
Vera

Public
Henry ⋅ January 14, 2021

Hello, Vera,
 
Thanks for the heads up! Am I correct in understanding that the filter group's type attribute is representing a logical and and or? For instance, in the example provided in the guide, is that filter saying "(Only give me data who's W field begins with 'm') and (who's country or state field begins with 'c')"?
 
Thanks again!
Henry

Public
Henry ⋅ January 14, 2021

Oh whoops, never mind the above, I missed the last sentence in the value documentation.
I believe that should answer all of my questions, much thanks to you and the flexmonster team!

Public
Henry ⋅ January 17, 2021

Hello, Vera,
 
Apologies for opening this ticket back up, please let us know if it would be best to open another ticket. We may have found a potential bug - we've provided a fiddle and a video for convenience.
Previously, when we selected the top level item in the hierarchy (Category), we could not expand out the (Country) rows. This has now been fixed with 2.8.24. However, we noticed that we cannot drill down to the last level in the hierarchy (Size) when the top level item is selected. If we select either the entire hierarchy (Item) or another level, e.g., Color, we can drill down to the last level.

  • We also noticed the same behavior if we removed Country from the rows, leaving the hierarchy as the only row.
  • Video
  • Fiddle
Public
Vera Didenko Vera Didenko ⋅ Flexmonster ⋅ January 18, 2021

Hello, Henry, 
 
Thank you for reporting this issue and for the detailed explanations.
We would like to confirm that this is not the expected behavior. 
 
Our team will provide the fix to this issue in the minor release version of Flexmonster with the ETA 8th of February. 
 
Please let us know if this would work for you.
Looking forward to your response.
 
Kind regards, 
Vera

Public
Henry ⋅ January 18, 2021

Hello, Vera,
 
That will work for us, much thanks to the team again!
 
Kind regards,
Henry

Public
Vera Didenko Vera Didenko ⋅ Flexmonster ⋅ February 9, 2021

Hello, Henry, 
 
We are glad to inform you that the issue with drill down to the last level in the hierarchy when the top-level item is selected was fixed.
 
This is available in the latest minor release of Flexmonster: https://www.flexmonster.com/release-notes/.
You are welcome to update the component. Here is our updating to the latest version tutorial for guidance.
 
Please let us know if the fix works fine for you.
Looking forward to your response.
 
Kind regards, 
Vera

Public
Henry ⋅ February 9, 2021

Hello, Vera,
 
Looks like everything is working as expected, much thanks to you and the team!
 
Kind regards,
Henry

Please login or Register to Submit Answer