Changing Object attributes anyone ?

Nick_Clark_(simmonssimmonsuser1_-_(deleted))

Putting together some C code to automatically create documents in the Enterprise workspace from Win95 against LL8.02 on Solaris & Oracle ... I create a new document with LL_AddDocument, I can then use LL_GetObjectInfo to get the attributes for the new object back, modify the NAME attribute using LL_AssocSetString & update the object with LL_UpdateObjectInfo - all of this is fine & the changes are reflected in Livelink.Now the bad bit. I would also like to be able to change the OWNER & CREATEDBY attributes in some cases - I can use the same procedure as above, but the changes are ignored when I call UpdateObject (I am testing this as Admin user ATM).The manual dosent say what attributes I can & cant change (although it warns against changing Node & Vol) - has anyone else tried this with more luck than me ?Ta....Nick.

Find more posts tagged with

Comments

Robert_Davies_(unlondonadmin_-_(deleted))

Hi Nick.I'm the definite newbie here so I apologize if I'm telling you things you already know -- every day is a journey of discovery for me...I'm not quite sure how an API call ties to a livelink function but by the looks of it they get internally translated into calls to the appropriate OScript function just as if the action had been done via the web.So I took a look inside the LLNode.NodeUpdate() method to see what checking it did. As far as I can see it only checks to make sure you have PModify permission to the node. I couldn't find any reference to attempts to change specific attributes. To be sure though I am still finding my way around Builder...After checking the permissions everything disappears into the DAPI.UpdateNode() 'builtin' method so maybe it's happening in there...What I did find interesting though is that I can't find how you change the owner/creator info via the web interface. It doesn't seem to me to be an option from the info pages.Do you have the Builder program? If you do you might be able to trace the calls into the Node Update.Best regards/matt.

Nick_Clark_(simmonssimmonsuser1_-_(deleted))

Thanks for that - I guess Im going to have to build an NT box & install the builder on it... Oh well.N.

Robert_Davies_(unlondonadmin_-_(deleted))

Hi Nick.Maybe I can help you out further since I already have the setup. Can you send me the code you are having a problem with? I can trace it into Livelink and send you the results.It'd have to be compiled - it's been a long time since I have done 'C'.Best regards/matt.p.s. Do you know Andrew Woolstone?

Mike_Oliver_(ollie_(Delete)_137504)

Those attributes are set by the system and for audit and security reasons are not updateable by the user. Why would you want to change those attributes anyway? If you have a process that is adding documents, do you not want to add them in the name of the user logged in? You could very easily and very quickly make the system unusable if you set an object to be owned by someone that can't get at it to change it...What problem are you trying to solve by changing those attributes?

Arlene_Elder_(GlaxoWellAdmin_(Delete)_1421884)

You should be able to change the owner to anyone. This is availabe through the web interface and should be available through the API. I highly reccomend setting up the builder to see what is going on in the calls. You can put break statements into the APIDOC:APIDocuments:UpdateObjectInfo Execute method to see exactly what is passed in and how it was processed. If the function is missing through the API, look at how it is done in the web interface and you can modify the API to handle these requests.Let me know if this helps

Nick_Clark_(simmonssimmonsuser1_-_(deleted))

Well - Heres the problem.We have a large number of users who will (hopefully) be creating a large number of documents. We wish to be able to control the location in which these documents are created (organised by client, in most cases) & automatically create a standard set of folders & attributes for the documents where required. But, we dont really want to give the majority of the users the ability to create folders; at least initially. We will also be restricting what they can do within the folders that exist (ie remove the ability to change attributes if we can).My cunning plan was to create the documents as one user who could also set the attributes & create folders as required, then change the ownership so that it appeared they were created & owned by someone else. Needless to say, I can work around this in a number of ways; I just didnt want to if I could avoid it(!!).N.