View Single Post
  #2  
Old March 15th, 2019, 01:12 PM
Dan Korn's Avatar
Dan Korn Dan Korn is offline
FusionPro Senior Engineer / Forum Moderator
 
Join Date: Aug 2008
Location: Chicago, IL
Posts: 4,468
Default Re: Original Input File Name Path

Two questions for you:
1. What exactly are you trying to do with the "original" input file path? What are you trying to accomplish?
2. In what context is this composition happening? In FusionPro VDP Producer? In FP Server via the Server API Web Service? In some other FP Server-based system (such as MarcomCentral or EFI Digital StoreFront)?

FusionPro.Composition.inputFileName returns the actual data file used for the composition, at composition time.

FusionPro.inputFileName should return the original input file path specified in the DEF (Data Definition) file, at both rule validation and composition time. And it does exactly that at composition time in FusionPro VDP Creator, for both regular and Preview compositions.

However, for a job that is collected up and composed via FusionPro VDP Producer or FusionPro Server, the "original" input file is the one that's collected into the Zip file or collect folder.

Even though we're in the FusionPro VDP Server (API) sub-forum, since you mention the word "Scheduler", I presume you're talking specifically about a FusionPro VDP Producer composition. In the case of Producer specifically, the "original" input file is the one in Producer's working directory. And that working directory is usually either a local path on that server, or a UNC path. (And actually, if you do a "Recompose" of the job via the Producer Monitor application, and upload a new input file there, then the "original" path returned by FusionPro.inputFileName will be the one originally uploaded with the job, while the "actual" file used for the composition returned by FusionPro.Composition.inputFileName will be the one you uploaded for the Recompose.)

Therein lies the rub: even if FusionPro.inputFileName returned the path of the original file that you specified in Acrobat, that's probably a local path on your client machine, and the Producer machine probably can't access that path anyway. (Even for full-on FP Server, if you're using the Server API Web Service, it's still generally going to be a path in the Server API's working directory, or in a similar location where the application stores its repository of submitted jobs.)

So, I'm not sure what good knowing that original path is going to do for you. Which brings me all the way around to my first question at the start of this post: For exactly what purpose are you trying to get that "original" data file path, and what are you trying to do with it? If I can understand what your ultimate goal is, then I can probably suggest a way to fulfill it.
__________________
Dan Korn
FusionPro Developer / JavaScript Guru / Forum Moderator
PTI Marketing Technologies | Printable | MarcomCentral
LinkedIn

I am a not a Support engineer, and this forum is not a substitute for Support. My participation on this forum is primarily as a fellow user (and a forum moderator). I am happy to provide help and answers to questions when I can; however, there is no guarantee that I, or anyone else on this forum, will be able to answer all questions or fix any problems. If I ask for files to clarify an issue, I might not be able to look at them personally. I am not able to answer private messages, emails, or phone calls unless they go through proper Support channels. Please direct any sales or pricing questions to your salesperson or inquiries@marcom.com.

Complex template-building questions, as well as all installation and font questions or problems, should be directed to FusionProSupport@marcom.com. Paid consulting work may be required to fulfill your template-building needs.

This is a publicly viewable forum. Please DO NOT post fonts, or other proprietary content, to this forum. Also, please DO NOT post any "live" data with real names, addresses, or any other personal, private, or confidential data.

Please include the specific versions of FusionPro, Acrobat, and your operating system in any problem reports or help requests. I recommend putting this information in your forum signature. Please also check your composition log (.msg) file for relevant error or warning messages.

Please post questions specific to the MarcomCentral Enterprise and Web-to-Print applications in the MarcomCentral forum. Click here to request access. Or contact your Business Relationship Manager (BRM/CPM) for assistance.

Please direct any questions specific to EFI's Digital StoreFront (DSF) to EFI support.

How To Ask Questions The Smart Way

The correct spellings are JavaScript, FusionPro, and MarcomCentral (each with two capital letters and no spaces). Acceptable abbreviations are JS, FP, and MC (or MCC). There is no "S" at the end of "Expression" or "Printable"! The name of the product is FusionPro, not "Fusion". "Java" is not is not the same as JavaScript.

Check out the JavaScript Guide and JavaScript Reference! FusionPro 8.0 and newer use JavaScript 1.7. Older versions use JavaScript 1.5.

return "KbwbTdsjqu!spdlt\"".replace(/./g,function(w){return String.fromCharCode(w.charCodeAt()-1)});

Last edited by Dan Korn; March 15th, 2019 at 01:22 PM..
Reply With Quote