sirdiego/importr

Flexible importer for all kinds of files!

importr

, _(*1)

The importr can be used to create a bridge between TYPO3 entities and Excel, CSV or other text files., _(*2)

Installation

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, _(*3)

The frequency should be as often as possible (e.g. * * * * *), this way the Importr can be as precise as possible with the import timings., _(*4)

TODO: Screenshot, _(*5)

TYPO3 Composer Mode

composer require diego/importr, _(*6)

Via Extension Manager

TODO: Screenshot, _(*7)

Usage

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., _(*8)

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)., _(*9)

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., _(*10)

A simple Strategy can look like this:, _(*11)

Configuration, _(*12)

before:
  updateInterval: 100 # Sets th
after:
  createImport:
    1:
      importId: 1
      start: tomorrow 0400
      filepath: uploads/my_import.csv

Resources, _(*13)

HDNET\Importr\Service\Resources\Csv:
  skipRows: 1
  delimiter: ,

Targets, _(*14)

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