nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Browse DCR externally

Shail2

Hi,

I am browsing DCR externally using the following code:

window.open('/iw-cc/command/iw.formspub.browse_for_link?vpath='+vpath+'&ceiling='+ceiling+'&hier_callback=eval(callback_81=function(path){opener.parent.WBForm.selectpath.value = path); }

With the above code i am able to browse but not able to set the DCR.

Can anyone please help me out here.

Thanks in advance.

Shail

Find more posts tagged with

Comments

Adam Stoller

What have you done to try to debug the issue?

What are you actually, really, trying to do (and why)?

My guess is that you're attempting to use context-specific directives within that URL that do not work when being used in some other context - but if you explained in more detail precisely what you are trying to accomplish and why you are trying to accomplish it the way you seem to be - someone here might be able to point you to a better way.

Shail2

Hi,

I want to browse DCR in Action Editor of Targeting, so i have written a simple jsp code to browse the DCR's manually, but somehow ok button is not working after browsing.

Thanks,

Shail

Adam Stoller

The problem with using non-officially sanctioned commands (like iw.formspub.browse_for_link) is that you do not have any real documentation for it nor [easy] access to the code to determine what the code is actually doing; and in your case you seem to be using directives based on someone else's code that used that command (e.g.: Jeff Bonifaci and Jonathon Gulbrandsen's "Building a Reusable FormAPI Framework" from 2006) with the assumption that the called function still behaves exactly the same way in whatever version of TeamSite you are using (not mentioned) which most likely is not the same.

You are also assuming that the code called from the context you are using for it will work exactly the same as the code called from the context that JB & JG (or whomever your original source was) called it from within; which may not be correct.

For example:

Is the directive 'callback', 'callback_81', 'hier_callback' or something else?
Are you sure that opener.parent.WBForm.selectpath.value is the correct address for your custom usage of this code?
Etc.

In cases like this, if you aren't using a published API and don't have [easy] access to the code you are attempting to use, you might be better off writing your own browser code so that you have total control over it and can truly debug it.