How to avoid wrong revision used in MPP?
Hi Community, there is a known issue in MPP that the application will not check if the MBOM uses the same Part revisions as specified in the EBOM. The EBOM/MOBM mainly validates quantities, but never checks if the used parts revision matches. The missing revision check is a high risk. We cannot trust the MBOM data if in certain cases they will not match the original values specified in the EBOM. In worst case, this can lead to serious problems in the final product. How shall we fully track our product lifecycle, when we have wrong data? Unfortunately MPP is not in the focus of Aras right now. So I do not assume there will be much development in this application. I wonder if it´s possible to add the revision check on our own? Maybe we can customize the Method mpp_GetBomTreeGrid to add an additional MBOM validation. Or a simple onBeforeAdd Method when adding Consumed Parts to Operations, that checks if the Part exactly matches the Part specified in the EBOM. The second idea is probably easier to do, but we have to consider that we may have a multilevel EBOM. Do you have any additional ideas? I would be happy to share my solution as soon as I have one, as this one constantly make me worry.
how to prevent the related item being updated to the source item?
we have a custom Item type called "Buyer" and OOTB item type "Document" There is a relationship type "Buyer Document". So when there is an update with the related Document to the Buyer item, the latest "Document" is getting updated to the Old "Buyer" revision too. how to prevent the item being propagated.? For example : Buyer Doc 1.1 <-> Document 001.1 Buyer document is updated to Buyer Doc 1.2 <-> Document 001.1 Now the Document is updated Document 002.3 and the old Buyer Doc 1.1 linked to the latest Document 002.3. How to stop upward propgation and downward propagation of linkage , we want to do it manually link the respective Document to the buyer doc,