Skip to main content
O
ODuinn
Inspiring
February 12, 2018
Question

exportAsFDF: values exported from fields not in the array

  • February 12, 2018
  • 1 reply
  • 700 views

I have the following in a folder level script in a privileged context:

this.exportAsFDF({aFields: ["txtTP.Agent.Broker", "txtTP.Agent.BrokerFullName", "txtTP.Agent.Address", "txtTP.Agent.City", "txtTP.Agent.State", "txtTP.Agent.Zip", "txtTP.Agent.BrokerNo"], cPath: "" + parentPath + agentsFolder + fdfbroker});

This works as intended EXCEPT that it is exporting values from several other fields ( examples: "txtTP.Agent.FirstName", "txtTP.Agent.LastName") that are not included in the intended array. These other fields do have the same non-terminal parent "txtTP.Agent" but my understanding is that the array should limit the export to only the named fields.

I can work-around this by first resetting the excluded fields, but that shouldn't be necessary. I cannot see that a parameter is missing whose absence is causing these other fields to be included, and would appreciate any advice to correct this.

Thank you.

This topic has been closed for replies.

1 reply

try67
Community Expert
try67Community Expert
Community Expert
February 12, 2018

That's probably because of your naming scheme. The period notation is

reserved for declaring groups of fields. It's most likely considering those

fields as members of "txtTP.Agent", and therefore exports all of them.

On 13 February 2018 at 00:10, ddunn@davidsdunn.com <forums_noreply@adobe.com

O
ODuinnAuthor
Inspiring
February 13, 2018

Although I recognize that you are probably correct I am reluctant and perhaps unqualified to say so, but in my limited experience it seems to me the evidence is otherwise.

in the API Reference a comment accompanies the aFields parameter for exportAsFDF. That comment says "Specify non-terminal field names to export an entire subtree of fields (see the example below)." Using a non-terminal field is therefore a shortcut to exporting all child fields and values of that parent. The corollary to using the non-terminal shortcut is to go to the trouble of specifying an array limiting the export to specific fields.

Every discussion of the word "array" throughout the API is accompanied by the word "specifics." The objective of arrays is precision. In the context of exportAsFDF then, an array of fields ought to limit the export to only the named fields, regardless of whether they are part of a larger family. This leads me to believe that the inclusion of all omitted child fields with an array of specific fields in the same family is a program defect that needs to be fixed. For example, you won't get that result in the context of calculated values of numeric child fields.

try67
Community Expert
try67Community Expert
Community Expert
February 13, 2018

I agree that it shouldn't work like that. I was just trying to guess why it might. Neither you nor I know the insides of this function, after all... You can always report it to Adobe as a bug: Feature Request/Bug Report Form

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices