Options
  • State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 8 subscribers
  • Views 635 views
  • Users 0 members are here
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Ghost undeletable object avec use of CreateObject

ls_sanjco

Hello everyone,

I used the VaultObjectOperations.CreateNewObject function in a script without doing a check-in. In result, Objects are created but are not visible in M-Files desktop.


I finally understand my error and corrected the script but I cannot delete these objects. They are visible only through the "content" menu of the type in M-Files Server.


I absolutely have to delete them because I need to insert the new ones with the same ID.

Have a nice day.

  • +1

    You cannot add new ones with the same ID even if you delete them. However, you can install the MF-Client on the server and should then be able to find your objects in a special View "Other" at the bottom of the front page. From there you should be able to promote them to objects in the vault. It is similar to the situation when some application fails to save a document properly to M-Files on your PC.

  • 0 in reply to bright-ideas.dk

    Thank you for your replies.

    In the M-Files client, I have a zone "other views" with a per class or per workflow view and my objects are not here, just an empty rep for the class. I found no "Other" view and it is not in the masqued views.

    What did I missed?

  • 0 in reply to ls_sanjco

    Can't promise you that you will find it there. If it is present, it is in "Other" below the group "Other Views". You may also be able to find your files as greyed out files at the bottom of a view that shows the class in which they are supposed to go. This at least is what happens on a PC when things go wrong. I thought it might be the same on the server, but of course, you did not use the MF-Desktop when things go wrong. So I might be wrong in my assumption.

  • 0

    is correct about the IDs.

    These objects - where version 1 is not yet checked in - are only visible to the user on the machine that created them.  You would need to connect as that user from that machine, find them (they'll be "checked out to me"), and undo the checkout (effectively destroying them).





              

© M-Files Corporation 2024 | Privacy Policy