dalespivey Posted April 27, 2014 Share Posted April 27, 2014 Hi, would love some help with this one. I've updated my Mavericks Mac to FP VDP 9.2.26 now my barcode 128 rule is giving me an incorrect output. The JS code that worked in earlier versions was: return Make128Barcode (Field("formid")); I've tried the two preloaded rules for 128 and still get non-working results. I've attached the template and other files, nothing real special here. All help is appreciated, let me know what I've overlooked.PTI.zip Quote Link to comment Share on other sites More sharing options...
Alex Marshall Posted April 28, 2014 Share Posted April 28, 2014 Why not use the XML Rule template, i.e. 128 B Barcode. Then in the frame where the barcode will appear, insert this rule from the "Variable" drop box. No need to apply the font as it is specified in the Rule. Does this work? Quote Link to comment Share on other sites More sharing options...
dalespivey Posted April 28, 2014 Author Share Posted April 28, 2014 Hi Alex, Nope, that doesn't work either. I still get a non-working barcode. This rule and my JS code above still works in 9.1 http://i57.tinypic.com/20pd7ki.png Quote Link to comment Share on other sites More sharing options...
Alex Marshall Posted April 28, 2014 Share Posted April 28, 2014 send me your files to fusionprosupport@pti.com Quote Link to comment Share on other sites More sharing options...
Dan Korn Posted April 28, 2014 Share Posted April 28, 2014 Exactly which version of FusionPro were you using previously that generated the barcode correctly? Also, do you have an example of output from that previous version with the correct barcode? Quote Link to comment Share on other sites More sharing options...
dalespivey Posted April 28, 2014 Author Share Posted April 28, 2014 Hi Dan, I used Mac FP VDP 9.10 with my JS code in my original posts, files are also attached to post. Here's a screenshot of the merge, I'll email an example to the support address in a minute. http://i59.tinypic.com/2nta39d.png Quote Link to comment Share on other sites More sharing options...
Dan Korn Posted April 28, 2014 Share Posted April 28, 2014 Thanks for the information, Dale. I've identified the cause of the problem, and it will be fixed in an upcoming release. In the meantime, you can work around the problem in your 9.2 installation by editing the Builtins.js file at "/Library/Application Support/PTI/FusionPro". Please back up the Builtins.js file before modifying it! Open the file in any editor, such as TextEdit, and search for "ConvertWindowsEncodingToNative". There should be two instances of this string in the file. All you need to do is remove these strings, leaving the rest of the line intact. So there's a line like this in the file: return ConvertWindowsEncodingToNative(Make128BarcodeBase_Result); That should be changed to this: return (Make128BarcodeBase_Result);And there's a second instance for 2 of 5 barcodes like this: return ConvertWindowsEncodingToNative(barcode); Which should be changed to this:return (barcode);Then save the file. This should fix the problem. Quote Link to comment Share on other sites More sharing options...
dalespivey Posted April 29, 2014 Author Share Posted April 29, 2014 Dan, this did the trick, thanks! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.