url stringlengths 50 196 | text stringlengths 3 17.2k | heading stringlengths 2 103 | embeddings list |
|---|---|---|---|
https://pimcore.com/docs/platform//Data_Importer/Installation#for-older-versions | For Older Versions
To install the Data Importer bundle for older versions of Pimcore, please run the following commands instead:
composer require pimcore/data-importer
bin/console pimcore:bundle:enable PimcoreDataImporterBundle
bin/console pimcore:bundle:install PimcoreDataImporterBundle
Make sure the Datahub bundle'... | For Older Versions | [
-0.41699427366256714,
0.1546667367219925,
-0.1567651331424713,
0.07971421629190445,
-0.03699176758527756,
-0.12696224451065063,
0.29464030265808105,
0.046588361263275146,
-0.3168841004371643,
0.31013208627700806,
-0.2527042031288147,
0.3390274941921234,
0.00819720420986414,
0.2389858365058... |
https://pimcore.com/docs/platform//Data_Importer/Installation#bundle-configuration | Bundle Configuration | Bundle Configuration | [
-0.1497521698474884,
-0.7734434604644775,
-0.1553780883550644,
0.29922330379486084,
0.2179914116859436,
0.0595809631049633,
0.41703736782073975,
-0.20630677044391632,
-0.17295368015766144,
0.117451973259449,
-0.02126796543598175,
0.16865700483322144,
-0.127521812915802,
0.2348327785730362,... |
https://pimcore.com/docs/platform//Data_Importer/Installation#import-execution | Import Execution
The imports are executed asynchronously in the background. The processing can be done via executing commands on a regular
basis or by utilizing symfony messenger. Either of the two needs to be configured. | Import Execution | [
-0.06681837886571884,
0.012479715049266815,
-0.21614107489585876,
-0.0049805836752057076,
-0.18718263506889343,
-0.2279355525970459,
0.4237322509288788,
-0.07200663536787033,
0.05904795229434967,
0.20851679146289825,
-0.14360615611076355,
-0.11349298804998398,
0.12262046337127686,
0.013445... |
https://pimcore.com/docs/platform//Data_Importer/Installation#command-based | Command Based
For command based importing, following commands need to be executed on regular base. The actual interval depends
on use cases and system environment.
# Process import queue items that can be executed in parallel
*/5 * * * * php /home/project/www/bin/console datahub:data-importer:process-queue-parallel --p... | Command Based | [
-0.22948844730854034,
-0.2944258153438568,
-0.212009996175766,
-0.18043571710586548,
-0.27121052145957947,
-0.2064366340637207,
0.39467668533325195,
-0.007719088811427355,
0.044345494359731674,
0.23621629178524017,
-0.024075118824839592,
-0.12360332906246185,
0.07769015431404114,
0.2381558... |
https://pimcore.com/docs/platform//Data_Importer/Installation#symfony-messenger-based | Symfony Messenger Based
For symfony messenger based importing, at least following configuration needs to be done in symfony configuration:
pimcore_data_importer:
messenger_queue_processing:
activated: true
If activated, the processing is kicked off automatically as soon as an import is prepared.
In additio... | Symfony Messenger Based | [
-0.22409434616565704,
-0.2524506151676178,
-0.11849305033683777,
0.0069206710904836655,
-0.0313141904771328,
-0.33990800380706787,
0.4574353098869324,
-0.10789713263511658,
0.09050372987985611,
0.3617623746395111,
-0.18321946263313293,
0.001645364216528833,
0.06524541229009628,
0.095772340... |
https://pimcore.com/docs/platform//Data_Importer/Installation#cron-execution | Cron Execution
Import configuration can be setup to be executed on regular base by defining a cron definition. To make sure, the cron
definitions are checked on regular base, following command needs to be executed on regular base. The actual interval depends
on use cases and system environment; the shorter, the more ac... | Cron Execution | [
-0.3432917892932892,
-0.09229625761508942,
-0.1642962098121643,
-0.2187681943178177,
-0.14713044464588165,
-0.20605334639549255,
0.29837656021118164,
-0.04606457054615021,
0.07311045378446579,
0.21328145265579224,
0.17631690204143524,
0.21502545475959778,
-0.2669183909893036,
0.28921508789... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Data_Sources#data-sources | Data Sources
Every data importer configuration needs a data source. Following data sources are available and can
be configured. | Data Sources | [
-0.4574468433856964,
0.14052757620811462,
-0.18174955248832703,
0.07489432394504547,
0.16994230449199677,
-0.29850465059280396,
0.45968902111053467,
-0.08950667828321457,
-0.11722820997238159,
0.3635765016078949,
-0.3523601293563843,
-0.010871772654354572,
0.1274140477180481,
0.49179804325... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Data_Sources#asset | Asset
Loads data from an asset stored within the Pimcore instance. | Asset | [
-0.3056051433086395,
-0.15998221933841705,
-0.16604268550872803,
0.4591439664363861,
0.028485899791121483,
-0.2922780215740204,
0.3886083960533142,
-0.05156049504876137,
-0.06344358623027802,
0.16380345821380615,
-0.2365993857383728,
0.5675492286682129,
0.2588118016719818,
0.08913111686706... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Data_Sources#configuration-options: | Configuration Options:
Path to asset
| Configuration Options: | [
-0.21190646290779114,
-0.259934663772583,
-0.22283756732940674,
-0.006499129347503185,
0.2778901755809784,
-0.1389550119638443,
0.357229620218277,
0.16718389093875885,
-0.1874283105134964,
0.2649907171726227,
0.14295953512191772,
0.4073967933654785,
-0.054196689277887344,
-0.09286526590585... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Data_Sources#sftp | SFTP
Loads data from a (remote) sftp location. | SFTP | [
-0.19303151965141296,
0.05881305783987045,
-0.14811141788959503,
0.18452061712741852,
-0.18690235912799835,
-0.3412891924381256,
0.18738672137260437,
0.12762123346328735,
0.320864737033844,
0.12060847133398056,
0.05593671649694443,
-0.0657433271408081,
0.3485680818557739,
0.619778513908386... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Data_Sources#configuration-options: | Configuration Options:
Host
Port
Username
Password
Remote Path: Absolute path on remote location.
| Configuration Options: | [
-0.23039622604846954,
-0.2968432307243347,
-0.0906912311911583,
-0.39592939615249634,
-0.15421012043952942,
-0.43792781233787537,
0.36242347955703735,
0.16126464307308197,
-0.09593382477760315,
0.24105583131313324,
-0.004943355917930603,
0.23971980810165405,
0.23198436200618744,
-0.1870249... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Data_Sources#http | HTTP
Loads data from a (remote) http location. | HTTP | [
0.011739484034478664,
-0.14596588909626007,
-0.2571944296360016,
0.2318284511566162,
-0.1583239883184433,
-0.3446551263332367,
0.21669329702854156,
-0.014728627167642117,
0.10658783465623856,
0.03089245781302452,
-0.004060471896082163,
-0.018256548792123795,
0.40537890791893005,
0.06706199... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Data_Sources#configuration-options: | Configuration Options:
Schema: one of http:// or https:// which is prepened to the URL.
Url: Url to file without schema definition (which is added based on schema configuration due
to security reasons).
This implementation uses php wrappers internally, so
encoding username and password is supported as follows: user... | Configuration Options: | [
0.15299980342388153,
-0.2742011845111847,
-0.11202691495418549,
-0.13430523872375488,
0.095273457467556,
-0.2589343190193176,
0.13289329409599304,
-0.08642023801803589,
-0.054903652518987656,
0.28613680601119995,
0.2924940884113312,
-0.24007613956928253,
0.07755754142999649,
0.032166533172... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Data_Sources#push | Push
The push data source does not download the data from a remote location, it provides a http endpoint
where data can be pushed to via a POST request.
The data needs to be in the configured file format and provided as raw content of the POST request. The
push data source internally uses php://input to read the conten... | Push | [
-0.40773969888687134,
-0.35648927092552185,
-0.08587043732404709,
-0.0037592612206935883,
-0.22128061950206757,
-0.3881264328956604,
0.060423191636800766,
0.03254074603319168,
-0.2430160641670227,
0.10536040365695953,
-0.19535942375659943,
0.28285032510757446,
0.3052094876766205,
0.4084766... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Data_Sources#configuration-options: | Configuration Options:
API Key: API Key that needs to be set as authorization header for every push request.
Ignore not empty queue: By default, imports are only started when import queue is empty
(see also Import Execution Details). Thus pushing data to the
endpoint when import queue is not empty would result in an... | Configuration Options: | [
0.005347716622054577,
-0.34383466839790344,
-0.13930727541446686,
-0.28019043803215027,
-0.12837831676006317,
-0.2782927453517914,
0.02954138070344925,
-0.1216554045677185,
0.20552091300487518,
0.12777014076709747,
0.11348919570446014,
0.1169791966676712,
0.2943146526813507,
0.194469779729... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/File_Formats#file-formats | File Formats
The source data needs to be in an interpretable format for the importer. Following interpreters can
be configured: | File Formats | [
-0.2961357831954956,
-0.06264628469944,
-0.23722097277641296,
0.1303590089082718,
0.26802098751068115,
-0.158161461353302,
0.2078874260187149,
0.2945135235786438,
-0.009883401915431023,
0.3315631151199341,
-0.19655051827430725,
0.08367655426263809,
-0.02051408588886261,
0.349370539188385,
... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/File_Formats#csv | CSV
The source data is interpreted as CSV. | CSV | [
-0.04039116948843002,
-0.3126400411128998,
-0.2419499158859253,
0.06374810636043549,
0.13468101620674133,
-0.1696365922689438,
0.19245584309101105,
0.2726577818393707,
-0.10601437091827393,
0.22398604452610016,
0.09523169696331024,
0.036857154220342636,
-0.03474370762705803,
0.319850414991... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/File_Formats#configuration-options: | Configuration Options:
Skip First Row: If activated, first row will be used as column names and not interpreted as data row.
Delimiter
Enclosure
Escape
Internally the adapter uses fgetcsv function of php. | Configuration Options: | [
-0.08791705220937729,
-0.37984463572502136,
-0.1634759157896042,
0.08792269974946976,
0.3159419596195221,
0.0002726935490500182,
0.4227636158466339,
0.14470157027244568,
0.12241015583276749,
0.5407545566558838,
0.17369645833969116,
0.13921719789505005,
0.07277074456214905,
0.21246892213821... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/File_Formats#json | JSON
The source data is interpreted as JSON.
The adapter expects an array of json objects and reads all first level attributes as separate fields.
If one field contains sub objects (like technical_attributes) in the example below, this object
is interpreted as array in one field (and needs to be considered in the trans... | JSON | [
0.11691664159297943,
-0.39525818824768066,
-0.18878796696662903,
0.3205379545688629,
0.2443767488002777,
-0.08086100220680237,
0.2803281545639038,
0.08444786816835403,
0.2878568172454834,
0.3012440800666809,
0.16967500746250153,
0.277446448802948,
0.143944650888443,
0.2225794643163681,
0... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/File_Formats#xlsx-(excel) | XLSX (Excel)
The source data is interpreted as XLSX Excel file. | XLSX (Excel) | [
-0.23218153417110443,
-0.1492055058479309,
-0.19316740334033966,
0.08653780072927475,
0.08757542073726654,
-0.10070134699344635,
0.007858609780669212,
0.34072911739349365,
-0.17319172620773315,
0.2584994435310364,
-0.20590554177761078,
0.007580773904919624,
0.06942296773195267,
0.429333984... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/File_Formats#configuration-options: | Configuration Options:
Skip First Row: If activated, first row will be used as column names and not interpreted as data row.
Sheet: Name of data sheet to be imported.
Internally the adapter uses phpspreadsheet to read the data. | Configuration Options: | [
-0.0697435811161995,
-0.5178841352462769,
-0.17094752192497253,
0.06640473008155823,
0.18307630717754364,
0.20574957132339478,
0.4232274293899536,
0.18531166017055511,
0.1698385328054428,
0.4763279855251312,
0.03216632083058357,
0.09020006656646729,
0.2056867778301239,
0.2232101857662201,
... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/File_Formats#xml | XML
The source data is interpreted as XML.
The adapter expects a list of data elements at the configued xpath and reads all first level elements
of the data elements as separate fields. If one element contains sub elements (like technical_attributes) in the example
below, this the sub elements are interpreted as array ... | XML | [
0.033904388546943665,
-0.5185436010360718,
-0.1743863821029663,
0.317653626203537,
0.6165262460708618,
-0.06098164990544319,
0.3673146665096283,
-0.21850083768367767,
0.36846235394477844,
0.33041954040527344,
0.005290589760988951,
0.3016815185546875,
-0.015648694708943367,
0.39319008588790... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/File_Formats#configuration-options: | Configuration Options:
XPath: XPath to the elements to be imported. For the sample below it would be /root/item.
Schema: XSD Schema the import data should be validated against. If not defined, to validation takes place.
Sample File:
<?xml version="1.0"?>
<root>
<item>
<title_de&... | Configuration Options: | [
-0.22292618453502655,
-0.2928377687931061,
-0.058169618248939514,
0.2749379873275757,
0.192378431558609,
-0.10574069619178772,
0.19275158643722534,
0.06737010180950165,
0.6699854135513306,
0.28159454464912415,
-0.059970904141664505,
0.15368086099624634,
0.07801448553800583,
0.0063285827636... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/File_Formats#custom-file-formats | Custom File Formats
You can import any file format using custom adapters. | Custom File Formats | [
-0.35078737139701843,
-0.2869437634944916,
-0.23955589532852173,
0.03592023625969887,
0.16212326288223267,
-0.041876986622810364,
0.2689336836338043,
0.24868148565292358,
0.03399144113063812,
0.15516220033168793,
-0.3142719864845276,
-0.025759385898709297,
-0.18421627581119537,
0.445071160... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Import_Preview#import-preview | Import Preview
The import configuration allows to show a preview of the data which helps
to setup the mapping configuration and
validate the expected results.
The preview interprets the file the same way as actual import data sources
will be interpreted when executing the import and shows one record of the preview
fi... | Import Preview | [
-0.5831827521324158,
-0.3464009463787079,
-0.10858017206192017,
0.0508895218372345,
-0.25785019993782043,
-0.05246853455901146,
0.07273928821086884,
0.2657693326473236,
0.019305353984236717,
0.2967457175254822,
-0.46256449818611145,
0.11812804639339447,
0.214059516787529,
0.116034291684627... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Resolver_Settings#resolver-settings | Resolver Settings
Resolver settings are responsible to define to which Pimcore data imported data should
be imported to and consists of following parts:
| Resolver Settings | [
-0.184027761220932,
-0.1718893200159073,
-0.12508071959018707,
0.005811244249343872,
0.2351948469877243,
-0.18901021778583527,
-0.08813076466321945,
-0.13242781162261963,
-0.2419082671403885,
0.1312393993139267,
-0.32671427726745605,
0.30159276723861694,
0.285274475812912,
0.00968227814882... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Resolver_Settings#class | Class
Define the Pimcore data object class of the imported data. | Class | [
-0.3859283924102783,
-0.1628296822309494,
-0.19481106102466583,
0.2900635004043579,
0.24256132543087006,
-0.2238103747367859,
0.08802364766597748,
0.09503186494112015,
-0.3628922402858734,
0.24002882838249207,
-0.19220755994319916,
0.3081169128417969,
-0.016523154452443123,
0.3704845011234... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Resolver_Settings#element-loading | Element Loading
Define a strategy the importer should use for looking for existing Pimcore data objects in order
to update them instead of creating new data objects.
Following strategies are available: | Element Loading | [
-0.10876189917325974,
-0.17214345932006836,
-0.23478591442108154,
0.2751128375530243,
-0.006523554213345051,
-0.3521186411380768,
0.3196991980075836,
-0.0868431031703949,
0.2698301672935486,
0.37163421511650085,
-0.3620908260345459,
0.22835519909858704,
0.280882865190506,
0.509114146232605... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Resolver_Settings#loading-strategy:-no-loading | Loading Strategy: No Loading
Does not look for any existing Pimcore data objects. Import always creates new data objects. | Loading Strategy: No Loading | [
-0.11915174126625061,
-0.14503860473632812,
-0.15017877519130707,
0.36392953991889954,
0.061494261026382446,
-0.5641927123069763,
0.24092218279838562,
0.00724272383376956,
-0.030549637973308563,
0.0680253654718399,
-0.600546658039093,
0.3212454319000244,
0.16835084557533264,
0.360700845718... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Resolver_Settings#loading-strategy:-id | Loading Strategy: Id
Look for data objects based on their id.
Data Source Index: Field of import that contains the id to look for.
| Loading Strategy: Id | [
0.0514901801943779,
-0.13664181530475616,
-0.2307320237159729,
0.3421053886413574,
-0.1112135797739029,
-0.363433301448822,
0.3537534475326538,
0.22193144261837006,
0.37268713116645813,
0.13422590494155884,
-0.3613763451576233,
0.10780617594718933,
0.2716508209705353,
0.5446409583091736,
... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Resolver_Settings#loading-strategy:-path | Loading Strategy: Path
Look for data objects based on their full path.
Data Source Index: Field of import that contains the path to look for.
| Loading Strategy: Path | [
0.03864787146449089,
-0.10404706001281738,
-0.20637202262878418,
0.3297533392906189,
-0.03495102748274803,
-0.46427077054977417,
0.21091705560684204,
0.26849889755249023,
0.29575902223587036,
0.15853072702884674,
-0.2995251715183258,
0.22006432712078094,
0.03181189298629761,
0.502635359764... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Resolver_Settings#loading-strategy:-attribute | Loading Strategy: Attribute
Look for data objects based on a specific attribute (e.g. Remote Id, EAN, ...).
Data Source Index: Field of import that contains the attribute value to look for.
Attribute Name: Attribute of data object to look for.
| Loading Strategy: Attribute | [
0.14827996492385864,
-0.21914087235927582,
-0.162735715508461,
0.33662912249565125,
-0.046705860644578934,
-0.4222789704799652,
0.2981113791465759,
0.1774708330631256,
0.30622443556785583,
0.11671289801597595,
-0.3948170244693756,
0.062071409076452255,
0.3783644437789917,
0.572096943855285... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Resolver_Settings#element-creation | Element Creation
Define location of new created data objects. | Element Creation | [
0.01751721277832985,
-0.17999045550823212,
-0.2218485325574875,
0.14350126683712006,
0.06955977529287338,
-0.45150357484817505,
0.2697848975658417,
-0.15894384682178497,
0.13939517736434937,
0.1814807802438736,
-0.12865829467773438,
0.1703237146139145,
-0.028977587819099426,
0.268058866262... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Resolver_Settings#location-strategy:-static-path | Location Strategy: Static Path
Always put new elements to a fixed specific folder.
Path: Folder where to put new elements to.
| Location Strategy: Static Path | [
0.08031675964593887,
-0.21629703044891357,
-0.25107860565185547,
-0.02471758984029293,
0.2062637209892273,
-0.4728078544139862,
0.25892993807792664,
0.16309022903442383,
-0.020588379353284836,
0.1482379138469696,
-0.09462960064411163,
0.18841923773288727,
-0.05469334125518799,
0.0110211400... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Resolver_Settings#location-strategy:-find-parent | Location Strategy: Find Parent
Find parent based on a strategy.
Find Strategy: Strategy find to parent
Loading Strategy Id: Load based on id.
Loading Strategy Path: Load based on full path.
Loading Strategy Attribute: Load based on data attribute with additional settings:
Class: Data object class to look for (can b... | Location Strategy: Find Parent | [
0.18020734190940857,
-0.17657719552516937,
-0.21273565292358398,
0.2745939791202545,
0.14580059051513672,
-0.2954709827899933,
0.10759824514389038,
0.30988407135009766,
0.03898303210735321,
0.035845864564180374,
-0.41078221797943115,
-0.010196231305599213,
0.09216905385255814,
0.3490124046... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Resolver_Settings#element-location-update | Element Location Update
Define location updates of data objects. The importer applies the location update strategy to all imported data objects -
no matter if they are updated or created.
For details on the strategies see Element Creation above. In addition, there is a No Change strategy that does not change
the locati... | Element Location Update | [
0.1685648262500763,
0.04587133228778839,
-0.19366692006587982,
-0.1820450723171234,
0.0519074983894825,
-0.3120567798614502,
0.4634701609611511,
-0.15892192721366882,
0.1865120828151703,
0.23635239899158478,
-0.258604496717453,
-0.021564703434705734,
0.2976614534854889,
0.20619024336338043... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Resolver_Settings#element-publishing | Element Publishing
Define a strategy to set the published state of data object during import.
Following strategies are available:
Always Publish: Always publishes new created or updated data objects.
Attribute Based: Set publish state based on a field of the import data.
No Change, Publish New: Do not change existi... | Element Publishing | [
0.03587251529097557,
-0.10014816373586655,
-0.15599927306175232,
-0.22453610599040985,
-0.0064374967478215694,
-0.5151487588882446,
0.3035309314727783,
0.09093214571475983,
0.18257588148117065,
0.35386374592781067,
-0.02732473984360695,
0.02442157454788685,
0.1780506670475006,
0.6782411336... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Processing_Settings#processing-settings | Processing Settings
There are a couple of processing settings that allow fine-tuning the import process. | Processing Settings | [
-0.33347874879837036,
-0.27132508158683777,
-0.28564977645874023,
-0.12677127122879028,
0.20752613246440887,
-0.1568278968334198,
0.11224845051765442,
0.2019680291414261,
0.07974810898303986,
0.4125872254371643,
-0.1503828763961792,
-0.09664234519004822,
0.14903901517391205,
0.181655913591... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Processing_Settings#execution-type | Execution Type
There are two types of processing - sequential and parallel - which are configured in the import configuration.
For details see Import Execution Details. | Execution Type | [
-0.18612460792064667,
-0.5798156261444092,
-0.23211443424224854,
-0.01453356072306633,
-0.041899170726537704,
-0.12855595350265503,
0.17082074284553528,
-0.07808444648981094,
0.20192794501781464,
0.31119778752326965,
-0.10458213835954666,
0.07414382696151733,
0.13575924932956696,
0.3002725... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Processing_Settings#archive-file-import | Archive File Import
Define if the importer should archive the imported file for later traceability. When activated,
the importer will create an application logger entry with the imported file as file object attached.
Be aware of needed disk space for archiving the data and that the importer creates a log entry of every... | Archive File Import | [
-0.26621758937835693,
0.11428648978471756,
-0.055492665618658066,
0.09872198104858398,
-0.08484858274459839,
-0.06020701304078102,
0.28973329067230225,
-0.03028898313641548,
0.2813948690891266,
-0.08018803596496582,
-0.1825041025876999,
0.019410116598010063,
-0.2935207188129425,
0.17758463... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Processing_Settings#delta-check | Delta Check
This option requires an id field in the import data.
With active delta check, the importer checks if imported data has changed since last import and imports
data only if updates are available. This might speed-up import because only updated data object will be
processed and saved.
The delta check is based... | Delta Check | [
-0.30402904748916626,
-0.3053799271583557,
-0.2652623653411865,
-0.19009500741958618,
-0.24443091452121735,
-0.21524274349212646,
0.0823674201965332,
0.3461752235889435,
0.3210962414741516,
0.18024082481861115,
-0.28762736916542053,
-0.05083277449011803,
0.16680455207824707,
0.444374024868... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Processing_Settings#cleanup | Cleanup
This option requires an id field in the import data.
The importer can cleanup in Pimcore existing data objects if they are not part of the current import data
anymore. There are two cleanup strategies available:
Unpublish: Unpublish data object to be cleaned up.
Delete: Delete data object to be cleaned up.
... | Cleanup | [
-0.22360830008983612,
-0.00715226074680686,
-0.09136419743299484,
-0.03358547016978264,
-0.07685714215040207,
-0.09120973944664001,
0.2219363898038864,
0.07980404794216156,
-0.09414563328027725,
0.2694540321826935,
-0.5369436144828796,
0.343622624874115,
0.30839380621910095,
0.373884767293... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Mapping_Configuration/Transformation_Pipeline#transformation-pipeline | Transformation Pipeline
The transformation pipeline takes the data read from source data based on the
Source Attributes setting and transforms it to a necessary target format
with one or multiple operators.
The transformation result panels shows information about the current resulting
type of the transformation and -... | Transformation Pipeline | [
-0.1200539693236351,
-0.046132929623126984,
-0.06642432510852814,
-0.0865706205368042,
0.024569854140281677,
-0.15526151657104492,
0.005697471555322409,
0.18492591381072998,
-0.40812498331069946,
0.09059114009141922,
-0.09226948022842407,
0.1926104724407196,
0.1264226734638214,
0.482046186... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Mapping_Configuration/Transformation_Pipeline#operators | Operators
Operators transform the input data to a desired output format. Every operator
expects certain input formats and delivers certain an output format.
There are two groups of operators
Standard Operators: Do some real processing and transformation with the input data.
Factory Operators: Prepare data for a certai... | Operators | [
0.25441786646842957,
-0.17006725072860718,
-0.08287558704614639,
-0.12755391001701355,
0.19121836125850677,
-0.13908161222934723,
0.519178569316864,
-0.0034327805042266846,
-0.1295941025018692,
0.21805575489997864,
0.13390769064426422,
0.17739436030387878,
-0.1354735791683197,
0.1969340294... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Mapping_Configuration/Transformation_Pipeline#list-of-available-operators | List of available Operators
As Array: Converts data to an array, if not already.
As Boolean: Converts data to a boolean.
As Date: Converts data to a date, format definition necessary.
As Gallery: Packs a single asset, or an asset array to a gallery.
As Image Advanced: Packs a single asset to an image advanced.
A... | List of available Operators | [
0.1413664072751999,
-0.2515602111816406,
-0.296642541885376,
-0.018832501024007797,
0.15666581690311432,
-0.11199970543384552,
0.3270660638809204,
0.07146438956260681,
0.1991199105978012,
0.10523107647895813,
-0.24214251339435577,
0.3961515724658966,
-0.035329047590494156,
0.34718164801597... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Mapping_Configuration/Transformation_Pipeline#what-operators-are-not-supposed-to-do: | What Operators are NOT supposed to do:
Complex statistical calculations: you possibly get an idea like that you can explode string to array and then calculate some average value, but it is wrong place to do it. Please keep the import peformance light.
Assign data to data object fields: One import is updating fields ... | What Operators are NOT supposed to do: | [
-0.08634522557258606,
0.031185319647192955,
-0.3021022081375122,
-0.047348763793706894,
0.3318246603012085,
-0.21079644560813904,
0.241094172000885,
-0.05410783365368843,
0.1077614426612854,
0.41099652647972107,
-0.18937024474143982,
0.06751249730587006,
0.12044472247362137,
0.273283004760... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Mapping_Configuration/Data_Target/Classification_Store_Batch_Details#classification-store-batch-details | Classification Store Batch Details
The Classification Store Batch data target allows assigning multiple classification store attributes
with one mapping. There are a couple of aspects important to know about. | Classification Store Batch Details | [
-0.25355058908462524,
-0.13521689176559448,
-0.12441454827785492,
-0.11201938986778259,
0.2647620439529419,
0.07259037345647812,
0.48644858598709106,
-0.05190408229827881,
-0.037460807710886,
0.05875132605433464,
-0.33517202734947205,
0.06447960436344147,
0.02794477716088295,
0.43057826161... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Mapping_Configuration/Data_Target/Classification_Store_Batch_Details#transformation-result-format | Transformation Result Format
The Classification Store Batch data target requires an array with <GROUP_ID>-<KEY_ID> as keys, and values
to be assigned as array values.
This format has to be prepared by the transformation pipeline in advance.
The simpliest way to archive that is using a JSON data source like
... | Transformation Result Format | [
-0.23502592742443085,
0.22722545266151428,
-0.07987870275974274,
-0.10716664046049118,
0.27239304780960083,
-0.1441337913274765,
0.31893986463546753,
0.29758429527282715,
-0.08721033483743668,
-0.05752040073275566,
-0.09702745825052261,
0.33844903111457825,
-0.05645161122083664,
0.52110356... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Mapping_Configuration/Data_Target/Classification_Store_Batch_Details#assign-complex-data-values | Assign Complex Data Values
Assigning more complex values (like date or quantityValue) to the classification store requires some more operators
to be added to the transformation pipeline, as the values need to be transformed to a date or quantityValue.
This is possible, with one restriction: One transformation pipeline ... | Assign Complex Data Values | [
-0.10743243992328644,
0.058812983334064484,
-0.09761358797550201,
-0.008044482208788395,
0.2963888347148895,
-0.18025656044483185,
0.4042811989784241,
0.18066197633743286,
0.12107803672552109,
0.13353657722473145,
-0.1637732833623886,
0.1332470178604126,
0.2469632476568222,
0.5526030063629... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Mapping_Configuration/Data_Target#data-target | Data Target
Data target definition assigns the result of the transformation pipeline to a data object field. The available data object
fields for assignment depend on the transformation result of the transformation pipeline.
Three different data target types are available: | Data Target | [
0.07981686294078827,
-0.10269016027450562,
-0.13827969133853912,
0.07198181003332138,
0.3395380675792694,
-0.17640149593353271,
0.13898633420467377,
-0.004673386923968792,
-0.2655383348464966,
0.017818186432123184,
0.020616615191102028,
0.3722916543483734,
-0.08832719177007675,
0.452581048... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Mapping_Configuration/Data_Target#direct | Direct
Assign data directly to fields defined directly in the data object class, object bricks or localized fields. The naming
schema for Object brick fields is <OBJECT_BRICK_FIELD>.<OBJECT_BRICK_TYPE>.<ATTRIBUTE>.
The availability of target fields depends on the settings and the result type of the... | Direct | [
0.2018194943666458,
-0.11649858951568604,
-0.04590079188346863,
0.005868856329470873,
0.41786903142929077,
-0.03497318923473358,
0.28967902064323425,
-0.060824912041425705,
0.30031678080558777,
0.2740311920642853,
-0.12569250166416168,
0.5288063883781433,
0.09808330237865448,
0.39154711365... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Mapping_Configuration/Data_Target#classification-store | Classification Store
Assign data to specific keys in a classification store.
The availability of target fields depends on the settings and the result type of the transformation pipeline.
| Classification Store | [
0.25699707865715027,
0.09101027250289917,
-0.12427166104316711,
0.08113307505846024,
0.31314757466316223,
-0.26450687646865845,
0.45800256729125977,
-0.23894885182380676,
-0.029512356966733932,
-0.02485494315624237,
-0.05859474092721939,
0.3389405906200409,
0.23714925348758698,
0.503954172... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Mapping_Configuration/Data_Target#classification-store-batch | Classification Store Batch
Assign multiple classification store attributes with one mapping. For this to work, the transformation result has to be
an array with <GROUP_ID>-<KEY_ID> as keys, and values as array values.
For more details and examples see Classification Store Batch Details. | Classification Store Batch | [
-0.13025832176208496,
0.022808058187365532,
-0.11111605912446976,
-0.11742017418146133,
0.322742223739624,
0.014788773842155933,
0.6017442345619202,
0.2249307930469513,
0.1933901011943817,
0.0890078917145729,
-0.23862364888191223,
0.3040352761745453,
0.18220677971839905,
0.2009034603834152... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Mapping_Configuration#mapping-configuration | Mapping Configuration
The mapping configuration defines what data fields from the import data should be imported where and how to
the Pimcore data object.
The mapping configuration consists of multiple mapping entries. Each mapping entry provides settings for:
Label: Defines a name for the mapping entry. The name i... | Mapping Configuration | [
-0.08794265240430832,
-0.36040642857551575,
-0.08982829004526138,
0.14091727137565613,
0.06809312105178833,
-0.14833955466747284,
0.0026994715444743633,
-0.033967938274145126,
-0.08032086491584778,
0.07481259852647781,
-0.37623000144958496,
0.30875158309936523,
0.3538811206817627,
0.431130... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Execution_Configuration#execution-configuration | Execution Configuration
Depending on the configuration there are different options to start an actual import.
When data source is push, the import process starts every time data is pushed to the corresponding
endpoint. There is no further configuration possible or needed.
For all the other data sources, Pimcore needs a... | Execution Configuration | [
-0.5101251602172852,
-0.3404647409915924,
-0.08721015602350235,
-0.040363818407058716,
-0.08977173268795013,
-0.48515838384628296,
0.14356529712677002,
-0.40465468168258667,
-0.17132212221622467,
0.17960238456726074,
-0.1667807549238205,
0.3660500645637512,
0.2435726821422577,
0.3866222500... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Execution_Configuration#manual-execution | Manual Execution
Clicking on the Manual Execution Start button in the configuration editor manually starts the import.
| Manual Execution | [
-0.24479369819164276,
-0.2625137269496918,
-0.06955282390117645,
-0.3075398802757263,
0.12593580782413483,
-0.02366614155471325,
0.20741255581378937,
-0.13732193410396576,
-0.05431889370083809,
0.32001328468322754,
0.06023922562599182,
0.21041661500930786,
0.007019649725407362,
0.356179058... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Execution_Configuration#cron-based-execution | Cron-based Execution
Besides the Manual Execution Start button there is also the possibility to configure a cron definition
based on which the import starts on a regular base, e.g. every 10 Minutes, once a day, etc.
See for example Crontab Guru for possibilities and a generator for generating
cron definitions.
Make s... | Cron-based Execution | [
-0.41711142659187317,
0.028675701469182968,
-0.09196820855140686,
-0.33787691593170166,
-0.25874194502830505,
-0.21520616114139557,
0.3065688908100128,
-0.13424129784107208,
0.29165560007095337,
0.17627879977226257,
0.2231408953666687,
0.30363911390304565,
-0.15237480401992798,
0.559975981... |
https://pimcore.com/docs/platform//Data_Importer/Configuration/Execution_Configuration#command-based-execution | Command-based Execution
It is also possible to imports with executing the datahub:data-importer:prepare-import command on the commandline.
For further details on import execution also see Import Execution Details. | Command-based Execution | [
-0.3727356493473053,
0.009809947572648525,
-0.18433283269405365,
-0.29750728607177734,
-0.06986106187105179,
-0.08622176945209503,
0.2569260597229004,
0.09616511315107346,
0.10768250375986099,
0.21988846361637115,
-0.28954988718032837,
0.12891913950443268,
-0.10739777237176895,
0.426580667... |
https://pimcore.com/docs/platform//Data_Importer/Configuration#configuration | Configuration
This section gives your details about all the configuration options of an import. Also, have a look
at Import Execution Details to understand how imports are
actually executed based on the import configuration. | Configuration | [
-0.08644283562898636,
-0.4381704330444336,
-0.21741802990436554,
-0.018831035122275352,
0.15531222522258759,
-0.23756557703018188,
0.33591777086257935,
-0.18053750693798065,
-0.11034645140171051,
0.3097684383392334,
-0.32617902755737305,
-0.038219209760427475,
0.3183239698410034,
0.0996665... |
https://pimcore.com/docs/platform//Data_Importer/Configuration#configuration-chapters | Configuration Chapters
Data Sources
File Formats
Import Preview
Resolver Settings
Processing Settings
Mapping Configuration
Execution Configuration
| Configuration Chapters | [
-0.32493093609809875,
-0.17523418366909027,
-0.1933232545852661,
-0.19406740367412567,
0.1525731086730957,
-0.008983726613223553,
0.15275229513645172,
0.4925452172756195,
-0.17099426686763763,
0.08124125748872757,
-0.19749291241168976,
0.2173539251089096,
0.23485881090164185,
0.56455433368... |
https://pimcore.com/docs/platform//Data_Importer/Import_Execution_Details#import-execution-details | Import Execution Details
Every import execution consists of two major parts
Preparation
Processing
| Import Execution Details | [
-0.03431188687682152,
-0.23005680739879608,
-0.3730713427066803,
-0.06532962620258331,
-0.05524647235870361,
-0.13421696424484253,
0.14251865446567535,
-0.0916217565536499,
0.028294941410422325,
0.21211037039756775,
-0.22314053773880005,
-0.1894853115081787,
0.3279280662536621,
0.219220057... |
https://pimcore.com/docs/platform//Data_Importer/Import_Execution_Details#1)-preparation | 1) Preparation
Import preparation loads import source from configured data source, interprets the file based on the file format settings
and splits import source into single data rows. These data rows are added to a queue to be processed during import processing.
Preparation starts when 'import is starte', that means .... | 1) Preparation | [
-0.21209679543972015,
-0.1709027886390686,
-0.21528975665569305,
-0.08201491832733154,
-0.36047127842903137,
-0.20873390138149261,
0.08839801698923111,
-0.07467104494571686,
-0.36208030581474304,
0.2319115847349167,
-0.1244167760014534,
0.12876614928245544,
0.32348737120628357,
0.160289824... |
https://pimcore.com/docs/platform//Data_Importer/Import_Execution_Details#2)-processing | 2) Processing
There are two types of processing - sequential and parallel - which are configured in the import configuration.
Sequential imports process the queue items one by one in the order they were added. This might be necessary when data elements
depend on each other, e.g. when building up hierarchies etc.
Parall... | 2) Processing | [
0.09260790795087814,
0.06734475493431091,
-0.16694368422031403,
-0.058868296444416046,
-0.40693777799606323,
-0.10386642068624496,
0.1481732577085495,
0.06940146535634995,
0.16050657629966736,
0.033433765172958374,
-0.29170143604278564,
-0.09643951058387756,
0.34354591369628906,
0.23954179... |
https://pimcore.com/docs/platform//Data_Importer/Import_Progress_and_Logging#import-progress-and-logging | Import Progress and Logging | Import Progress and Logging | [
-0.41945672035217285,
0.23496291041374207,
-0.29321762919425964,
-0.1477649062871933,
0.12708555161952972,
-0.1598203033208847,
0.28953713178634644,
0.11585347354412079,
0.11611824482679367,
0.0570392943918705,
-0.08097458630800247,
-0.17765383422374725,
-0.11647364497184753,
0.50866037607... |
https://pimcore.com/docs/platform//Data_Importer/Import_Progress_and_Logging#import-progress | Import Progress
The execution tab of the import configuration shows current status and progress information of an import. It shows,
if there are queue items currently processed, the progress of the current processing, and it also allows to cancel the
current import run (and remove all queue items).
| Import Progress | [
-0.3176790773868561,
-0.36024805903434753,
-0.3183407783508301,
-0.1637984812259674,
-0.13595670461654663,
-0.00478958897292614,
0.031872984021902084,
0.11765372008085251,
0.21085187792778015,
0.5257171988487244,
-0.30878302454948425,
-0.03618387132883072,
0.29419705271720886,
0.3740779161... |
https://pimcore.com/docs/platform//Data_Importer/Import_Progress_and_Logging#logging | Logging
The importer logs overview information into Pimcore application logger and detailed debugging information into standard
Pimcore/symfony loggers.
The Import Logs tab of the importer configuration shows a prefiltered list of the application logger containing only
entries belonging to the current import configu... | Logging | [
-0.26512449979782104,
-0.13095131516456604,
-0.07928899675607681,
0.3113565146923065,
-0.09927788376808167,
-0.19415491819381714,
0.26311400532722473,
-0.09783760458230972,
-0.026533063501119614,
-0.03641693666577339,
-0.42629194259643555,
0.14802837371826172,
-0.11720357090234756,
0.09559... |
https://pimcore.com/docs/platform//Data_Importer/Extending/Extend_Custom_Strategies#extend-via-custom-strategies | Extend via Custom Strategies
The bundle architecture easily allows extension and customization of many
parts of the importing process.
Following strategies and configuration options can be extended all following the same schema:
Data Sources
File Formats
Resolver Loading Strategies
Element Location Strategies
Element ... | Extend via Custom Strategies | [
-0.0804060772061348,
-0.3190644085407257,
-0.20237816870212555,
0.04707395285367966,
0.18883046507835388,
0.002296827035024762,
0.1811046004295349,
0.002488377271220088,
0.08112230896949768,
0.2250736802816391,
-0.49958622455596924,
0.15503525733947754,
0.004858008585870266,
0.706323266029... |
https://pimcore.com/docs/platform//Data_Importer/Extending/Extend_Custom_Strategies#extending-schema | Extending Schema
Extending one of the listed strategies and configuration options needs following steps. Also, have a look at the current
implementations to see how things are working. | Extending Schema | [
-0.1345680058002472,
-0.29404452443122864,
-0.20718729496002197,
-0.1126568540930748,
-0.033616047352552414,
-0.36490896344184875,
0.2525404989719391,
0.020376233384013176,
0.11898019164800644,
0.25910520553588867,
-0.09720657020807266,
0.24418750405311584,
0.055941786617040634,
0.40725368... |
https://pimcore.com/docs/platform//Data_Importer/Extending/Extend_Custom_Strategies#1)-php-implementation | 1) PHP Implementation
PHP implementations always need to implement an interface (e.g. DataLoaderInterface for data sources). Sometimes there
is also an abstract base class, that already implements certain functionality. Try to use them if possible
(e.g. AbstractInterpreter for FileFormats). It is of course also possibl... | 1) PHP Implementation | [
-0.09126747399568558,
-0.2229117602109909,
-0.16799555718898773,
0.19230850040912628,
-0.06902507692575455,
-0.37821683287620544,
0.40280312299728394,
0.1056230440735817,
-0.03021368384361267,
0.3648756742477417,
0.310175359249115,
-0.08786237239837646,
0.07002187520265579,
0.0935268476605... |
https://pimcore.com/docs/platform//Data_Importer/Extending/Extend_Custom_Strategies#2)-registering-implementation-as-symfony-service | 2) Registering implementation as symfony service
The php implementation needs to be registered as symfony service and tagged accordingly.
Tag name defines the extension point (e.g. pimcore.datahub.data_importer.loader for data sources) and
type defines the actual type of the extension. It must be unique and is also the... | 2) Registering implementation as symfony service | [
-0.19903527200222015,
0.08796148002147675,
-0.039676234126091,
-0.02743469551205635,
-0.05207405984401703,
-0.4773560166358948,
0.3434161841869354,
0.06156100705265999,
0.15085065364837646,
0.1586032211780548,
0.1219070553779602,
0.40159985423088074,
0.1144561842083931,
0.3126404881477356,... |
https://pimcore.com/docs/platform//Data_Importer/Extending/Extend_Custom_Strategies#3)-javascript-implementation | 3) JavaScript Implementation
Create a JavaScript class which meets following requirements:
Located in a certain namespace depending on the extension point
(e.g. pimcore.plugin.pimcoreDataImporterBundle.configuration.components.loader.* for data sources).
Extend the pimcore.plugin.pimcoreDataImporterBundle.configuratio... | 3) JavaScript Implementation | [
-0.13830426335334778,
-0.3130020499229431,
-0.08500124514102936,
0.004434164147824049,
0.0407402440905571,
-0.47338587045669556,
-0.05121881514787674,
0.03304477781057358,
-0.18515579402446747,
0.14379149675369263,
0.08462227880954742,
0.3961014747619629,
0.19251520931720734,
0.53402084112... |
https://pimcore.com/docs/platform//Data_Importer/Extending/Events#events | Events
Another option to customize import behavior is listening for events. The bundle fires following events during the
import process:
Pimcore\Bundle\DataImporterBundle\Event\DataObject\PreSaveEvent: Fired just before an imported data object will be saved
Pimcore\Bundle\DataImporterBundle\Event\DataObject\PostSave... | Events | [
-0.3293416500091553,
-0.07497741281986237,
-0.14976215362548828,
-0.001309916377067566,
0.10110576450824738,
-0.376901239156723,
0.06978720426559448,
-0.055125776678323746,
-0.24955856800079346,
0.30264174938201904,
-0.2799990475177765,
0.32307636737823486,
-0.008514988236129284,
0.1784599... |
https://pimcore.com/docs/platform//Data_Importer/Extending#extending | Extending
The bundle architecture provides several extension possibilities for developers to customize the behaviour.
Beside standard symfony extension and customization possibilities, there are two more specific options for extending:
Extend via Custom Strategies
Events
| Extending | [
-0.0990673378109932,
-0.20562642812728882,
-0.16581374406814575,
0.1543361097574234,
-0.14887474477291107,
-0.23902346193790436,
0.18758437037467957,
0.05676601454615593,
-0.023287387564778328,
0.3866812288761139,
0.023454364389181137,
0.2307201474905014,
-0.22511142492294312,
0.1472763270... |
https://pimcore.com/docs/platform//Data_Importer/Troubleshooting_FAQ#troubleshooting--faq | Troubleshooting / FAQ | Troubleshooting / FAQ | [
0.036740805953741074,
-0.6615586876869202,
-0.22974461317062378,
0.3527034521102905,
-0.029654376208782196,
0.1610637605190277,
0.12575161457061768,
-0.16842731833457947,
-0.11515219509601593,
0.22468800842761993,
0.12393032014369965,
-0.13841374218463898,
0.09678515791893005,
-0.008834809... |
https://pimcore.com/docs/platform//Data_Importer/Troubleshooting_FAQ#1)-status-in-the-execution-isn´t-progressing | 1) Status in the Execution isn´t progressing
Please be aware that you either need to activate the symfony messenger based or the command based processing for the queue.
See Import Execution Details for details.
| 1) Status in the Execution isn´t progressing | [
-0.13806715607643127,
-0.1790996640920639,
-0.20282381772994995,
-0.07369963824748993,
-0.03934241831302643,
-0.26357847452163696,
0.3089359998703003,
0.032221823930740356,
0.09960656613111496,
0.22472840547561646,
0.03823035582900047,
-0.02589312009513378,
0.013696635141968727,
0.11427186... |
https://pimcore.com/docs/platform//Data_Importer/Troubleshooting_FAQ#2)-"error:-the-command-is-already-running."-while-running-the-process-queue-command | 2) "ERROR: The command is already running." while running the process queue command
Sometimes it can happen that one of the worker processes terminates unexpectedly. If you try to run the process queue command again,
you may get a "The command is already running." error message.
If that is the case,... | 2) "ERROR: The command is already running." while running the process queue command | [
-0.14798249304294586,
-0.127586230635643,
-0.15748512744903564,
-0.06448232382535934,
-0.10135404765605927,
-0.2187967300415039,
0.38961392641067505,
0.0021354369819164276,
0.044486820697784424,
0.2975963354110718,
0.09230893105268478,
0.0827014371752739,
-0.005993415601551533,
0.250988304... |
https://pimcore.com/docs/platform//Data_Importer#data_importer | Data_Importer
| Data_Importer | [
-0.4225550889968872,
0.09540855884552002,
-0.2734684348106384,
0.32118192315101624,
0.269009530544281,
-0.4048835039138794,
0.5063290596008301,
-0.000011214642654522322,
0.1717323660850525,
0.32474982738494873,
-0.1700919270515442,
0.03693433478474617,
-0.20452876389026642,
0.5193011760711... |
https://pimcore.com/docs/platform//Data_Importer#title:-data-importer | title: Data Importer | title: Data Importer | [
-0.12710948288440704,
0.3523194491863251,
-0.3356821835041046,
0.173544779419899,
0.16643624007701874,
-0.14673762023448944,
0.5038531422615051,
0.014403770677745342,
0.19740872085094452,
0.36469054222106934,
-0.1275109201669693,
0.03794975206255913,
-0.11609160155057907,
0.421319454908370... |
https://pimcore.com/docs/platform//Data_Importer#pimcore-data-importer | Pimcore Data Importer
This extension adds a comprehensive import functionality to Pimcore Datahub. It allows importing data from external
sources and adjusting it to Pimcore Data Objects based on a configured mapping without writing any code. | Pimcore Data Importer | [
-0.37474754452705383,
-0.08466199785470963,
-0.16620908677577972,
-0.0840390995144844,
-0.20292502641677856,
-0.18304051458835602,
-0.05146375671029091,
0.06689586490392685,
-0.015616482123732567,
0.19735324382781982,
-0.496031254529953,
0.35959067940711975,
-0.050607964396476746,
0.454350... |
https://pimcore.com/docs/platform//Data_Importer#features-in-a-nutshell | Features in a Nutshell
Multiple imports configuration directly in Datahub.
Data import from various data sources.
Supported File Formats: csv, xlsx, json, xml.
Strategies configuration for:
loading existing elements for updating data.
defining location for newly imported data.
publishing data.
cleanup of existing dat... | Features in a Nutshell | [
-0.22129853069782257,
-0.2854335904121399,
-0.268791526556015,
-0.11187516152858734,
-0.26091495156288147,
-0.2173309028148651,
0.10115774720907211,
0.20110958814620972,
-0.11740508675575256,
0.08575543016195297,
-0.38326555490493774,
0.16236886382102966,
0.05220429599285126,
0.69949191808... |
https://pimcore.com/docs/platform//Data_Importer#documentation-overview | Documentation Overview
Installation
Configuration
Import Execution Details
Import Progress and Logging
Extending
Troubleshooting/FAQ
| Documentation Overview | [
-0.13050095736980438,
-0.33996647596359253,
-0.23316745460033417,
-0.03097776137292385,
-0.07615767419338226,
0.050337906926870346,
0.1258305013179779,
-0.21064524352550507,
0.004310940857976675,
0.09526748955249786,
-0.01164546050131321,
0.06639984250068665,
0.17041048407554626,
0.2893598... |
https://pimcore.com/docs/platform//Data_Importer#further-information | Further Information
On other Pimcore Datahub adapters and export solutions:
Datahub (GraphQL API)
Datahub Simple Rest API
Datahub File Export
Datahub Productsup
Datahub CI Hub
| Further Information | [
-0.4473881125450134,
-0.1215147078037262,
-0.2617936134338379,
-0.14389358460903168,
-0.14080214500427246,
-0.23933781683444977,
0.46107912063598633,
0.22678741812705994,
0.1024336963891983,
0.253315806388855,
-0.3978445529937744,
0.3699144721031189,
0.1576916128396988,
1.0087016820907593,... |
https://pimcore.com/docs/platform//Datahub_File_Export/Installation/Upgrade#upgrade-information | Upgrade Information
Following steps are necessary during updating to newer versions. | Upgrade Information | [
-0.22016730904579163,
-0.21716107428073883,
-0.18844935297966003,
0.06598692387342453,
0.05852506309747696,
-0.04944508150219917,
0.04977540299296379,
0.07004286348819733,
-0.2696684002876282,
-0.04550585895776749,
-0.05604716017842293,
0.030289839953184128,
0.19013381004333496,
0.06546622... |
https://pimcore.com/docs/platform//Datahub_File_Export/Installation/Upgrade#upgrade-to-2.0.0 | Upgrade to 2.0.0
Make sure all running exports are done prior upgrading to version 2.0.0.
| Upgrade to 2.0.0 | [
-0.33890148997306824,
-0.15964637696743011,
-0.2327215075492859,
-0.0484854020178318,
0.19384616613388062,
-0.15836764872074127,
0.2535274624824524,
0.4611225724220276,
-0.025111569091677666,
0.3439916670322418,
0.07031708210706711,
0.27475637197494507,
0.019014084711670876,
0.273105710744... |
https://pimcore.com/docs/platform//Datahub_File_Export/Installation/Upgrade#upgrade-to-1.1.0 | Upgrade to 1.1.0
Execute all migrations of the bundle.
| Upgrade to 1.1.0 | [
-0.3606078028678894,
-0.28820350766181946,
-0.21636199951171875,
-0.03308386728167534,
0.1089639887213707,
0.05171853303909302,
0.14973768591880798,
0.3632907569408417,
-0.14371924102306366,
0.26242485642433167,
-0.025727316737174988,
0.32761669158935547,
-0.200162872672081,
0.150005802512... |
https://pimcore.com/docs/platform//Datahub_File_Export/Installation/Upgrade#upgrade-to-pimcore-x | Upgrade to Pimcore X
Update to latest (allowed) bundle version in Pimcore 6.9 and execute all migrations.
Then update to Pimcore X.
| Upgrade to Pimcore X | [
-0.5807572603225708,
-0.20940947532653809,
-0.1540290266275406,
0.007363408338278532,
0.04493528977036476,
-0.16714733839035034,
0.046648457646369934,
0.2623489201068878,
-0.2353164553642273,
0.23198316991329193,
-0.19107705354690552,
0.5369307398796082,
-0.01311113778501749,
0.18771138787... |
https://pimcore.com/docs/platform//Datahub_File_Export/Installation#installation | Installation | Installation | [
-0.06728437542915344,
-0.4834894835948944,
-0.3417288661003113,
0.20734061300754547,
0.06259846687316895,
0.09173910319805145,
-0.07573223114013672,
-0.07214274257421494,
0.15155638754367828,
0.1816904991865158,
-0.07461769878864288,
0.14365136623382568,
0.041423697024583817,
0.05546558648... |
https://pimcore.com/docs/platform//Datahub_File_Export/Installation#required-bundles | Required Bundles
This bundle depends on Pimcore Datahub bundle. This needs to be installed first. | Required Bundles | [
-0.3271258473396301,
-0.21303868293762207,
-0.19423209130764008,
-0.01872885785996914,
-0.07750827074050903,
-0.005332225002348423,
0.2224234789609909,
0.13292168080806732,
-0.18985703587532043,
0.07080167531967163,
-0.11254754662513733,
0.26534873247146606,
0.07108276337385178,
0.33809244... |
https://pimcore.com/docs/platform//Datahub_File_Export/Installation#installation-process | Installation Process | Installation Process | [
0.08020234853029251,
-0.4312822222709656,
-0.29270926117897034,
0.10546649992465973,
-0.1146225556731224,
0.020290104672312737,
-0.026727845892310143,
-0.1865369826555252,
0.10249292105436325,
0.14968742430210114,
-0.0016273048240691423,
0.1121966689825058,
0.1848244071006775,
-0.010504826... |
https://pimcore.com/docs/platform//Datahub_File_Export/Installation#for-pimcore->=-10.5 | For Pimcore >= 10.5
To install the File Export bundle for Pimcore 10.5 or higher, follow the three steps below:
Install the required dependencies:
composer require pimcore/data-hub-file-export
Make sure the bundle is enabled in the config/bundles.php file. The following lines should be added:
use Pimcore\Bundle... | For Pimcore >= 10.5 | [
-0.44369304180145264,
-0.06766670197248459,
-0.15079814195632935,
0.11299755424261093,
-0.02856118604540825,
0.00047492620069533587,
0.16594663262367249,
0.2542429566383362,
-0.31954631209373474,
0.2791726589202881,
-0.2091568112373352,
0.4623602628707886,
0.13484695553779602,
0.2808881103... |
https://pimcore.com/docs/platform//Datahub_File_Export/Installation#for-older-versions | For Older Versions
To install the File Export bundle for older versions of Pimcore, please run the following commands instead:
composer require pimcore/data-hub-file-export
bin/console pimcore:bundle:enable PimcoreDataHubFileExportBundle
bin/console pimcore:bundle:install PimcoreDataHubFileExportBundle
Please make su... | For Older Versions | [
-0.4840466380119324,
-0.032710082828998566,
-0.16554051637649536,
-0.03306727111339569,
-0.06956280767917633,
-0.05741095915436745,
0.3090205192565918,
0.1725400984287262,
-0.1890822947025299,
0.30420997738838196,
-0.23047089576721191,
0.39689603447914124,
0.046437643468379974,
0.316091567... |
https://pimcore.com/docs/platform//Datahub_File_Export/Basic_Configuration#basics | Basics | Basics | [
0.007046605460345745,
-0.5804570913314819,
-0.2560560703277588,
0.14939501881599426,
0.1518014371395111,
-0.18608762323856354,
0.06521893292665482,
0.07734181731939316,
-0.37329205870628357,
0.2516036331653595,
0.2457820028066635,
-0.01944676972925663,
0.29610195755958557,
0.22608016431331... |
https://pimcore.com/docs/platform//Datahub_File_Export/Basic_Configuration#general-settings | General settings
Active: Enable/Disable the configuration.
Description: Provide a description for the configuration.
| General settings | [
-0.4448903203010559,
-0.8079609274864197,
-0.1899394690990448,
-0.16266456246376038,
0.08455976098775864,
-0.0815856084227562,
0.15403763949871063,
-0.07818712294101715,
-0.09564527124166489,
0.2682456374168396,
0.016848942264914513,
-0.08671203255653381,
-0.1010870635509491,
0.09373375773... |
https://pimcore.com/docs/platform//Datahub_File_Export/Basic_Configuration#schema-definition | Schema definition
Configure the exported data with drag & drop as it you do it in the regular grid column definition in Pimcore.
Optionally define image / video thumbnails if you are going to export assets - if no thumbnail is selected, the original asset path is used.
Make sure your column names are unique and ... | Schema definition | [
-0.221286341547966,
0.23298053443431854,
-0.16835010051727295,
0.06060468778014183,
0.18108172714710236,
-0.05777984857559204,
0.21559230983257294,
0.302316814661026,
0.007275896146893501,
0.21707171201705933,
-0.2784872055053711,
0.5036147236824036,
0.23677273094654083,
0.49238321185112,
... |
https://pimcore.com/docs/platform//Datahub_File_Export/Basic_Configuration#workspace-definition | Workspace definition
Workspaces - restrict the export to specific folders.
Custom export service - define a custom export service which should execute the export - default is pimcore.datahub.fileExport.exporter.file.
If you define your own service, please make sure it is public, shared and tagged as in the sample ... | Workspace definition | [
-0.17272816598415375,
0.16382534801959991,
-0.21540047228336334,
-0.15416817367076874,
-0.3057127296924591,
-0.2757473587989807,
0.3100549578666687,
0.4820950925350189,
0.08033103495836258,
0.3041076958179474,
-0.41431787610054016,
0.22899483144283295,
0.06307315826416016,
0.38061749935150... |
https://pimcore.com/docs/platform//Datahub_File_Export/Basic_Configuration#delivery-destination | Delivery destination
File Type: The export format to use.
Filename: The name of the target file.
Delivery Type: Where the data should be delivered.
File name conflict:
Overwrite: Always creates a new file with just the changed data. Be careful when using Delivery directly on save
with this option as the data w... | Delivery destination | [
0.1164998933672905,
-0.13572517037391663,
-0.12202762812376022,
0.023203779011964798,
-0.09676144272089005,
-0.27857518196105957,
-0.08273548632860184,
0.0868210420012474,
-0.23071202635765076,
0.19281598925590515,
-0.037732332944869995,
0.0616915337741375,
0.06723400950431824,
0.592004120... |
https://pimcore.com/docs/platform//Datahub_File_Export/Basic_Configuration#delivery-trigger-and-execution | Delivery Trigger and Execution
The trigger for delivery defines, when the data should be exported:
Disabled: The export ist just done by the export command in the ProcessManger (more details later on). Each export is a full export.
Deliver directly on save: When the data object is saved, the data of this particula... | Delivery Trigger and Execution | [
-0.26873278617858887,
-0.2038652002811432,
-0.14556781947612762,
0.1328354775905609,
-0.12470663338899612,
-0.4705859422683716,
0.1822228729724884,
-0.15220336616039276,
0.025952504947781563,
0.2630174160003662,
0.04822074994444847,
0.1994873583316803,
0.08953969925642014,
0.29126417636871... |
https://pimcore.com/docs/platform//Datahub_File_Export/Export_Setup#export-setup | Export setup
The bundle allows manual and automatic execution of exports. The export can be setup in different ways. For all ways,
there are two export modes:
Full Export: Does a full export regardless of items that might be in the queue.
Only Queue Items: Only exports items that are in the queue (populated via the De... | Export setup | [
-0.2791728377342224,
-0.39714959263801575,
-0.13415716588497162,
-0.0435173436999321,
-0.0717715322971344,
0.0500047393143177,
0.3777276277542114,
-0.02065032720565796,
-0.15326029062271118,
0.189501091837883,
-0.13663513958454132,
0.21225780248641968,
-0.07343680411577225,
0.4548155963420... |
https://pimcore.com/docs/platform//Datahub_File_Export/Export_Setup#manual-execution-directly-in-configuration | Manual execution directly in Configuration
The export can be executed directly by the user in the configuration dialog. For the two export modes, two different buttons
exist. When clicking the corresponding button, the export is executed asynchronously via
Symfony messenger queue.
The progress of the export is also... | Manual execution directly in Configuration | [
-0.35230720043182373,
-0.06315844506025314,
-0.04127725213766098,
-0.0768224447965622,
-0.34757670760154724,
-0.09637850522994995,
0.3904837369918823,
-0.02661614865064621,
-0.26982858777046204,
0.3654625713825226,
-0.19890181720256805,
0.26807069778442383,
0.12183045595884323,
0.280548512... |
https://pimcore.com/docs/platform//Datahub_File_Export/Export_Setup#automatic-execution-via-cron-definition | Automatic execution via Cron Definition
In addition to the manual execution, a recurring export based on cron definitions can be configured directly in the configuration.
Thus, it is possible to easily configure exports e.g. every 10 Minutes, once a day, etc.
See for example Crontab Guru for possibilities and a gener... | Automatic execution via Cron Definition | [
-0.2761070728302002,
-0.030037831515073776,
-0.0490383543074131,
-0.10939010232686996,
-0.40492409467697144,
-0.31540316343307495,
0.40746358036994934,
-0.03910299390554428,
0.0008414580370299518,
0.3527483344078064,
0.11953514814376831,
0.2944898307323456,
-0.1882185935974121,
0.385195821... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.