Tree Grid Views but with additional filters to hide data we don´t need - what options do we have?
Hi community, let´s assume we have a multilevel BOM with many Parts. Some of them have Documents attached. There are Documents on level 0, 3 and 7 of the BOM. I want to have an tree-like overview of the Parts and the Documents, but I don´t want to display the Parts with no documents. We can use AML or SQL to get the data. E.g. I currently use following custom AML solution to get all documents and their levels in a simple grid rendering, SQL would work similiar: In the past I already used some 3rd part libs to render lightweight trees. But these custom trees often don´t blend in well if we don´t spend a lot of time with styling. So my idea is right now to use TGV for the tree rendering. I made a very test with QD and TGV. Data is missing intentionally as it´s just a functional sample. TGVs work well for trees, but they will show the complete BOM structure. Is there any way to hide the data we don´t need? We can use parameters to filter the data. But this filter option currently only hides the text of the elements and not the complete grid row itself. This behavior probably has a reason. In a multilevel BOM scenario Innovator cannot tell on which BOM level we have documents. TGVs need the complete data for the rendering. But I would be awesome if we would have some additional filter options to play around with appearance of the data AFTER query execution. Does anyone has an idea to do these kind of tree renderings? Thanks for any input!!! Angela
Can't map query elements in tree grid view
Hi, I have been trying to solve a problem I have with using the tree grid views. I can't seem to map certain elements. I wanted to make a recursive tree grid view based on a relation to a poly item where both poly sources had a relationship to the poly item. I was able to set up a query definition that seems to work fine when i run the test query, but certain elements won't map in the tree grid view. I have tried a few different ways to set up the query and while I've mainly worked in aras 11 sp12, I have also tried it in the open version of aras 12. It seems like the tree grid views have issues mapping element when there are multiple instances of "reuse query definition" in the query. Has anyone encountered or solved this problem? Best Regards Rick Query def: Tree grid view:
