Forum Discussion

Nathan_H_'s avatar
Nathan_H_
Ideator I
5 years ago
Solved

Not All Items are Aggregated

Good day all.  I am getting an error message when I open a Part, "Not all Items are aggregated. Please contact administrator to make sure that all the references are valid."  What does this mean?  Thanks for the help.

Errors
Parts
  • Nathan_H_'s avatar
    Nathan_H_
    5 years ago

    I ran logging on the server and noticed that the Method VC_GetFilesForViewingForItem is being called.  This Method calls the Method VC_GetItemsForAggregation.  My guess is that VC_GetItemsForAggregation calls a SQL script called GetItemsForAggregation.  I'm guessing that this script looks for the relationship between the Part and Document ItemTypes.  Since I deleted the relationship it was causing an error.  I created a new relationship between them & I am not receiving the error anymore. 

6 Replies

  • Nathan_H_'s avatar
    Nathan_H_
    Ideator I
    5 years ago

    I ran logging on the server and noticed that the Method VC_GetFilesForViewingForItem is being called.  This Method calls the Method VC_GetItemsForAggregation.  My guess is that VC_GetItemsForAggregation calls a SQL script called GetItemsForAggregation.  I'm guessing that this script looks for the relationship between the Part and Document ItemTypes.  Since I deleted the relationship it was causing an error.  I created a new relationship between them & I am not receiving the error anymore. 

  • AngelaIp's avatar
    AngelaIp
    Ideator I
    5 years ago

    I remember seeing this error message, but cannot remember the context. Can you describe when you see this one?

    Edit: You say when you open a part. Do you use custom Server Method on your Part? Sound like a Federation issue

    • Nathan_H_'s avatar
      Nathan_H_
      Ideator I
      5 years ago

      This is happening whenever I open or save a Part (ItemType Part).  I accidently deleted the Part Document relationship, I'm wondering if that is where the error is coming from.  

      • AngelaIp's avatar
        AngelaIp
        Ideator I
        5 years ago

        Deleting the Document relationship sounds like a very possible source for this problem.

        The Part/Document connection is used by many standard Aras components. I assume your Part-Changes tab throw the error. Depending on your Innovator versions, it´s already triggered when you open a part, even when you don´t click on the changes tab itself. The changes tab expects, that your Document relationship is still there.

        I would not recommend to delete the relationship. If you don´t need it, better hide it.