mclisa81 Posted January 7, 2011 Share Posted January 7, 2011 Hi, We've recently upgraded from FP6.2 to 7.1. I have been using the same "OnNewOutputFile" rule for quite some time and now after upgrading it gets an error when composing. Nothing has changed with this template besides the upgrade. Can someone let me know what I need to change now to fix this. Thanks. msg error OnNewOutputFile, line 1: Error: In Field(), no data source defined or data could not be loaded. FusionPro.Composition.outputFileName="604292-"+(Field("Barcode")+".pdf") Link to comment Share on other sites More sharing options...
mclisa81 Posted January 18, 2011 Author Share Posted January 18, 2011 Does anyone have any ideas on this? My output seems ok, I'm just curious as to why after upgrading I am getting an error. Link to comment Share on other sites More sharing options...
Dan Korn Posted January 19, 2011 Share Posted January 19, 2011 I don't have any problems with the OnNewOutputFile rule, in a test job with similar logic, using the latest version of FusionPro. Can you collect up a minimal example job which demonstrates the problem and either post it here or send it to Support? Link to comment Share on other sites More sharing options...
mclisa81 Posted January 19, 2011 Author Share Posted January 19, 2011 Hi Dan, I'll post the collected files, along with 2 message files. Same data used - (1 with FusionPro 6.2P1c, 1 with FusionPro 7.1P1c). There has been no changes to this template except for the update to FusionPro and as you can see after the update I am now getting an error. ThanksAS00010_Stampimage.zip Link to comment Share on other sites More sharing options...
Dan Korn Posted January 20, 2011 Share Posted January 20, 2011 That message can be safely ignored. As you have seen, your output file will still be properly named; you'll just get the false message once per composition. So it's a reporting bug, against which I've created case FP-11499. I didn't see the problem when I tried it in the Frodo Travel tutorial, because that job does preprocessing for FP Expression images, and the preprocessing suppresses that message. Turning on imposition stacking will also invoke preprocessing and suppress the message. Link to comment Share on other sites More sharing options...
mclisa81 Posted January 20, 2011 Author Share Posted January 20, 2011 Thanks for your help Dan. Link to comment Share on other sites More sharing options...
aronallenson Posted March 3, 2011 Share Posted March 3, 2011 Hi Dan, I have the same issue but if I try to use any PDF security such as no changes to the PDF, no output file is produced and FP hangs. Any ideas? Aron Link to comment Share on other sites More sharing options...
aronallenson Posted March 3, 2011 Share Posted March 3, 2011 I am running into the same error but no output file is produced. This occurs when I turn on PDF security. If I turn off PDF security, I get the same response as is written above. Any ideas Link to comment Share on other sites More sharing options...
Dan Korn Posted March 4, 2011 Share Posted March 4, 2011 I am running into the same error but no output file is produced. This occurs when I turn on PDF security. Sorry, that is a different bug, one about which I was not aware. This bug doesn't have anything to do with the OnNewOutputFile rule. You'll get the same crash if you have the "Output to multiple files" box checked and you're using PDF Security, regardless of whether you're trying to rename the output file in OnNewOutputFile or doing preprocessing. Apparently that particular combination of features (output to multiple files with PDF security) is not covered in our QA testing. I've entered case FP-11516 regarding this issue, and we'll make sure it gets fixed in the 7.2 release. (Actually, I've already fixed it.) In the meantime, you'll have to either not use security or output to a single file. Or you can compose to a non-PDF-based output format (which ignores the PDF Security settings). If these workarounds are not acceptable, please contact Support and they will escalate the issue. If I turn off PDF security, I get the same response as is written above. That's just the aforementioned reporting bug (FP-11499), which is harmless, although that's targeted for a fix in 7.2 as well. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.