Thanks Kunwar​unfortunately my mistake was even more basic - the data source for my picker - e.g. /content/myapp/dam wasn't there on the target VM environment So spurious "{value}" actually a red herring.I think I went down a bad line of enquiry.  Printing and sending you the stack trace was helpfu...

smacdonald2008​ and Kunwar​thanks for your help with this.Embarassingly it looks like the problem is down to the  spurious ""{value}" +" added into the middle of my defaultPickerSrc string. I'm not sure how that works in my local but doesn't work elsewhere

Hi smacdonald2008​no, unfortunately, I am amending customisation provided from a third party - and who had a contractor working for them to add some further indirection!  The previous supplier's code has a 'targetCollection' property value of '#cq-commerce-product-picker-collection' in their /apps/f...

Hi Kunwar​sorry it wasn't very helpful to include that WARN message.  It's something that was there before i joined the project, doesn't seem to affect operation of our custom code and to be honest i've ignored it (i think it's related to some vue.js custom javascript we include but I don't work on ...

Thanks Kunwar​sorry you are right there are the config options available for us at http://dev-author.westeurope.cloudapp.azure.com:4502/system/console/configMgr/org.apache.sling.scripting.java.impl.JavaS… (I think i mistakenly did a text search for Javascript expecting it to be in the title) but the...

Hi smacdonald2008​generally, I've added some clientlibs and extended (by copying and amending the copied jsps etc) to add additional markup.  In the main pathfield render.jsp I have amended the line that assigns the defaultPickerSrc variable, so it now looks like the following,final String defaultPi...