This documentation is not using the current rendering mechanism and will be deleted by December 31st, 2020. The extension maintainer should switch to the new system. Details on how to use the rendering mechanism can be found here.
The importr can be used to create a bridge between TYPO3 entities and Excel, CSV or other text files.
After installing the extension via one of the possible methods you need to add the Scheduler Task to your tasks.
- Extbase CommandController Task (extbase) - importr:import:initializeservicemanager
The frequency should be as often as possible (e.g.
* * * * *), this way the Importr can be as precise as possible with the import timings.
TYPO3 Composer Mode¶
composer require diego/importr
Via Extension Manager¶
After installing the extension and adding the Scheduler Task you can start configuring your possible imports. These are called Strategies and should be placed on the root of your TYPO3 installation.
A Strategy consists of three main parts. The general configuration, the resource configuration and the target configuration. Every import needs to know from what resource it gets its data (resource) and where to put it (target).
By default the extension ships with an Excel (HDNET\Importr\Service\Resources\Excel), CSV (HDNET\Importr\Service\Resources\Csv) resources and Extbase model (HDNET\Importr\Service\Targets\ExtbaseModel) and database record (HDNET\Importr\Service\Targets\DbRecord) targets.
A simple Strategy can look like this:
before: updateInterval: 100 # Sets th after: createImport: 1: importId: 1 start: tomorrow 0400 filepath: uploads/my_import.csv
HDNET\Importr\Service\Resources\Csv: skipRows: 1 delimiter: ,
HDNET\Importr\Service\Targets\ExtbaseModel: model: VENDOR\MyExt\Domain\Model\MyModel repository: VENDOR\MyExt\Domain\Repository\MyRepository pid: 123 mapping: 0: myPropertyA 1: myPropertyB 8: myPropertyD