Setting Filename Based on Custom BOD -- but not exported field

I have a custom BOD that is created via a data flow and exported to an XML file. I need to set the output filename based on some logic related to the BOD content, but not exactly a field listed in the file template.

For example, the BOD has a field/element called Company. If its value is say 'ABC123', the filename should be something like FileType1_[current_date].xml, if the file name is 'XYZ456' or 'QRS 789', it might be FileType2_[current_date].xml, etc. In any case, the strings such as 'FileType1' and 'FileType2' do not exist in the output file contents.

It seems that custom header fields might be the best way to tackle this, but I am new to scripting and not entirely sure how to make that work. I have seen a couple of other posts that seem to set input variables for the content or headers and then output the content and updated headers. While I can set up multiple input variables within the script, in the data flow script input parameters, it only lists one. I'm not sure if that is a limitation or not. I tried it as is with just one input parameter and something of a guess at the code. However, when I tried to activate the data flow, I got some cryptic error saying "Message: Property 'outputVariable0' is not unique. All properties must be unique." I have no outputVariable0, so it must be a setup issue on my part.

Any suggestions on how to approach this would be much appreciated, especially if you have screenshots or snippets about the code or the script parameter setup.

Thanks.

Find more posts tagged with

ION Connect

Accepted answers

unknown

Thanks to much help from Kevin and support from Sheryll, we were finally able to get this to work. Thank you both! We wanted to post a resolution here so that others could benefit from what was done.

Below is a sample script we ended up using (with some specific string values tweaked). In it, we look for the value of an element called Company in the input message and use some logic to set an output value for a custom header called custom_LocHdr. Note that custom must, at this point, use a lowercase c -- more on this later.

I used input_content and output_content for the message content script variables and input_headers and output_headers for the script header variables as is shown earlier in the post.

[View:/cfs-file/__key/communityserver-discussions-components-files/73/ScriptForCustomHeader.txt:320:240]

The Schema that we are attaching the custom header to needs to have that custom header defined in the Data Catalog under Object Schemas. Note that here it requires the name to start with an uppercase C: Custom_LocHdr.

In the File Connection Point, in the File Name Pattern field, if you hit Ctrl-Spacebar, it pops up a list of options you can use to help generate dynamic file names. One of these is listed as Custom_<<Name>>. Select that option, which puts [Custom_<<Name>>] into the field, and then change it to read the name of your custom field within square brackets: [Custom_LocHdr] in this case. Note that this must also use a capital C in Custom.

Infor is going to take a look at the upper and lower case situation, but the cases I have spelled out here work for me.

All comments

Kevin Heiman

In the Data Flow when using scripting you should have ability for Input parameters and Output Parameters.

Script would have matching input / outputs.

and supporting code to add or change a header.

output_headers = json.loads(input_headers)

# add a customer header for guid

custom_guid = "custom_guid"

output_headers[custom_guid] = batchUUID

we always recommend that you update or add the instances and several other desirable Headers on the output.

This is also covered in the documentation.

unknown

It's very strange. That second input variable just isn't there in the Script Input Parameters:

I've tried deleting them and re-adding them without luck. I always get one or the other, but not both.

unknown

Check that. I deleted the script from the data flow and then re-added it. Then they both appeared.

unknown

Progress, but errors:

If all I have to use for input is a One View intermediate XML document, do you have suggestions on how to take that (perhaps using XML-to-JSON converter) and use the Testing facility with separate headers and content? My apologies for my lack of knowledge here.

Kevin Heiman

Python can parse XML to fetch the value for your headers. As I interpret your requirement, there is no reason to convert to JSON in this case. You could even just do a string search in python if you don't want to use a XML parser.

Be sure to set the input payload to the output payload. And add any headers to the input Header.

the Testing tool works well for this scenario so you can refine your code and see the input and output. Paste the Oneview XML in there. Create a simple sample JSON headers that your code adds to or changes.

example:

{ "messageId" : "SomeStrring",

"fromLogicalId" : "SomeStrring",

"toLogicalId" : "SomeStrring",

"tenantId" : "SomeStrring",

"accountingEntity" : "SomeStrring",

"location" : "SomeStrring",

"documentId" : "SomeStrring",

"variationId" : 522552,

"revisionId" : "string",

"batchId" : "string",

"batchSequence" : 522552,

"batchSize" : 522552,

"batchRevision" : 522552,

"batchAbortIndicator" : false,

"instances" : 522552,

"source" : "SomeStrring",

"custom_one": "SomeStrring"

}

unknown

That was very helpful. Thank you. I was able to complete the programming and test successfully. The one really odd thing is the after the script in the data flow is a file connection point. Sending a document through gives no errors, but One View never shows the document going to the connection point. When I delete the script from the data flow, the file is written. I can't figure out why that might be. I would at least expect it to show errors somewhere. It's like it went into the script and never came out.

Copyright © 2025 Infor. All rights reserved.