using DAPI.RenameNode() function

Christina_Chan_(christinachan_-_(deleted))

When I use this function to rename a document in LL,specifically I changed the document's name from all-capitals to mixed-case. It seems to display properly with the new mixed-case name. But when I check the Properties-->General tab for the document, it still displays the old original all-capitals name. I did a quick Oracle SQL query and in the DTree table the "Name" is indeed in mixed case. So my question is: why does the general tab still show the all-caps name, and which table and field is it stored in?thanks,cc

Find more posts tagged with

Comments

Appu_Nair

I don't have builder currently so I am saying this from memoryI have a feeling that info is coming from dversdata table which is linked to dtree.dataid=dversdata.docid.But from oscript all you have to do is look at the DAPIVERSION object and use its methods.So in psuedocode here's how I would do.DAPINODE.ListVersions called on versionable object like 144If succesfull a LIST of DAPIVERSION handles are obtained.Echo the DAPVERSION.pname object in a loop nd see if you seeyour ALLCAPS name in it.just search inbuilder for allocating/manipulating DAPIVERSION objects

Christina_Chan_(christinachan_-_(deleted))

That is interesting..... Yes, I found it in DVersData table, the ALLCAPS name is in there, you have a good memory. So let me get this right. DTree.Name is the document name, but it is NOT the name being displayed under Properties/General tab. Instead, it displays the DVersData.FileName value. How strange.... and confusing. Do you know why it's setup this way?That means that DAPI.RenameNode() updates the DTree.Name but not DVerData.FileName, so the Properties/General name, will NOT reflect the new name.

Appu_Nair

Do not get me wrong oscript and OT LES code is very well written and they have reasons for doing that.What is the user looking for in a General properties of a folder,a name,how many items it contains and some more info,so they can be gotten from dtree,but the same user when they look for a document they will need to know what its size is,its mime etc there is just a whole slew of information for a versionable (which occupies space) than a folder which is just a row in a database,plus the umpteen versions it could have.So if there is a node it will be in dtree ,if it is a versionable node the extra info is held in dversdata and a lot of associated tables.To make the oscript programmers life easier they give you a DAPIVERSION handle so that you can manipulate that.If all of those was held in dtree it would be an extreme waste of DB column space .That is my idea why they did it like that.Consider taking some introductory builder classes and people like Howard Pell can fill you in on the correct reasons as well.

Christina_Chan_(christinachan_-_(deleted))

I've taken builder and advanced search courses, and given the high level approach of both, neither really gets into the nitty gritty of specific fields except a few major ones in dtree and kuaf, etc. Something like this issue can only be learned when accidentally encountering it as I just did when the results don't match the intent of the programming -- and then asking questions in the forums. That is just live and learn, but I still think this particular one is weird. Maybe as you say someone else can explain why it's setup this way.

Donna Nalls

Hi Christina,Here are a couple of points you may consider:1) it is always better to use the LLNode methods when manipulating a node item...the llnode methods will capture any callbacks that may be added to the system by OT or custom modules.2) The update to the DapiNode Name value (ie DTREE table NAME) should be reflected on the General tab. You can put a breakpoint on the webnode module's infoproperties.html file and step through to see this.3) Is it possible that there is some customization (or other configuration) that is defaulting the name displayed to the original filename?4) I ran through a couple of tests using both DAPI.RENAMENODE() and LLNode.NodeRename() and for both, the properties page updated as it should.However, the DAPI.RENAMENODE method does not update the Audit - if you use the LLNode.NodeRename, the audit data will be updated -- and any callbacks that may be registered in the system will get triggered by the LLNode method.5) Is it possible your browser is caching the properties page??I don't think this is an issue with a quirk in Livelink, i would venture a guess that you have something in your environment that is forcing the properties page to use the file name instead of the item name.Put a breakpoint on infoproperties.html and have a look!I am attaching the quick script that i put together for your review...in short (or not so short at this point), it is always better to use the LLNode methods over a DAPI method when you have a corresponding LLNode method.Good Luck,Donna

Appu_Nair

I guess I send the original poster on a tangent without actually testing it myself.I concur with Donna my LES 9.7.1 does not have a problem with the General properties with DAPI.RenameNode or llNode.NodeRename.Sorry to have created a confusion.All I can guess is exactly what Donna has said,it is something that is probably erratic about the code base the user is using or a patchlevel or something like that.

Christina_Chan_(christinachan_-_(deleted))

A belated Thank-You to you both Donna and Appu!! Your instinct was right -- there was a customization buried in the infoproperties page that was mucking up the works. I also noticed that the DAPI.RenameNode() function does NOT add an entry in the DauditNew table, and that was problematic too -- we'd much prefer to have it logged in the audit trail. So I'm going to tweak my program to use the llnode script instead of the dapi function.thanks again!! These discussion groups are very useful!cc

gaurav_mahajan

I have one more query..

Was going thru this thread and found it interesting. Could you tell me how can I change the nodes that are visible to me?

I mean General properties....shows name etc.. I want it to show Category as well. Can that be done?

Or in audits I want it to show what changes have been made.