Go Back   PTI Marketing Technologies User Community > Off Topic > Reviews, Rants, and General Musings

Notices

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old April 20th, 2015, 07:19 AM
sschardan sschardan is offline
Regular Contributor
 
Join Date: Oct 2008
Posts: 71
Default Feature request

A nice feature to have in VDP Creator would be the ability to easily re-map data fields when assigning a new data source. For example, instead of just getting a warning that the names of the data fields do not match and having to keep the old or use the new, we could be presented with an option of comparing the old to the new and re-map as necessary. Just a thought.
Reply With Quote
  #2  
Old April 20th, 2015, 07:56 AM
step's Avatar
step step is offline
Senior Contributor
 
Join Date: Jan 2010
Location: Charlotte, NC
Posts: 911
Default Re: Feature request

One way of handling this scenario is to assign your data fields to variables that are set in the OnRecordStart callback rule and referencing the new variables in your rules/text frames rather than the actual field names. That way re-mapping your variables is as easy as opening the OnRecordStart rule and re-assigning the field names to the variables without having to edit every specific rule or text box that references that field name. For example if I have a data file with fields "Name", "Phone" and "Address", my OnRecordStart callback would look like this:
Code:
FusionPro.Composition.AddVariable("temp_name", Field("Name"));
FusionPro.Composition.AddVariable("temp_phone", Field("Phone"));
FusionPro.Composition.AddVariable("temp_address", Field("Address"));
I prefixed "temp_" to names to distinguish between the variables I assigned and the variables that are in the data. Then in your rules you'd reference Field("temp_name") instead of Field("Name").

If you want to use the variable you created in a text rule, simply type "temp_name" in the "variable" selector of the Text Editor and click "Insert".

I know that's not as elegant as a GUI pop-up that remaps the variables for you but depending on how much time you spend re-mapping variables in your template, it might still end up saving you some time.
__________________
Ste Pennell
FusionPro VDP Creator 9.3.15
Adobe Acrobat X 10.1.1
Mac OS X 10.10.5

LinkedIn
Reply With Quote
  #3  
Old April 21st, 2015, 10:37 AM
Dan Korn's Avatar
Dan Korn Dan Korn is offline
FusionPro Senior Engineer / Forum Moderator
 
Join Date: Aug 2008
Location: Chicago, IL
Posts: 3,956
Default Re: Feature request

That's not a bad idea. But the devil is in the details.

What specifically do you intend that this "re-mapping" feature would do? It's probably fine to replace variable call-outs in text, where a variable is inserted into the Variable Text Editor dialog, similar to how Font Replacement works. But there are some problems with this approach, since data fields are also used in rules. Automatically replacing field names in Drag-and-Drop rules, XML Template rules, and Switch Wizard rules could work, but things can get tricky in JavaScript.

For instance, would you expect that such "re-mapping" would search through JavaScript rules and replace calls to the Field function? What if the Field name was itself specified in a JavaScript variable, such as in this example?
Code:
var fieldName = (Field("Gender") == "M") ? "MalePhoto" : "FemalePhoto";
return CreateResource(Field(fieldName));
Or what if a rule iterates through multiple fields, like so?
Code:
var r = [];
for (var i = 1; i <= 10; i++)
    r.push(Field("Item " + i));
return r.join("\n");
Another common thing is to create a rule with the same name as a data field, to override the field's value, such as:
Code:
// Rule "State"
return ToUpper(Field(State));
Other scenarios include using the data file as an ExternalDataFileEx to aggregate data field values from multiple records together, calling alternative functions such as FieldChanged, TaggedDataField, and OptionalRuleOrField, and lots of other specialized functionality.

It would be almost impossible for any kind of "field mapper" to account for all of these kinds of ways that fields can be used in rules, so something that merely replaced field names in text could lead to jobs where those are mismatched from what rules are doing.
__________________
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@pti.com.

Complex template-building questions, as well as all installation and font questions or problems, should be directed to FusionProSupport@PTI.com. Paid consulting work may be required to fulfill your template-building needs. Please do not post proprietary font files to this forum.

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)});
Reply With Quote
  #4  
Old April 22nd, 2015, 07:52 AM
sschardan sschardan is offline
Regular Contributor
 
Join Date: Oct 2008
Posts: 71
Default Re: Feature request

Dan,

I completely understand the conundrum with Javascript rules. What I run in to at times is having to pick up an old job where the client required us to delete the old data, so I can not compare the field names of the new data to the old. Yet, the Fusion file would have the old names remembered. Having a list pop up comparing the names would at least provide a shortcut to see what is the same, and what has changed without the trial and error of using the new names and seeing what breaks. Maybe a way to handle the fields used in javascript would be to have a .def file editor. I know, I can just keep dreaming!
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 02:51 AM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
(c) 2011, PTI Marketing Technologies™, Inc.