Enfocus Community

jan_suhr wrote: ↑Thu May 09, 2024 11:28 pm Try to change the XML to be just one line, no line feeds

This had zero effect on execution errors.

jan_suhr wrote: ↑Thu May 09, 2024 6:35 pm Have you enabled the Debug mode in your Switch

I have, and no additional debug messages are generated. The entire effort the last few days on this alternate flow have been a failure. I appreciate the help, but unless someone here has a magical solution I'm done wasting my time on it any further.

Next debugging test: 1. Removed all variables in POST Body and replaced with hard coded values in HTTP request 2. Removed Calculated URL value and Replace with hard coded URL in HTTP request Result: 1. Error regarding converting theCustomBody did not occur. 2. POST still fails with the message "...

I suggested to send a copy of that file to one more folder that ends and don't have any outgoing connections. That folder can be set to a static path on disc and that path hardcoded to your script. Since the files always will be there in that folder you will succeed with the rest. Ive made this cha...

This flow is never going to work if I can't stop the file from being moved and then deleted and can get a valid path for the POST body. Time to quit wasting my time today. This looked so promising this morning, but not any longer. It should not be this hard.

Hard coding String 1 and string 2 did not fix the issue. Upon reflection the file is no longer in the input directory because switch is moving it... Grrrrrr

Now I have to modify the flow so the file is not moved anywhere but a known network path and hope that is the problem. Sheesh!

If it is the XML you posted recently you are using it is not valid. It is missing a > before <RuleSetPath> There is also at the end a > missing. That was a good catch Jan. I did not notice that. I must have selected the > and the </RuleSetPath> when editing out the double quotes from using it in th...

The stuff you send to the server is apparently wrong. Your comment is totally focused on the wrong thing. The stuff I'm attempting to send is correct. Switch apparently has a problem converting it to a sting that can be sent. the 500 error is because Switch didn't actually send anything in the POST...

Well, good luck on your Switch journey Tom. I'm apparently going to need more than good luck. It is not working. Sigh... this is one of the many reasons there needs to be a debugger in Switch. Messages just doesn't cut it. 1st message: Add Input Send Remote Trigger V2 HTTP request with varible URL ...

Also if the filename always starts with the job number you don't need the first jobno folder in my suggested flow. You can just set the case to: case=[Job.NameProper:Before="-",Segment="6-"] Since the job name is required as a sting in the post body content I can use jobno and n...

OK got it upgraded to v20 but still see no Post Body in the HTML request v20

If that's correct - here is a flow that does that using private data: This is the kind of thing I started trying to do, but could not get past the URL selection. The Private Data Magician is something that I didn't try but I tried 4 other apps with no success. Go figure... I do not see a Post Body ...

I must say, teetomterrific, that the tone of some of your posts is not the style of this forum. This is a place where we meet to help each other to the best of our abilities, not to sling mud. Mud? So you would rather hear a dishonest assessment of Switch's inadequacies? Clearly my frustration with...

Thanks, could you also provide a couple of example jobnames? This is an example of a file name that would be dropped into the hot folder that contains a job name: 037984-24_001_8-C-Y.pdf The Job Name is 037984-24 The Job number is 037984 and the production year is 24 for 2024 the last digit of the ...

2. You are not going to use job.getPath since it will give you the path to the file that enters your script. The file we put in the folder, point 1 above, is now forgotten by Switch. Since this location is static you have to write that path in the script and then use the variable job.Name. Like thi...