Forum Discussion

AngelaIp's avatar
AngelaIp
Ideator I
3 years ago
Solved

GetItemRepeatConfig removes child items that are used multiple times. How to fix?

Hi community, I use a classical "GetItemRepeatConfig" query to get a Part BOM over multiple levels.  id="xyz"; Item partItem = inn.newItem("Part","GetItemRepeatConfig"); partItem.setAttrib...
Methods
  • Gopikrishnan's avatar
    Gopikrishnan
    3 years ago

    I was also in a similar situation to expand the related items but couldn't able to make it using GetItemRepeatConfig when the item repeated in the BOM. I end up writing a SQL stored procedure to get the max level of a BOM and constructed an AML query to fetch the result. 

    Would like to hear from ARAS if there is any better solution for this issue or status of the bug.

    SQL Query

    CREATE PROCEDURE [getBOMLevels] @source_id NVARCHAR(MAX)
    AS
    BEGIN
    WITH RecursiveBOM(SOURCE_ID, RELATED_ID, indent_level) AS
    (
    SELECT pb.SOURCE_ID, pb.RELATED_ID, 0 FROM innovator.PART_BOM pb WHERE SOURCE_ID = @source_id
    UNION ALL
    SELECT pb1.SOURCE_ID, pb1.RELATED_ID, indent_level +1 FROM innovator.PART_BOM pb1
    INNER JOIN RecursiveBOM rb ON rb.related_id = pb1.SOURCE_ID
    )
    SELECT MAX(indent_level) AS BOM_Level FROM RecursiveBOM rb
    END

    Using this, I constructed the loop of BOM structure AML query.

AngelaIp's avatar
AngelaIp
Ideator I
3 years ago

Hi community,

I maybe found a dumb solution to get the missing duplicate data. I didn´t found an elegant way to reference from the duplicates to the original items.

But if we fetch the relationships after executing the "GetItemRepeatConfig" query, we seem to get all the data:

.....
partItem = partItem.apply();
partItem.fetchRelationships("Part BOM","keyed_name,sort_order,related_id,source_id");

It´s not the best solution regarding performance, but at least I now should be able to build a proper tree.

Anyway, if anyone knows a better solution, let me know!

Angela

Harald_Korneliussen's avatar
Harald_Korneliussen
Ideator I
6 months ago

Hello Angela,

Did you ever find a better way to do this? I'm also making trees, which can't be built incrementally (we need to sum up things from the leaves). Fetching relationships on every level is really slow :/

  • AngelaIp's avatar
    AngelaIp
    Ideator I
    6 months ago

    Good question! I don´t even use my own fetch solution. 

    Now that I think about it, I believe I have a much better idea: Why don’t we just repair the structure?

    We use the regular getItemRepeatQuery as-is and than call a function that search for identical nodes and rebuilds the sub-data.

    • AngelaIp's avatar
      AngelaIp
      Ideator I
      6 months ago

      I made a very quick test. Restoring the missing nodes seems to be possible! That´s the current result:

      First one is the original structure. Second one with corrected nodes. 

      The concept isn´t finished yet, but looks promising.

      • Harald_Korneliussen's avatar
        Harald_Korneliussen
        Ideator I
        6 months ago

        I eventually managed to avoid fetching relationships by carefully caching the values I was interested in (by ID). I didn't take the risk of messing with the actual Item object itself, but interesting to know that it can work!