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,Selected Index type properties are not displayed/added in the Enterprise search
Hello, Apart from default search properties we added few other properties of an Item type in the enterprise search Indexed type properties but these properties are not displayed in the search. Some of these properties are Items from different Item types so we included or made the configuration as per the documentation to include them part of search but no luck. I would highly appreciate if any suggestions or some more documentation provided regarding this. Thanks, Vivek
Effectivity for Documents instead for Parts?
Hi community, is anyone of you familiar with the "Effectivity" features? If yes, do you know if we can use it for other ItemTypes than 'Part' and 'BOMs'? From my opinion "Effectivity" in Product Engineering was one of the most bizarre ideas our Boston friends ever had. It´s a feature that I never understood cause it doesn´t blend into the rest of Innovator. Not into change management, not into standard versioning and definitely not to other application like MPP. I already wrote about this in a previous forum post: https://community.aras.com/f/community/5344/will-effectivity-destroy-product-traceabilty For me Effectivity looks like a custom solution built for a single target customer that was never indented to incorporated with the rest. BUT: Maybe this feature is useful for tasks outside BOM control. I think it would work much better for Documents! Case Document can change independent from the product, for example when legal requirement changes or you just have to update some generic information in the document. For this use case, Effectivity for Document suddenly sounds very useful. Maybe also Compliance data could be handled that way, cause here effectivity according to date or other factors is something common. But for addressing these use cases, Effectivity has to be supported by other ItemTypes. Something, that I never have seen or tested by myself. Has anyone tested something like this and can share experience? Thanks for any input! Angela
