@@ -42,8 +42,8 @@ The source system of your Import Provider has a simple database table where webp
For the import process you can use this ID as a **unique identifier** for your import objects because it is unique and you know exactly which entity is requested.
1. Your ImportProvider tells the CMS Import the structural attributes of a group of entities (e.g. sites). ("Hey QUIQQER, these are my source CMS pages, each with a unique identifier i can use to identify things!")
2. Each MetaEntity is then fetched as an ImportEntity which contains all the necessary data to create this entity as an object in the QUIQQER system. ("Hey ImportProvider - give me the ImportEntity with unique identifier XYZ from your source CMS!")
1. Your ImportProvider tells the CMS Import the structural attributes of a group of entities (e.g. sites). ("Hey QUIQQER, these is the hierarchy of my source CMS pages, each with a unique identifier i can use to identify them!")
2. Each MetaEntity is then fetched as an ImportEntity which contains all the necessary data to create this entity as an object in the QUIQQER system. ("Hey ImportProvider - give me the ImportEntity with unique identifier XYZ from your source CMS so i can import it to QUIQQER!")
```php
<?php
...
...
@@ -72,8 +72,6 @@ class MyImportProvider extends \QUI\CmsImport\AbstractImportProvider
}
```
Unique identifiers
### Keeping entity IDs in QUIQQER
You may want to keep IDs from you source system in QUIQQER. For this purpose some ImportEntity classes implement `\QUI\CmsImport\Entities\CustomQuiqqerIdInterface` which allows to set a (unique) ID for the QUIQQER system.
