When exposing the affected items tab on express eco I get TypeError: Cannot create property 'width' on string 'image'
Any ideas on how to resolve this? It doesn't seem to affect anything other than UI response after it appears but it is quite an annoyance to anyone that clicks on the tab. I am trying to display some properties for review.3.4KViews1like7CommentsChange ItemType and Affected Item
Good day all. I am working on modifying our change ItemTypes (don't use the OOTB ones). I have been looking at the Simple ECO as an example. Our current changes are associated to a single document/part. So if someone is updating a drawing that affects a part, they would have to submit two changes, it gets worse if this affects multiple things. I would like to modify (or create a new ItemType) these changes to have the Affected Items tab. I have been testing this with a custom ItemType, but am running into problems with the Has Changes getting updated. I looked at Changes Pending in Part post and saw that there were a few Methods that I needed to look at. I modified the Methods PE_update_has_change_pending and PE_ChangeItemTransition to include my change ItemType, but my test document will not get marked as Change Pending. I tested the Simple ECO and it does mark the document. Thank you for any help you can provide.Solved5.6KViews1like6CommentsECO Item in Browser changes after voting it from Planning and to In Work
Hi all, Currently setting up a new production environment with V31 and have gotten a very special error on our ECO item. The ECO is slightly modified, but uses the EHT module from Minerva for dynamical assignment. Everything is going as planned until the ECO is voted to In Work. When the ECO refreshes it has changed its keyed_name to the affected_part keyed_name, and has gotten a new item ID. When trying to seach in the database after the ECO with the new item ID it does not exists. It seems that the ECO is now trying to be the afffected part, but the signoff tab still works, and we are able to finish the voting and release of the ECO and its affected parts. If we close the ECO tab and open it again its back to its normal state. It seems like its a client/browser issue, but I*m now at a miss to where troubleshoot. I have excluded server and client methods, but the issue is still present. We are using Edge (Version 131.0.2903.112 (Official build) (64-bit)) Any tips and help is greatly appreciated!0Views1like10Comments