Change 'Save As' to use part number sequence instead of adding Copy Of in the part number field?
With Aras V11, SP15: For the Part Item type, we have a pattern setup that we want all parts to follow this pattern: PRT-##### and we want it restricted to this length (9). This works. However, when someone does a 'Save AS' or in an Express ECO chooses to renumber a part. we get this error "The given value of type String from the data source cannot be converted to type nvarchar of the specified target column." This is because we've set the item_number length to equal 9 and Aras is trying to create a new part with the number field set "Copy of PRT-#####". We can get past the error by setting the item_number length to 20 but we don't want to do this as people can then create parts that don't match our pattern. Where can we change it so Aras doesn't add the "Copy of" in front of the original part's number: We'd also ideally like it to just grab the next number in our part number sequence. I've been hunting through aras methods but can't find where the "Copy of" is being added. Anyone know? Thanks.Solved7.7KViews0likes4CommentsIdentify when affected Items' server methods are being invoked on Express ECO Release/Revise?
I have some Custom BOM Item Types controlled by the Express ECO. On the custom Items we have the on Before Update and On after Update Server Events responsible for formulating the name(based on some specific field values) of these Items. Is there a standard way to ensure that the server methods are not called while the Items are promoted to the released state from the Express ECO(Release/Revise)? P.S. When it is called the On Before Update Method doesn't receive the entire context of the affected Item and sets the name to blank value. Thanks :)Solved1.8KViews0likes1CommentAffected Items Floating relationship not floating on Express ECO
Hi all, Strange error happening here. For some unknown reason, when an item is on an ECO and it is versioned, the relationship is not floating to latest. In my dev environment it is working fine and the other environment is just a push from the dev environment. I tried resetting the behavior and still nothing. I've had this issue before and I was able to resolve it by deleting the relationship and reimporting however that was a relationship I had created and in this case the OOB relationship has so much going on that I'd rather not. Any suggestions?1.6KViews1like2CommentsBatch Approve Express ECOs
We are using Innovator 24 in a large course (550+) students. This Fall we will be having all students submit their work using the Express ECOs. Once items are scored, we would like to be able to Batch Approve the ECOs by selecting the desired ECOs with an Action available in the contextual menu to approve the selected ECOs. Any assistance with writing the method that would enable this would be greatly appreciated.Solved0Views0likes1Comment