CSV file template vs corresponding BOD ID path

I have followed your recommendations to model in ION the different steps necessary to export for example data from a Cloud application as a BOD in a delimited file on a local external file server.

This includes the creation of a single-level file template reflecting the structure of the expected CSV file and the generation of an associated BOD.
This BOD will be used to map the standard BOD and its link with the file model from which it is derived will allow the data to be "mapped" during the file generation phase at the connection point.

Everything works not without some difficulty for the first development. Thank you for your support to achieve this first step.

My question is about the following point: When the "flat" file model is created and the BOD is generated, at no time have I seen how to take back the "hand" on the BOD metadata, in particular to fill in the identifier path.

I only noticed that it was the last field of the file model that was associated as a key by default.
Is there any way to improve this?

Because, then in IONView, I see that this is the value that is displayed. In this case, for example, a quantity when it would be more relevant to have an order number.

Thank you for you help

Find more posts tagged with

ION Mapper & Scripting

Accepted answers

All comments

Legacy Contributor

I don't know about cloud, but on-premise I would:

- go to Data Catalog/Object Schemas

- find my custom BOD, download it

- unzip the file, find <BODname>.xml file, and open it in text editor

- find IDXPath element and change it to the desired document id field, save the file

- zip it again, and import it into Data Catalog/Object Schemas

Apart from that, when I click Generate Metadata based on CSV file template, SW lists the fields with assumed datatypes (which are what it takes from sample CSV, and you can change them) and this same screen is saying something like please select Document ID field.. So if you are changing/checking the fields and then just finish the process at the last one, voila, that is your Document ID.

Denis MARETTE

HI @tilen-markez

In my various tests, I also proceeded in 2 steps: generate my BOD by creating xsd and xml files and zipping them as described in the documentation to have control over these metadata. Then, in a second step, I created a file template with the same field names so that when I exported it, everything would work. I had especially taken the precaution of not generating the metadatas from the file template.

But it seems to me that the fact of not having generated the BOD from the file template had caused me problems at the level of the file generation. But now, you put me in doubt. I will check again.

On the other hand, in the cloud, when you declare your file template, I did not see a message telling me like please select Document ID field. I will check again

Thank you for your very responsive and appreciated help

Copyright © 2025 Infor. All rights reserved.