Return field names instead of values

[invaricconsulting]

Never had a need to do this but am being asked, is there a way in FP Desktop to return a variable field's name instead of its value?

 

Apparently copying and pasting the field name into the value is not sufficient in this particular case (will spare the details).

[Dan Korn]

I'm not sure I understand what you're asking. If you know what field's name to ask for, then you know the field's name. The name of the field "X" is "X" by definition. Can you explain more about what you're trying to accomplish?

[invaricconsulting]

Thank you for your response Dan. Here is the scenario as explained to me...

 

The client's requirement is to be able to compose a VDP job and print a proof set with the field names as opposed to the field values showing. It was suggested that they simply create a dummy data file with one record using the field names as the values. The client outright rejected this idea. They consider this as involving extra typing and inviting opportunity for error.

 

Although it may be typically assumed that when you get started with a VDP template, you have a data file, or at least know what your date needs to be, in this client's case, they don't. They import the artwork, draw variable text boxes, then create their variable field names on the fly. After this they inform their customer, these are the fields we're working with, please apply these to your data. So the client recieves the actual data at a later time.

 

The client states this can be done in Microsoft Word mail merge and in Acrobat PDF forms, but they are looking to move to a more dedicated VDP application if they can find one that meets their requirements. In summary, entering field names in "Create new flat file" is acceptable to the client, but any work beyond that is not.

 

[Dan Korn]

Try this in OnRecordStart:

for (var field in FusionPro.Fields)
   FusionPro.Composition.AddVariable(field, field);

[aaronsupremeworks.com]

What I would do is set up the template using your database, then for your proof set the data source to none. That should return te fields or rules as <<rulename>>, then when ready to compose just link back up to your data source and go.

[invaricconsulting]

I tried both of the suggestions and I think they are both workable.

 

 

Thanks!

[Dan Korn]

You can also uncheck the "First row contains field names" box on the "Flat File" step of the Define Data Source Wizard.

[invaricconsulting]

Thanks again. Hopefully with these suggestions the client will find one that is acceptable to them.