How to get items with all of its revisions with maximum generation
Hi, I am trying to get part all revision with maximum generation using IOM: below are the entries: Item Number Generation Revision Testnumber1 1 00 Testnumber1 2 00 Testnumber1 3 00 Testnumber1 4 00 Testnumber1 5 00 Testnumber1 6 00 Testnumber1 7 00 Testnumber1 8 01 Testnumber1 9 01 Testnumber1 10 02 so from above entries I want: Item Number Generation Revision Testnumber1 7 00 Testnumber1 9 01 Testnumber1 10 02 I got this result with below SQL: select item_number, MAX(generation) as generation, major_rev from innovator.PART group by item_number, major_rev order by generation but how to do this with IOM? Regards, Maddy.
Increase the Major_Rev / Revision sequence.
Hello! I am trying to create a new revision by using the "PE_CreateNewRevision" method and it is throwing this error at me: <faultstring>Failed to version the item: revision sequence exceeded.</faultstring> Does anyone know where this List/Sequence is located so I can increase its limit? It looks like it currently maxes out at 'AZ' Thanks.Workflow Activity not get created when new revision is created
Hi, I have part lifecycle, in which I have 3 states Preliminary, Review and Released, On Released state I give permission to update, so it will create a new revision of , this all works fine, State of the part also get change from Released to Preliminary, but workflow task will not get create for B revision. Thanks.
Workflow haven't restarted after new manual revision
Hello, Gone through community posts but could not found answer. Hope some one could answer my question. Workflow is not restarted after creating revision to an item(Custom item type), Does Aras restrict such restart of workflow? if yes, how could i achieve this. This is part of my data migration requirement where the newly migrated items needs to be in "Released" state and should be capable enough to revisioned and behave as normal workflow to vote.
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,
Restart workflow on Revision
Hi I have an Item with a workflow attached to it.On creation of a new revision of that Item I would like to Restart my workflow. I tried to call reinstantiate and start workflow on the lifecycle state draft. However unless I am deleting the last workflow process, I am unable to start the workflow again . But this impacts the workflow history of the past revision of the item. Is there any other way to achieve this functionality without affecting its history ?
