Hi I am importing some xml and want to automate it so my script does (v.basic breakdown) this...

1>Custom dialog asking where the xml is.

2>Inserts this into a container as a filereference.

3>Sets a nonglobal variable ($xmlfilepath) from the file reference.

4>import xml, predefining the xsl file and I have put $xmlfilepath as the file for the xml.

Its step 4 that falls over, When i check this script step it as defaulted over to http request.

So I try inserting the $xmlfilepath variable as a calculation, when I run the script this time it will populate the http request window with the correct full filepath (filemac etc etc) but it throws up an error saying the xml failed.

I know the xml is valid and the xsl too as i have manually done the import with success.

But I have to automate the process as i need to parse the xml 3 times with 3 different style sheets, hence the initial script steps of setting the original filepath so that I can automate the following import processes.

Edited October 31, 200619 yr by Guest

OK another way of wording this would be as a question...

I want a client to select the xml file they want to import once.

Then I want to run the next 4 import script steps using that same exacting filepath as they initially selected.

Edited November 1, 200619 yr by Guest

I've been experiencing similar issues -- though it is not at all consistent. Some xml files work, some don't...in certain locations.

They will work if I hard-code the output file and the xml source. But it seems odd that the variables cause problems, especially when I check that they are correct.

Anybody have insight into this issue?