• Replies 7 replies
  • Subscribers 39 subscribers
  • Views 14360 views
  • Users 0 members are here
Options
Related

Not a single item error when saving on PLM

pmateo
Offline

Hello,

I don't think we have done anything major to our implementation of PLM, but I am getting the following error when I try to modify some parts manually:

Not a single item<SOAP-ENV:Envelope xmlns:SOAP-ENV="">schemas.xmlsoap.org/.../"><SOAP-ENV:Body><SOAP-ENV:Fault xmlns:af="">www.aras.com/.../faultcode><faultstring><![CDATA[Not a single item]]></faultstring><detail><af:legacy_detail><![CDATA[Not a single item]]></af:legacy_detail><af:exception message="Not a single item" type="System.Exception"/></detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>

It does not happen to all the parts but this makes things even more confusing because it was not happening before and looks like something is triggering the error on some parts and not others. Has anyone experienced this error before?

PMateo

Parents
  • Offline

    Hi PMateo

    Can you confirm when you are getting this error ?. Is it happening on initial save of a part or opening a part or editing a part ?

    Not a single item is a generic error where the method apply result is expecting one item instead it is a collection of items. 

    Based on some condition from part form, are you trying to populate some relationship tab or something when part is saved initially. If that condition is satisfied you might not get any error else you will get an error. 

    Thank You

    Gopikrishnan R

  • Offline in reply to Gopikrishnan

    Turns out, at some point a few weeks ago we updated our service pack and a list was created (automatically it seems, I was absent during this time) with some of our product codes, and those codes on the list were generating the error. I just removed them from the list and errors are gone, everything works as intended and we have not lost functionality. I was unlucky I did not check the differences between databases and data between service packs sooner.

    But thanks for your help, in the future I will make sure I use more the debugging options available.

    Pmateo

Reply
  • Offline in reply to Gopikrishnan

    Turns out, at some point a few weeks ago we updated our service pack and a list was created (automatically it seems, I was absent during this time) with some of our product codes, and those codes on the list were generating the error. I just removed them from the list and errors are gone, everything works as intended and we have not lost functionality. I was unlucky I did not check the differences between databases and data between service packs sooner.

    But thanks for your help, in the future I will make sure I use more the debugging options available.

    Pmateo

Children
No Data