Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Content Management (Extended ECM)
API, SDK, REST and Web Services
Problem with TargetBrowseDialog
Robert_Davies_(unlondonadmin_-_(deleted))
Hi folks.I am using the TargetBrowseDialog to try and select objects in livelink as part of a custom module's functionality, but it seems that sometimes the dialog doesn't work properly.What is happening is that the dialog displays properly and you can move up and down the hierarchy of projects & folders. However when you try and select an object nothing happens: no object is selected and the dialog doesn't close.It does work properly though if I, for example, choose the Move function for an object. The dialog opens and I can select an object, closing the dialog.The URL for the action is of the same form in both cases (pasted after doing Copy Link Location)javascript:selectNodeItem( 2000, 'Livelink', 'Enterprise' )It's just in one case it works, and in the other it doesn't. I tried switching browser but see the same thing under NS4 and IE5.Has anyone else seen similar behaviour? Have any ideas how I can solve the problem?This is the code that I use to create the browser dialog;Assoc tbargs;tbargs.createType = $ApplTypeFolder;tbargs.headerLabel = "Choose new starting point.";tbargs.selectLabel = "Start Here";tbargs.javaFuncName = "doStartHere";;call < .HTMLPrefix() + 'targetbrowsedialog.html'>( tbargs, "Create" )and this is the code for the button that invokes itAny help would be much appreciated...Best regards/matt.
Find more posts tagged with
Comments
Robert_Davies_(unlondonadmin_-_(deleted))
In case anyone else manages to do this, here was my mistake:By judicious use of Alert() statements in the JScript function 'selectNodeItem' defined in:$LL_HOME\module\webnode_8_x_x\html\targetbrowse.htmlI worked out that I had mismatched the name in the tag with the name on the button that invokes the dialog. Since the that name is used to construct a reference to a JavaScript variable it's quite important.When selectNodeItem() tries to assign the details of the selected node to the variables in the form a javascript error occurs. Of course because the dialog has no status bar you don't see the message about the javascript error. The error halts the script so the window never gets closed.The perils of copying & pasting code...Best regards/matt.