Need to format Date in 'Write' setting of File Connection point setting.

Hello,

In the below highlighted option of FileConnection Point,

The File name comes with date format as, 'RECCONF_2024-07-31_05-34-04-210' , while I need the File name as 'RECCONF_20240731053404210' [without hyphen(-) ]

Is there any way to achieve this?

Find more posts tagged with

General Discussion

Accepted answers

All comments

balkenhol

Documentation doesn't show any options for formatting on these keywords or any sort of replacement functionality.
https://docs.infor.com/inforos/2024.x/en-us/useradminlib_cloud/default.html?helpcontent=iontechconceag_cloud_osm/lsm1436532314824.html&hl=current_datetime

The only way I think you can achieve this within ION is to run the file through a python script task that sets a file name in the header and use the [source] keyword on the File Name Pattern to use that file name from the header. The alternative is to manage the file name before it enters ION and use the [source] keyword.

I'd also like to know if there is a way to achieve this using just the File Name Pattern on the File Connection Point.

Kevin Heiman

adding to Brandon's response. I would suggest using header of [custom_<<Name>>] versus [source]. By definition, source has a specific purpose and it would be less confusing to use the custom_ header. You would add the custom header (ex. customer_timestamp) to the noun / document definition and it will be visible in your options for selection in the File Write.

It would be ideal that your message producer can put this in the header when publishing. Otherwise the scripting option is another way to get the header added/changed.

sample of a script ..

unknown

This is a good solution. However in my case it won't be applicable as, the file I need to write is a custom Flat File.

I appreciate the help. Thanks.

balkenhol

This should be applicable for flat files.

All documents have headers containing metadata within ION regardless of if they are flat files or BODs. These headers are separate from the data contained within the flat file. When you read these in with a script, the contents of the flat file are contained in the "Input Document Content" and the headers attached to the file are contained in the "Input Document Headers".

If you make changes to add the [custom_<<Name>>] as Kevin suggested, the script would just pass the unchanged file contents with the new custom header field to be used within the File Connection Point's write File Name Pattern field.

I had suggested the [source] field because when working with flat files, that [source] field has always contained the file name. I think Kevin's custom header field is a better solution since it doesn't alter the original value in the [source] field.

Copyright © 2025 Infor. All rights reserved.