Scripted import XML file pops dialog, can I get it to run without the dialog, without stopping?

[ignotum]

My script imports an XML file... when the step is called FMP pops a dialog, can I get it to run without the dialog, without stopping? The import works properly, putting data into the correct fields.

I am not using an XSL style sheet. Should me import settings be different to get this to run without a dialog?

[comment]

It is hard to understand your settings from the screenshots.

1. Do you have the option 'With dialog' turned off in the Import Records step?

2. Are you using a variable or an explicit filename to specify the path to the source file (the screenshots show conflicting data)?

3. What is the exact dialog you get when you run the script? Is there an error message?

 

 

[ignotum]

UPDATE: The below is not correct.... see my later post to explain why I THOUGHT this worked and why is is not correct info.




So... problem solved...(!?) I kept playing around with the settings... what worked is shown in the screen shots. It seems odd to me that I needed to set the import to "XML data" and "HTTP request" and leave the HTTP request field (see attachments) empty. Dialog ON/OFF was always set to off.

Now this will loop through the XML files in the target folder properly, without stopping.

FYI this WAS the dialog where it was stopping.
 

×

I spoke too soon.... it WAS working but now it is not.... hold please.......

Edited January 9 by ignotum

[ignotum]

Here is the odd behavior.

 

I set the import step's Specify Data source section as follows:

 

Run the script and it works as expected, without pausing.

 

I then go back to the script and open the "Specify data source" section of the import step and see this:

 

 

If I click OK it will, as expected, save this new setting.... and the IMPORT step will fail, not doing ANY importing, not pausing.... just looping through the files in the folder.

 

Is this a bug or some expected behavior that I don't understand?

FYI this is under FMP 18 (because that's where I have BaseElements installed that I'm using to get the list of files in the folder)

Mark

 

 

[comment]

16 minutes ago, ignotum said:

then go back to the script and open the "Specify data source" section of the import step and see this

I see the same thing (in version 18). This is apparently a bug. But the solution is simple: do not go back to the script. And if you do, do not click OK. Or switch it back to 'File' before clicking OK. Or do not save the script changes.

 

Edited January 9 by comment

[ignotum]

So it's not still a bug in more current versions? This is just a process that I'm using here to deal with some data issues for a client so I have full control over the environment, and it'll be a one-off use so I'm not REALLY worried but "knowledge is power"

Thanks for the help.

[comment]

6 minutes ago, ignotum said:

So it's not still a bug in more current versions?

I don't know (I am currently stuck at v.18). But I wouldn't be surprised if it's still the same.