After our upgrade to Tridion 2011, I was trying to convert our Tridion 2009 Custom URL code written using ASP, to work on 2011. While working on this, I was stuck with a few API's that are not available on Tridion 2011.

On Tridion 2009, below is working as expected:-


On Tridion 2011, I changed the Custom URLs to use the below format but I didn't get back values from the Custom URLs as expected. For firefox, I get too few values back and on IE I get values as undefined.


window.dialogArguments.getFields()[0].properties.fieldDefinition.localName = SingleLineTextField
window.dialogArguments.getFields()[0].isMultiValued = Undefined
window.dialogArguments.getFields()[0].publicationURI = undefined


window.dialogArguments.getFields()[0].properties.fieldDefinition.localName = Undefined
window.dialogArguments.getFields()[0].isMultiValued = Undefined
window.dialogArguments.getFields()[0].publicationURI = Undefined

Please suggest how I might be able to fix this.

  • Hi Siva, if one of the answers below helped fix your issue, could you consider accepting it? (click the check mark next to that answer) Mar 4, 2013 at 12:06
  • @BartKoopman: Thanks for the information :) . Actually I was working on it, thats the reason I haven't accepted. Once my testing is completed on it, I will accept it Mar 4, 2013 at 16:50

2 Answers 2


The Publication URI is available through the controller object which is available in the window.dialogArguments, so you should be able to use:


Through the controller you can also get the actual item and related information, best to check it out in a debugger to see all available method.

isMultivaluedis a method, so you should call it like: window.dialogArguments.getFields()[0].isMultivalued(), that should return you the correct value.

It's unclear to me why properties.fieldDefinition.localName does not work in IE. I have the same behaviour while it works fine in Chrome and FF (something you should report to Customer Support). For the time being, perhaps you can try to use window.dialogArguments.getFields()[0].getTypeName() instead, that does seem to return the fieldtype fine in both Chrome and IE for me.

  • When I was testing, window.dialogArguments.getFields()[0].isMultivalued() is still not working and window.dialogArguments.controller.getItemPublicationUri() is working Mar 10, 2013 at 14:10
  • window.dialogArguments.getFields()[0].isMultivalued() works fine for me on both Chrome and IE on 2011 SP1 HR1, so you might want to contact Customer Support if it doesn't for you. Mar 11, 2013 at 8:33
  • 1
    I found isMultivalued() issue on FF. The problem is on 2009 isMultiValued, the letter V is Caps but on 2011 isMultivalued() letter v is small case. Mar 11, 2013 at 13:44

Another series of calls you might find helpful here and in the future are calls obtainable from window.dialogArguments.controller.getItem().

For example:


.. and the list is quite large, check it out in Firefox Firebug Console command line.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.