Data Import add-on state

Support
#1

Hi,

in our Jmix 2.x application, which is currently under development, we plan to create a general data export-import function. The DataTools add-on has such a function, but it only supports json format. We saw that there is a Data Import add-on that is currently in incubation state and has not been officially released yet.

We would prefer this add-on because of its configurability (ImportConfiguration) and support for multiple data formats.

In this regard, we have the following questions:

  • since it has not been officially released yet, is it suitable for use in a production environment in its current state?

  • when is the official release expected?

  • are you planning to provide this solution with a UI?

We found an issue for it, but unfortunately there is no more information in it

  • do you plan to use this solution for export as well, i.e. to create an XML or JSON file based on the given parameters, and it could be imported in another Jmix app?

Thanks,
Peter

2 Likes
#3

Hi,

The DataImport add-on is used for importing data from any arbitrary source. For example, you already have some external system that generates files with exported data and need to import this data to Jmix app. In this case, you can use the DataImport add-on because it allows you to configure fields mappings and so on. Also, keep in mind that the DataImport add-on does nothing regarding exporting data.

If you need the import-export functionality, take a look at the io.jmix.core.EntityImportExport service. A javadoc for the io.jmix.core.EntityImportPlan describes how you can fine-tune the import process. If the task is to do the import-export between multiple Jmix applications, then I would suggest to use this API.

As for our plans regarding the making the DataImport add-on and developing the UI for it, we don’t have it in our nearest roadmap. The add-on was implemented as an experiment quite a long time ago and we didn’t return to it since then. If the DataImport add-on in its current state looks suitable for you, you may use it, its source code is on GitHub and you can always make an own copy or modify it. But there are no guarantees that we won’t change its API in the future.

#4

Hi Maxim,

Thanks for the clarification and the info.
In fact, we would need a mixture of the two solution :slight_smile:
We will go through the source code in more detail and see what the possibilities are.