url stringlengths 50 196 | text stringlengths 3 17.2k | heading stringlengths 2 103 | embeddings list |
|---|---|---|---|
https://pimcore.com/docs/platform//Datahub/GraphQL/Query/Query_Samples/Sample_Parent_Children_Siblings#get-objects-parentchildrensiblings | Get objects Parent/Children/Siblings
For example, to get berlina object's (id:261) parent, children and siblings
| Get objects Parent/Children/Siblings | [
-0.164576455950737,
-0.12458928674459457,
-0.26490792632102966,
0.6726257801055908,
0.12105990201234818,
-0.023020420223474503,
0.13602383434772491,
0.5043283700942993,
0.09171178191900253,
0.05546226724982262,
-0.41886574029922485,
-0.09755176305770874,
0.08020953834056854,
-0.06481357663... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Query/Query_Samples/Sample_Parent_Children_Siblings#request | Request
Note that for children and _siblings you can use the objectTypes argument to filter for specific types.
Any combination of variant, object, folder is possible as a value for the objectTypes argument (default: ["object", "folder"]).
{
getCar(id: 261) {
id
name
parent {
..... | Request | [
-0.1647019386291504,
-0.31030717492103577,
-0.23409292101860046,
0.5071359872817993,
0.09407172352075577,
-0.1812811940908432,
0.08953307569026947,
0.526416540145874,
-0.08589877188205719,
-0.08053702861070633,
-0.2500837445259094,
0.2730937600135803,
-0.147947296500206,
0.3026238083839416... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Query/Query_Samples/Sample_Parent_Children_Siblings#response | Response
{
"data": {
"getCar": {
"id": "261",
"name": "1900",
"parent": {
"id": "260",
"name": "1900"
},
"children": [
{
"id&... | Response | [
-0.12168864160776138,
-0.19528281688690186,
-0.4041162431240082,
0.400481253862381,
0.15636968612670898,
0.006357635371387005,
0.08599702268838882,
0.37292221188545227,
-0.12981835007667542,
0.09729025512933731,
0.09663024544715881,
0.33037301898002625,
0.11556986719369888,
0.1963422000408... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Query/Query_Samples/Sample_Get_Linked_Data#get-linked-data | Get Linked Data | Get Linked Data | [
-0.10736570507287979,
-0.1541416347026825,
-0.27617207169532776,
0.5318459272384644,
-0.05223904922604561,
-0.1931147426366806,
0.1906571239233017,
0.3348652124404907,
0.06460306793451309,
0.298431932926178,
-0.24620257318019867,
0.0895136296749115,
0.1508299857378006,
-0.01259292662143707... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Query/Query_Samples/Sample_Get_Linked_Data#get-car-with-referenced-manufacturer-and-manufacturer-logo-image-thumbnail | Get Car With Referenced Manufacturer and Manufacturer Logo Image Thumbnail | Get Car With Referenced Manufacturer and Manufacturer Logo Image Thumbnail | [
-0.16311341524124146,
-0.22225438058376312,
-0.2521759271621704,
0.449456125497818,
-0.08865837752819061,
-0.1332443356513977,
0.3490481376647949,
0.2964807152748108,
-0.24244341254234314,
0.23351851105690002,
0.05693640932440758,
0.2191421240568161,
0.14233946800231934,
0.1076481342315673... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Query/Query_Samples/Sample_Get_Linked_Data#configuration | Configuration
Deeplink: https://demo.pimcore.fun/admin/login/deeplink?object_277_object
Note that you have to adapt your schema definition as depicted below. The thumbnail
will generated using the Thumbnail Operator.
| Configuration | [
-0.23576074838638306,
-0.23042359948158264,
-0.10658669471740723,
0.03755243122577667,
-0.061309441924095154,
-0.3324098289012909,
0.14213287830352783,
0.0005375464679673314,
-0.145549014210701,
0.21458058059215546,
-0.2498854249715805,
0.3970678746700287,
0.0696190893650055,
0.23883605003... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Query/Query_Samples/Sample_Get_Linked_Data#request | Request
{
getCar(id:277, defaultLanguage:"en") {
name
frenchName: name(language: "fr")
productionYear
cylinders
manufacturer {
...on object_Manufacturer {
id
name
logo {
fullpath
}
customThumbnail
}
}
}... | Request | [
0.05022251978516579,
-0.18874244391918182,
-0.20237955451011658,
0.5342446565628052,
-0.13658744096755981,
-0.2414044886827469,
0.012921534478664398,
0.18112623691558838,
-0.12919378280639648,
0.2266298085451126,
0.3720529079437256,
0.11899224668741226,
0.2689645290374756,
0.09865767508745... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Query/Query_Samples/Sample_Get_Linked_Data#response | Response
{
"data": {
"getCar": {
"name": "Montreal",
"frenchName": null,
"productionYear": 1970,
"cylinders": 8,
"manufacturer": {
"id": "28",
"name": "A... | Response | [
0.030556607991456985,
-0.1323365569114685,
-0.34746360778808594,
0.37342965602874756,
-0.08154115080833435,
-0.08991633355617523,
-0.11393196880817413,
0.4838145673274994,
-0.09963642060756683,
0.10050012171268463,
0.2326033115386963,
0.1948082447052002,
0.16658847033977509,
0.187356010079... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Query/Query_Samples/Sample_Translate_Values#translate-values | Translate Values
The following example translates the AccessoryPart condition value.
Deeplink: http://pimcore-demo-basic.pim.zone/admin/login/deeplink?object_373_object
Operator Config:
Website Translation Grid:
The idea in the following example is to use the website translation feature to convert
the value of the se... | Translate Values | [
-0.3520979583263397,
-0.037505440413951874,
-0.14290142059326172,
0.16537407040596008,
-0.07639239728450775,
-0.4336349666118622,
-0.12432336062192917,
0.16318368911743164,
-0.259840190410614,
0.25427526235580444,
-0.19836072623729706,
0.497274249792099,
0.3118499517440796,
0.1740434765815... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Query/Query_Samples/Sample_Translate_Values#request | Request
{
getAccessoryPart(id: 373, defaultLanguage: "de") {
# real condition
condition
# processed by the website translator with the prefix as defined in the export
# config and the language as specified above
translatedCondition
}
}
| Request | [
0.0280411746352911,
-0.3807360529899597,
-0.26904362440109253,
0.17381520569324493,
0.132023423910141,
-0.40443283319473267,
-0.17209433019161224,
0.34578436613082886,
0.04141314700245857,
0.366580069065094,
0.12855511903762817,
0.07839609682559967,
0.47964316606521606,
0.05541105568408966... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Query/Query_Samples/Sample_Translate_Values#response | Response
{
"data": {
"getAccessoryPart": {
"condition": "broken",
"translatedCondition": "nicht mehr zu gebrauchen :-)"
}
}
}
| Response | [
-0.06051596254110336,
-0.17057006061077118,
-0.3416650891304016,
0.16042058169841766,
0.13677573204040527,
-0.37995445728302,
-0.09017843008041382,
0.3612326681613922,
0.1050087958574295,
0.3344862461090088,
0.12733091413974762,
-0.06648826599121094,
0.1662897765636444,
0.04440151900053024... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Query/Add_Custom_Query_Datatype#add-a-custom-query-datatype | Add a Custom Query Datatype
For adding a new query data type two steps are necessary:
add a type definition
provide a resolver implementation (optional)
To add a type definition, add a section similar to this one to your services.yml file.
pimcore.datahub.graphql.dataobjectquerytypegenerator_datatype_mycustomdata... | Add a Custom Query Datatype | [
-0.21494267880916595,
-0.07678220421075821,
-0.05555066838860512,
-0.04027499631047249,
-0.25783491134643555,
-0.2992401123046875,
-0.06210619583725929,
0.0966806709766388,
0.1966591775417328,
0.27495476603507996,
-0.19836290180683136,
0.533257007598877,
0.051207706332206726,
0.44467926025... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Query/Add_Custom_Query_Operator#add-a-custom-query-operator | Add a Custom Query Operator
For adding a new query operator two steps are necessary:
add a type definition
add the operator implementation
| Add a Custom Query Operator | [
0.05654361844062805,
-0.10870952159166336,
-0.2260325402021408,
-0.15835489332675934,
-0.2527989447116852,
-0.23521488904953003,
0.04624976962804794,
0.10935327410697937,
-0.06085065379738808,
0.33244675397872925,
-0.2422405332326889,
0.22508075833320618,
-0.209769606590271,
0.117908887565... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Query/Add_Custom_Query_Operator#type-definition | Type Definition
Add a section similar to this one to your services.yml file.
pimcore.datahub.graphql.querytypegenerator_operator_mycustomoperator:
class: Pimcore\Bundle\DataHubBundle\GraphQL\QueryOperatorConfigGenerator\MyCustomOperator
tags:
- { name: pimcore.datahub.graphql.dataobjectq... | Type Definition | [
-0.35535043478012085,
-0.07554415613412857,
-0.07326573878526688,
-0.11918526142835617,
-0.024017727002501488,
-0.40565454959869385,
0.04918051138520241,
0.2025505006313324,
0.048769574612379074,
0.2978878319263458,
-0.19204872846603394,
0.41081953048706055,
-0.08982255309820175,
0.3553046... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Query/Add_Custom_Query_Operator#operator-implementation | Operator Implementation
You have to provide both JavaScript code dealing with the UI configuration aspects specific to your operator
and the server-side PHP implementation doing the actual calculations.
A JS sample can be found here.
Note that the namespace would be pimcore.plugin.datahub.operator.mycustomoperator.
Ma... | Operator Implementation | [
-0.0998954176902771,
0.17153725028038025,
-0.05215075984597206,
0.007075274363160133,
-0.3091018497943878,
-0.6341555118560791,
0.3349798321723938,
-0.08860903233289719,
-0.12889061868190765,
0.5046208500862122,
-0.14513280987739563,
0.5295401215553284,
-0.02824368141591549,
0.367749422788... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Query/Add_Custom_Query#add-a-custom-query | Add a Custom Query
You can extend the query schema and add your custom query in the following way.
See Events and Event Listeners
if you need more information on Pimcore's event mechanism.
\Pimcore::getEventDispatcher()->addListener(\Pimcore\Bundle\DataHubBundle\Event\GraphQL\QueryEvents::PRE_BUILD,
function (\P... | Add a Custom Query | [
-0.5214472413063049,
-0.08899138867855072,
-0.17860351502895355,
0.2146967053413391,
-0.3071851432323456,
-0.4746091365814209,
-0.012432124465703964,
0.16956473886966705,
0.01886325515806675,
0.1937025636434555,
-0.29090192914009094,
0.6551320552825928,
-0.032582998275756836,
0.44397336244... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Document_Mutations#document-mutations | Document Mutations | Document Mutations | [
-0.016694417223334312,
-0.04524531587958336,
-0.103736013174057,
0.30302733182907104,
-0.03754029422998428,
-0.014419930055737495,
0.24331341683864594,
0.2390151470899582,
-0.3210400938987732,
0.02702055498957634,
-0.04652327671647072,
0.37936821579933167,
0.09182524681091309,
-0.432033240... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Document_Mutations#supported-document-types | Supported Document Types
Email
Link
Page
...
| Supported Document Types | [
-0.13721072673797607,
-0.4434571862220764,
-0.1494317352771759,
0.10035958886146545,
-0.11131826043128967,
0.10043235868215561,
0.3314995765686035,
0.1593676656484604,
0.23828913271427155,
0.10007306188344955,
-0.02639937773346901,
-0.03912220522761345,
-0.27705323696136475,
0.378920137882... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Document_Mutations#supported-page-element-types | Supported Page Element Types
Areablock
Block
Embed
Image (for now only target asset + alt text, no hotspots or markers)
Input
Multiselect
Scheduled Block
Select
Wysiwyg
| Supported Page Element Types | [
-0.34607845544815063,
-0.6505326628684998,
-0.1083579733967781,
-0.17299559712409973,
0.004578204359859228,
-0.21551184356212616,
0.44632038474082947,
0.10576757788658142,
0.39500537514686584,
0.18014487624168396,
0.18610547482967377,
0.3870397210121155,
-0.16344955563545227,
0.44270521402... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Document_Mutations#mutation-modes | Mutation Modes
There a two modes for document mutations. The Free-form API allows updating single editable content but
requires lots of Pimcore insight knowledge. The Tree API provides a more intuitive nested approach for
creating and updating documents. | Mutation Modes | [
-0.165677011013031,
-0.03826318308711052,
-0.15378302335739136,
-0.1005096286535263,
-0.1814204305410385,
-0.34030309319496155,
-0.14253275096416473,
0.11108652502298355,
-0.5269249081611633,
0.1628440022468567,
-0.13171786069869995,
0.5260124802589417,
0.1473010629415512,
0.08297735452651... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Document_Mutations#free-form-api | Free-form API
Important Note: To be able to fully exploit this feature you have to understand Pimcore's editable naming strategy
Update or add single or multiple editables by defining their exact name and their content. | Free-form API | [
-0.19742675125598907,
-0.05763304606080055,
-0.285758376121521,
-0.09798625111579895,
0.03705034777522087,
-0.21266664564609528,
0.1426827609539032,
0.09827352315187454,
-0.2892259657382965,
0.40355148911476135,
-0.30971890687942505,
0.6562830209732056,
-0.10423547774553299,
0.386755973100... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Document_Mutations#sample-(update-existing-document) | Sample (Update Existing Document)
mutation {
updateDocumentPage(
id: 99
input: {
editableUpdateStrategy: replaceAll # defaults to update
editables: {
input: [
{ _editableName: "content:2.headline", text: "HEYYOU 3" }
{ _ed... | Sample (Update Existing Document) | [
0.05681794136762619,
-0.06662783771753311,
-0.048064421862363815,
-0.40194910764694214,
0.2524632215499878,
-0.042327240109443665,
0.22989752888679504,
0.42397427558898926,
-0.0423395112156868,
-0.08397543430328369,
-0.10688605159521103,
0.6977174878120422,
0.04454094544053078,
-0.05881623... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Document_Mutations#additional-examples | Additional Examples
See following list for more examples with the free-form API approach:
Create document with areablocks and nested block with images
Update email document
Create a new link document
| Additional Examples | [
-0.03358009085059166,
-0.07800476253032684,
-0.2317599356174469,
0.04723481461405754,
-0.2659626305103302,
-0.11205180734395981,
0.3669266402721405,
0.14674530923366547,
0.33874261379241943,
0.17124159634113312,
0.29778584837913513,
-0.0058332947082817554,
0.026647144928574562,
0.315711438... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Document_Mutations#tree-api | Tree API
If you are not familiar with Pimcore's editable naming strategy
you can also use the nested approach. | Tree API | [
-0.16486723721027374,
-0.14160525798797607,
-0.3558438718318939,
0.10522717982530594,
0.09066323935985565,
-0.29479607939720154,
0.08066556602716446,
0.11749138683080673,
-0.3013714849948883,
0.40949055552482605,
-0.272438645362854,
0.4267406165599823,
-0.07828398793935776,
0.1465877890586... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Document_Mutations#sample-(update-a-page-with-an-areablock-using-the-nested-approach) | Sample (Update a Page With an Areablock Using the Nested Approach)
mutation {
updateDocumentPage(
id: 99
input: {
editables: {
areablock: [
{
_editableName: "content"
items: [
{
... | Sample (Update a Page With an Areablock Using the Nested Approach) | [
-0.08342956006526947,
-0.08505675941705704,
-0.12731324136257172,
-0.2978692352771759,
0.10729306936264038,
-0.15941449999809265,
0.4143376052379608,
0.38057941198349,
0.20702119171619415,
0.0946192592382431,
-0.017309395596385002,
0.5575945973396301,
0.10875365138053894,
0.218210011720657... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Document_Mutations#additional-examples | Additional Examples
See following list for more examples with the tree API approach:
Create document with areablocks and nested block with images
| Additional Examples | [
-0.1680189073085785,
-0.0537869893014431,
-0.32825377583503723,
0.20913951098918915,
-0.20613373816013336,
-0.15647025406360626,
0.2318614274263382,
0.15742681920528412,
0.1949118971824646,
0.2122693657875061,
0.1982157677412033,
0.19196660816669464,
0.06774420291185379,
0.1851775497198104... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Asset_Mutations#asset-mutations | Asset Mutations | Asset Mutations | [
-0.1286129355430603,
-0.06294048577547073,
-0.23416104912757874,
0.33320748805999756,
0.28905215859413147,
-0.1737455427646637,
0.4365455210208893,
0.2705294191837311,
-0.16148720681667328,
0.04571322724223137,
-0.1796717494726181,
0.5111352205276489,
0.08119658380746841,
-0.33841234445571... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Asset_Mutations#create-asset | Create Asset
This will create an Asset with uploading data provided:
mutation {
createAsset(
parentId: 1,
filename: "foo.png",
type: "image",
input: {
data: "ewogICAgImZpZWxkY29sbGVjdGlvbiI6IFsKICAgICAgICB7CiAgICAgICAgICAgICJwYXJlbn...."
}) {
success
mes... | Create Asset | [
-0.1279015988111496,
-0.17594851553440094,
-0.20271797478199005,
-0.16710330545902252,
0.3050345480442047,
-0.13923101127147675,
0.26232093572616577,
0.3334448039531708,
-0.08142201602458954,
-0.024424219503998756,
0.08886314183473587,
0.2142183482646942,
-0.038447946310043335,
0.057699739... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Asset_Mutations#update-asset | Update Asset
This will rename the Asset and update the data.
Request:
mutation {
updateAsset(id: 76, input: {filename:"newfilename",
data:"iVBORw0KGgoAAAANSUhEUg....."}) {
success
message
assetData {
modificationDate
}
}
}
| Update Asset | [
0.07724732160568237,
0.2452131062746048,
-0.20735174417495728,
-0.19620022177696228,
0.1622050255537033,
0.00351679022423923,
0.21589963138103485,
0.5065470933914185,
-0.1927138715982437,
-0.11739857494831085,
-0.09478045254945755,
0.3280158042907715,
0.3532152771949768,
-0.143125146627426... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Asset_Mutations#delete-asset | Delete Asset
mutation {
deleteAsset(id: 533) {
success
message
}
}
or
mutation {
deleteAsset(fullpath: "/Sample Content/Background Images/foo.png") {
success
message
}
}
| Delete Asset | [
0.021025775000452995,
-0.19593816995620728,
-0.20583033561706543,
-0.05538742616772652,
-0.06453800201416016,
-0.06829550862312317,
0.32963812351226807,
0.34140533208847046,
-0.08874242752790451,
0.06724956631660461,
-0.17135651409626007,
0.2385910600423813,
0.018013037741184235,
-0.317160... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/DataObject_Mutations#dataobject-mutations | DataObject Mutations
TODO: Align this with the new demo as soon as reasonable content is available.
Create Objects
Update Objects
Delete Objects
In addition, you can turn on mutations to modify assets, create object folders and on on.
Note that for Create and Update operate you can query the updated data using the... | DataObject Mutations | [
-0.1508055329322815,
0.27549055218696594,
-0.24790215492248535,
0.08542252331972122,
0.06764204055070877,
-0.26223647594451904,
0.14384111762046814,
0.29009851813316345,
-0.3290182948112488,
0.06897144764661789,
-0.3025665879249573,
0.39228662848472595,
-0.12527936697006226,
-0.01872126385... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/DataObject_Mutations#supported-mutation-datatypes | Supported Mutation Datatypes
Also check out the Pimcore's data type documentation.
Boolean Select
Checkbox
Country
Countries (Multiselect)
Date
DateTime
Email
External Image
Field Collections
Firstname
Gender
Geopoint
Image
ImageGallery
Input
Language
Lastname
Link
Many-to-One Relation
Many-to-Many Relation
Many-to-M... | Supported Mutation Datatypes | [
-0.47593221068382263,
-0.06038912758231163,
-0.12053045630455017,
-0.03991325944662094,
-0.022558512166142464,
-0.26545315980911255,
0.12167326360940933,
0.22216016054153442,
0.03588961809873581,
0.0892644077539444,
-0.2501586973667145,
0.6486928462982178,
0.02089179866015911,
0.4668458998... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/DataObject_Mutations#supported-mutation-operators | Supported Mutation Operators
IfEmpty
Locale Switcher
...
See the overview page for more details. | Supported Mutation Operators | [
-0.24436673521995544,
-0.4333489239215851,
-0.17087188363075256,
-0.256279319524765,
0.06729460507631302,
-0.27890846133232117,
0.23081070184707642,
-0.03352179750800133,
-0.029681524261832237,
0.09364400058984756,
-0.21617932617664337,
0.22851961851119995,
-0.21560269594192505,
0.15088838... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/DataObject_Mutations#create-object | Create Object
TBD: do we need an extra workspace permission for that ? (in addition to write which would be only used for updates)
Request:
mutation {
createNews(parentId: 66, key: "testcreate27", published: false) {
success
message
output(defaultLanguage: "de") {
id
... | Create Object | [
0.11394479870796204,
0.1057402640581131,
-0.06394297629594803,
-0.19034536182880402,
-0.11791470646858215,
-0.2345331609249115,
0.18704791367053986,
0.1647772639989853,
0.006199186202138662,
0.02210122160613537,
-0.011336544528603554,
0.06065096706151962,
-0.13423480093479156,
0.1272642016... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/DataObject_Mutations#update-object | Update Object
Updates german title and short text and returns the modification date.
Request:
mutation {
updateNews(id: 773, defaultLanguage: "de", input: {title: "german TITLE", shortText: "new short text"}) {
success
output {
modificationDate
}
}
}
Response:
{
&q... | Update Object | [
0.16400213539600372,
0.05231587588787079,
-0.14831465482711792,
-0.10061230510473251,
0.02877129800617695,
-0.36069273948669434,
-0.12650229036808014,
0.22291453182697296,
-0.17737895250320435,
-0.030613046139478683,
0.014715625904500484,
0.37678223848342896,
0.3616931736469269,
-0.0609869... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/DataObject_Mutations#delete-object | Delete Object
Request:
mutation {
deleteBlogCategory(id: 37) {
success
message
}
}
Response:
{
"data": {
"deleteBlogCategory": {
"success": true,
"message": ""
}
}
}
| Delete Object | [
0.42954587936401367,
-0.10344935953617096,
-0.20883004367351532,
-0.0041587441228330135,
0.017365291714668274,
-0.07081843912601471,
-0.043754566460847855,
0.27788275480270386,
-0.18807552754878998,
-0.0962744727730751,
-0.20385874807834625,
0.522498607635498,
-0.1328260600566864,
-0.03710... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/DataObject_Mutations#extend-data-object-mutations | Extend Data Object Mutations
It is possible to add custom mutation data types and mutation operators. For details see detail documentation
pages:
Add a custom mutation datatype
Add a custom mutation operator
| Extend Data Object Mutations | [
-0.19896003603935242,
-0.10719907283782959,
-0.22551129758358002,
-0.09821107983589172,
0.22967173159122467,
-0.2135402411222458,
0.12992320954799652,
0.1149856299161911,
-0.042660314589738846,
0.13608545064926147,
-0.19391867518424988,
0.44221028685569763,
-0.07726145535707474,
0.13124118... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/DataObject_Mutations#more-examples | More Examples
See following list for more examples with data object mutations:
Add Relations
Fieldcollection Mutations
| More Examples | [
-0.043328940868377686,
0.23350019752979279,
-0.1811654269695282,
0.05845271050930023,
0.012322399765253067,
-0.06353054940700531,
0.1819097250699997,
0.05758059397339821,
-0.09333068877458572,
0.07659178972244263,
0.051437538117170334,
0.5381149649620056,
0.08841902017593384,
0.01572393998... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Mutation_Operators#mutation-operators | Mutation Operators
Operators allow to modify and transform the data before it is stored in Pimcore.
| Mutation Operators | [
-0.17665113508701324,
-0.13113676011562347,
-0.21284909546375275,
-0.08069419860839844,
0.1275029331445694,
-0.5046712160110474,
0.001369022880680859,
0.014108006842434406,
-0.39906254410743713,
0.29931095242500305,
-0.35023191571235657,
0.45608434081077576,
-0.041415393352508545,
0.150685... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Mutation_Operators#ifnotempty | IfNotEmpty
Only sets the value if current one is empty. | IfNotEmpty | [
-0.008977113291621208,
-0.30820432305336,
-0.21651571989059448,
0.1460438221693039,
-0.24523332715034485,
-0.2683796286582947,
0.14399367570877075,
0.13781382143497467,
0.051219772547483444,
0.4412224292755127,
0.35385242104530334,
-0.12528106570243835,
-0.0351642370223999,
-0.028050476685... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Mutation_Operators#locale-switcher | Locale Switcher
Switches to different language other than the default language. | Locale Switcher | [
-0.05059288069605827,
-0.2661501169204712,
-0.10484600812196732,
0.08913353830575943,
0.08453657478094101,
-0.14770105481147766,
0.23321592807769775,
-0.039815276861190796,
0.07851364463567734,
0.2217312902212143,
0.005967943929135799,
0.27549025416374207,
0.07276105880737305,
0.0258447285... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Mutation_Operators#locale-collector | Locale Collector
Allows editing all languages for a single field. | Locale Collector | [
-0.04764733463525772,
0.3028317093849182,
-0.2976258099079132,
-0.03743479773402214,
0.17085331678390503,
-0.12536057829856873,
0.23038657009601593,
0.3328550457954407,
-0.1088271215558052,
0.30016177892684937,
-0.15070180594921112,
0.10069602727890015,
-0.057889774441719055,
-0.0227671824... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Mutation_Samples/FreeformAPI_Create_Document_with_Areablocks#[freeform]-create-document-with-areablocks-and-nested-block-with-images | [FreeForm] Create Document With Areablocks and Nested Block With Images
See demo document 99 for reference.
mutation {
createDocumentPage(
key: "documentkey47"
parentId: 1
input: {
editables: {
areablock: [
{
_editableName: "conte... | [FreeForm] Create Document With Areablocks and Nested Block With Images | [
-0.10800358653068542,
-0.1770651936531067,
-0.21636632084846497,
0.13596853613853455,
-0.16714337468147278,
0.015208909288048744,
0.409803569316864,
0.41496893763542175,
0.32132968306541443,
0.19342678785324097,
0.10453753173351288,
0.11754016578197479,
0.14026594161987305,
-0.003658691886... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Mutation_Samples/FreeformAPI_Update_Email_Document#[freeform]-update-email-document | [FreeForm] Update Email Document
See demo document 144 for reference.
mutation {
updateDocumentEmail(
id: 144
editableUpdateStrategy: replaceAll # defaults to update
input: {
editables: {
wysiwyg: [
{
_editableName: "greeting_text"
... | [FreeForm] Update Email Document | [
0.1440095156431198,
-0.008407740853726864,
0.014281258918344975,
-0.18158231675624847,
0.2816529870033264,
-0.031829144805669785,
0.23091870546340942,
0.24916952848434448,
-0.13843096792697906,
0.10508763790130615,
0.12558892369270325,
0.2577996253967285,
-0.06340141594409943,
0.1765467822... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Mutation_Samples/FreeformAPI_Create_new_Link_Document#[freeform]-create-a-new-link-document | [FreeForm] Create a New Link Document
mutation {
createDocumentLink(key: "newlinkdocument", parentId:1, input: {
internal:308
internalType:"asset"
}
) {
success
}
}
| [FreeForm] Create a New Link Document | [
-0.1989600509405136,
-0.13531547784805298,
-0.09386119246482849,
-0.014115463942289352,
0.0014533695066347718,
-0.28584226965904236,
0.14129017293453217,
0.5053992867469788,
0.10927833616733551,
-0.018439454957842827,
-0.0899171456694603,
0.25231117010116577,
0.012703130021691322,
-0.08040... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Mutation_Samples/TreeAPI_Create_Document_with_Areablocks#[treeapi]-create-document-with-areablocks-and-nested-block-with-images | [TreeAPI] Create Document With Areablocks and Nested Block With Images
Note that this produces the same result as this example
but uses the nested API instead of the free-form approach
mutation {
createDocumentPage(
key: "documentkey48"
parentId: 1
input: {
editables: {
... | [TreeAPI] Create Document With Areablocks and Nested Block With Images | [
-0.06189675256609917,
-0.14905427396297455,
-0.1737930178642273,
0.053364068269729614,
-0.21567068994045258,
0.017049796879291534,
0.21450279653072357,
0.45888763666152954,
0.18650755286216736,
0.07610064744949341,
-0.005435963161289692,
0.38727661967277527,
0.20802433788776398,
0.03322232... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Mutation_Samples/Sample_Add_Relations#sample-add-relations | Sample Add Relations
This will add relations to categories relation field of Car object. Type can be omitted for
mutations only allowing one type, e.g. many-to-many-objects .
Note: Read permissions are required for related objects to be assigned.
Request:
mutation {
createCar (
key: "test-car",
pa... | Sample Add Relations | [
-0.061818767338991165,
0.22522559762001038,
-0.09800439327955246,
0.045870341360569,
0.09997192770242691,
0.108559250831604,
0.03840457275509834,
0.2528338134288788,
-0.19668768346309662,
-0.3643673360347748,
-0.04296046867966652,
0.5352698564529419,
0.05600865185260773,
-0.025118999183177... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Mutation_Samples/Fieldcollection_Mutations#fieldcollection-mutations | Fieldcollection Mutations
A Field Collection
is a list of items which can have different types.
Since there is no Union input type in GraphQL, the approach for Fieldcollection mutations is different.
The mutation processor expects a list of items for a specific type.
Within the list, all items are listed with their ind... | Fieldcollection Mutations | [
-0.006058436818420887,
0.1281728297472,
-0.0872044637799263,
0.18732792139053345,
-0.3018219769001007,
-0.009325842373073101,
-0.1297520101070404,
0.17125193774700165,
0.2539251446723938,
-0.02959853783249855,
0.07295489311218262,
0.4832680821418762,
0.031793124973773956,
-0.06421033293008... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Mutation_Samples/Fieldcollection_Mutations#example | Example
mutation {
updateNews(
id: 1143
input: {
content: {
replace: false
items: {
NewsText: [{ index: 1, text: "news text" }]
NewsCars: [
{ index: 0, relatedCars: [{ type: "object", id: 318 }, { type: "object", id: 38 }] }
{ index: 2, title: &q... | Example | [
-0.0036313673481345177,
-0.1953916847705841,
-0.22170811891555786,
-0.10135706514120102,
0.10162647068500519,
-0.0582033209502697,
-0.05688755214214325,
0.34733846783638,
-0.03205403685569763,
-0.10797269642353058,
-0.1104641780257225,
0.5654739737510681,
0.08506661653518677,
0.02082399465... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Mutation_Samples/Fieldcollection_Mutations#notes | Notes | Notes | [
-0.016914453357458115,
-0.4316244423389435,
-0.34626007080078125,
0.427049458026886,
0.10867005586624146,
0.04726218804717064,
-0.03976982459425926,
0.042672913521528244,
-0.3682597875595093,
0.38127338886260986,
0.06945302337408066,
-0.05854159593582153,
-0.1467302292585373,
-0.2071422487... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Mutation_Samples/Fieldcollection_Mutations#index | Index
The index is optional. If no index is provided then an autoincrement is used. | Index | [
0.15989159047603607,
-0.4326306879520416,
-0.23795078694820404,
-0.11767182499170303,
-0.12670162320137024,
-0.016428211703896523,
0.2574250102043152,
-0.05836186930537224,
0.3034925162792206,
0.41477879881858826,
0.3772748112678528,
0.07138781994581223,
0.09202646464109421,
-0.01174934767... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Mutation_Samples/Fieldcollection_Mutations#replace-vs.-overwrite | Replace vs. Overwrite
If replace is set to true (default is false) then the entire collection will be replaced.
Otherwise individual items will be overwritten. | Replace vs. Overwrite | [
0.19732825458049774,
0.04769250750541687,
-0.2417391985654831,
-0.2531086802482605,
-0.09426718205213547,
-0.2328725904226303,
0.30870985984802246,
-0.014539695344865322,
-0.048553209751844406,
0.20996704697608948,
0.11126451939344406,
0.30610594153404236,
0.3311009407043457,
-0.1755698919... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Mutation_Samples/Operators/Locale_Collector#datahubgraphqlmutationmutation_samplesoperatorslocale_collector | Datahub/GraphQL/Mutation/Mutation_Samples/Operators/Locale_Collector
| Datahub/GraphQL/Mutation/Mutation_Samples/Operators/Locale_Collector | [
-0.14363038539886475,
0.37365782260894775,
-0.1899612993001938,
-0.13822217285633087,
-0.10598543286323547,
-0.3338221609592438,
0.28639668226242065,
0.060877349227666855,
-0.011668268591165543,
0.18518047034740448,
-0.14069092273712158,
0.3875710070133209,
-0.2015695571899414,
0.143571570... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Mutation_Samples/Operators/Locale_Collector#title:-locale-collector | title: Locale Collector | title: Locale Collector | [
0.06509991735219955,
0.3868826925754547,
-0.22663545608520508,
0.1685332953929901,
0.03339776769280434,
-0.055751290172338486,
0.35776278376579285,
0.14112317562103271,
-0.05476434901356697,
0.4219430088996887,
-0.12313973158597946,
0.0057439482770860195,
-0.250918984413147,
-0.30450281500... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Mutation_Samples/Operators/Locale_Collector#sample-for-mutation-operator-"locale-collector" | Sample for Mutation Operator "Locale Collector"
mutation {
updateTable(
id: 7
input: {
name_translated: {
en: "Dinner table"
de: "Esstisch"
}
}
) {
success
message
output {
name_en: name(language: "en")
name_de: ... | Sample for Mutation Operator "Locale Collector" | [
-0.04851828143000603,
0.1674075722694397,
-0.18869167566299438,
-0.12751354277133942,
0.06299851834774017,
-0.20534199476242065,
0.07650113850831985,
0.2789517939090729,
-0.0502827949821949,
0.11391711235046387,
-0.08560303598642349,
0.6511564254760742,
0.10398513823747635,
-0.106982260942... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Add_Custom_Mutation_Datatype#add-a-custom-mutation-datatype | Add a Custom Mutation Datatype
For adding a new mutation data type two steps are necessary:
add an input type definition
provide a processor implementation
Add a section similar to this one to your services.yml file.
pimcore.datahub.graphql.dataobjectmutationtypegenerator_datatype_mycustomdatatype:
class:... | Add a Custom Mutation Datatype | [
-0.33254173398017883,
-0.046705156564712524,
-0.008990844711661339,
-0.26935774087905884,
-0.05894451588392258,
-0.30129748582839966,
0.02773464098572731,
0.052860528230667114,
0.19496776163578033,
0.0474490188062191,
-0.07808691263198853,
0.7258544564247131,
-0.17646588385105133,
0.426671... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Add_Custom_Mutation_Operator#add-a-custom-mutation-operator | Add a Custom Mutation Operator
For adding a new mutation operator two steps are necessary:
add a type definition
add the operator implementation
| Add a Custom Mutation Operator | [
-0.12432865053415298,
-0.14950765669345856,
-0.1142660453915596,
-0.276096373796463,
0.11577163636684418,
-0.21049118041992188,
0.1929750293493271,
0.1102498471736908,
0.02053968422114849,
0.1211588904261589,
-0.2513994574546814,
0.4742497503757477,
-0.1478467434644699,
0.06215552613139152... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Add_Custom_Mutation_Operator#type-definition | Type Definition
Add a section similar to this one to your services.yml file.
pimcore.datahub.graphql.dataobjectmutationtypegenerator_operator_mycustommutationoperator:
class: Pimcore\Bundle\DataHubBundle\GraphQL\DataObjectMutationOperatorConfigGenerator\MyCustomMutationOperator
tags:
- { name: pimcore.d... | Type Definition | [
-0.31639784574508667,
-0.2596571743488312,
-0.009782042354345322,
-0.06018831580877304,
-0.011340404860675335,
-0.3460851013660431,
0.09849970787763596,
0.15877196192741394,
0.27275991439819336,
0.13931380212306976,
0.030787060037255287,
0.5498653054237366,
-0.2808237075805664,
0.488708436... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Add_Custom_Mutation_Operator#operator-implementation | Operator Implementation
You have to provide both JavaScript code dealing with the UI configuration aspects specific to your operator
and the server-side PHP implementation processing the input (the input processor according to your input schema).
A JS sample can be found
here.
Note that the namespace in your case would... | Operator Implementation | [
-0.01634438894689083,
-0.08381916582584381,
-0.07286202162504196,
-0.06994841247797012,
-0.08615598827600479,
-0.6415978670120239,
0.3510788679122925,
-0.10820209980010986,
-0.23996275663375854,
0.443718284368515,
-0.16044732928276062,
0.40022173523902893,
-0.0024299444630742073,
0.2005274... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Mutation/Add_Custom_Mutations#add-custom-mutations | Add Custom Mutations
You can extend the mutation schema and add your custom mutations in the following way.
See Events and Event Listeners
if you need more information on Pimcore's event mechanism.
\Pimcore::getEventDispatcher()->addListener(\Pimcore\Bundle\DataHubBundle\Event\GraphQL\MutationEvents::PRE_BUILD,
... | Add Custom Mutations | [
-0.4793630540370941,
-0.08358170837163925,
-0.06192931532859802,
-0.03495686501264572,
-0.09150411188602448,
-0.47691231966018677,
0.009455514140427113,
0.0163798239082098,
0.07875284552574158,
0.18391692638397217,
-0.25861993432044983,
0.7718963623046875,
-0.12608779966831207,
0.397788882... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Events#events | Events
Datahub GraphQL events are based on the Symfony event dispatcher, and are triggered during execution of Query and Mutation requests.
Read more about events on Pimcore documentation.
All Datahub events are defined as a constant on component classes:
Query
Mutation
Executor
Listing
Ouput cache
| Events | [
-0.31517383456230164,
0.05507053807377815,
-0.07262901961803436,
0.013257469050586224,
-0.3480311334133148,
-0.43464022874832153,
-0.024721650406718254,
-0.14543971419334412,
0.19083552062511444,
0.10841475427150726,
0.043260302394628525,
0.44678863883018494,
-0.012364553287625313,
0.38343... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Events#event-subscriber-examples | Event Subscriber Examples
With Symfony, you can listen to events using either Event Listeners or Event Subscribers.
Event Subscribers are used in the examples below.
Create a new class in src/AppBundle/EventListener/GraphQlSubscriber.php and use autoconfigure: true in your service configuration file
(app/config/service... | Event Subscriber Examples | [
-0.4055013060569763,
0.11414855718612671,
-0.0347752720117569,
-0.039664991199970245,
-0.10378844290971756,
-0.31101351976394653,
0.18287532031536102,
0.007810282055288553,
0.39934059977531433,
0.376901775598526,
0.06435780227184296,
0.3299061357975006,
-0.4315972328186035,
0.2398483157157... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Events#example-1:-query-&-mutation-execution | Example 1: Query & Mutation execution
<?php
namespace AppBundle\EventListener;
use Pimcore\Bundle\DataHubBundle\Event\GraphQL\ExecutorEvents;
use Pimcore\Bundle\DataHubBundle\Event\GraphQL\Model\ExecutorEvent;
use Pimcore\Bundle\DataHubBundle\Event\GraphQL\Model\ExecutorResultEvent;
use Symfony\Component\EventD... | Example 1: Query & Mutation execution | [
-0.4535232484340668,
-0.134197399020195,
-0.1576067954301834,
0.14324721693992615,
-0.17008408904075623,
-0.5121110677719116,
-0.045564185827970505,
0.0450589582324028,
0.14487183094024658,
0.23537912964820862,
-0.036562561988830566,
0.43708762526512146,
-0.05331305414438248,
-0.0893617868... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Events#example-2:-bypass-workspace-permissions-with-querymutation-build-events | Example 2: Bypass workspace permissions with Query/Mutation build events
<?php
namespace AppBundle\EventListener;
use Pimcore\Bundle\DataHubBundle\Event\GraphQL\MutationEvents;
use Pimcore\Bundle\DataHubBundle\Event\GraphQL\Model\MutationTypeEvent;
use Pimcore\Bundle\DataHubBundle\Event\GraphQL\Model\QueryTypeEvent... | Example 2: Bypass workspace permissions with Query/Mutation build events | [
-0.3390832245349884,
0.3337255120277405,
-0.11014953255653381,
0.015833675861358643,
-0.353358656167984,
-0.47324785590171814,
0.2525937557220459,
0.2899159789085388,
0.15218833088874817,
0.3549574315547943,
-0.2312207818031311,
0.41283726692199707,
-0.1011262983083725,
-0.0209812559187412... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Events#example-3:-add-custom-arguments-to-existing-types | Example 3: Add custom arguments to existing types
<?php
namespace AppBundle\EventListener;
use Pimcore\Bundle\DataHubBundle\Event\GraphQL\MutationEvents;
use Pimcore\Bundle\DataHubBundle\Event\GraphQL\Model\MutationTypeEvent;
use Pimcore\Bundle\DataHubBundle\Event\GraphQL\Model\QueryTypeEvent;
use Symfony\Component... | Example 3: Add custom arguments to existing types | [
-0.4001729488372803,
-0.05411317199468613,
-0.06240660324692726,
0.24467965960502625,
-0.19162143766880035,
-0.4356803596019745,
0.14196552336215973,
0.09868945926427841,
0.1669132113456726,
0.019507311284542084,
-0.11446265131235123,
0.5595816969871521,
-0.0969725251197815,
0.034410517662... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Events#example-4:-add-custom-query-conditions-to-object-listing | Example 4: Add custom query conditions to object listing
For global SQL conditions also General Settings
For simple filter conditions also see Filtering
<?php
namespace AppBundle\EventListener;
use Pimcore\Model\DataObject\Service;
use Pimcore\Bundle\DataHubBundle\Event\GraphQL\ListingEvents;
use Pimcore\Bundle... | Example 4: Add custom query conditions to object listing | [
-0.28752607107162476,
-0.088384248316288,
-0.1668887883424759,
0.20011965930461884,
-0.225030317902565,
-0.5037521123886108,
-0.18944098055362701,
0.2889874279499054,
0.31281179189682007,
-0.0794171467423439,
-0.23676341772079468,
0.4141313433647156,
-0.06702148169279099,
0.291041582822799... |
https://pimcore.com/docs/platform//Datahub/GraphQL/Events#example-5:-add-custom-conditions-to-enabledisable-output-(responses)-cache-per-request | Example 5: Add custom conditions to enable/disable output (responses) cache per request
OutputCacheEvents::PRE_LOAD: is triggered before trying to load an entry from cache, if cache is enabled. You can disable the cache for this request by setting $event->setUseCache(false). If you disable the cache, the entry wo... | Example 5: Add custom conditions to enable/disable output (responses) cache per request | [
-0.17807452380657196,
-0.1360296756029129,
-0.13156747817993164,
0.0771080031991005,
-0.27701881527900696,
-0.5246546864509583,
-0.03241965174674988,
0.21210727095603943,
0.386507511138916,
0.0682263895869255,
-0.0677926167845726,
0.2704260051250458,
0.045576293021440506,
0.064931742846965... |
https://pimcore.com/docs/platform//Datahub/GraphQL#datahubgraphql | Datahub/GraphQL
| Datahub/GraphQL | [
-0.2881881892681122,
0.06434548646211624,
-0.30703121423721313,
-0.01861765794456005,
-0.40019461512565613,
-0.2725207507610321,
0.23494763672351837,
0.08273538947105408,
0.43488609790802,
0.21217310428619385,
-0.13334211707115173,
0.2464311420917511,
-0.07037799805402756,
0.78111433982849... |
https://pimcore.com/docs/platform//Datahub/GraphQL#title:-graphql | title: GraphQL | title: GraphQL | [
0.032722391188144684,
0.1207767203450203,
-0.3566285967826843,
-0.025270210579037666,
-0.024240760132670403,
-0.11138709634542465,
0.15060827136039734,
0.04520697891712189,
0.494809627532959,
0.3518557846546173,
0.02728603407740593,
0.21288475394248962,
-0.14663901925086975,
0.288876712322... |
https://pimcore.com/docs/platform//Datahub/GraphQL#-graphql | GraphQL
With GraphQL endpoints, Datahub allows integrating Pimcore to other systems
and services via GraphQL and test them with the integrated
GraphiQL explorer tool right away.
| GraphQL | [
-0.5811161398887634,
-0.14178410172462463,
-0.1854405254125595,
-0.1744140088558197,
-0.3691570460796356,
-0.3255486488342285,
0.0545518659055233,
0.016038060188293457,
0.3536754846572876,
0.07756896317005157,
-0.2605704963207245,
0.6008426547050476,
0.12475509941577911,
0.7045472860336304... |
https://pimcore.com/docs/platform//Datahub/GraphQL#configuration | Configuration
Configuration takes place in the endpoint configuration and offers following possibilities:
General Settings
Schema Definition
Security Settings
Custom Permissions
| Configuration | [
-0.018620720133185387,
-0.3363243341445923,
-0.209370955824852,
-0.2035093456506729,
-0.13072669506072998,
-0.1366063505411148,
0.09606600552797318,
-0.39151817560195923,
0.045210354030132294,
0.11372917145490646,
-0.03283495455980301,
0.0712156891822815,
0.2065524011850357,
0.143368527293... |
https://pimcore.com/docs/platform//Datahub/GraphQL#external-access | External Access
The standard endpoint is
/pimcore-graphql-webservices/{configurationname}?apikey={yourApiKey}
So if your configuration name is blogdemo and your apikey 123456 then your endpoint would be
/pimcore-graphql-webservices/blogdemo?apikey=123456
Here is a configuration how to override the standard endpoint | External Access | [
-0.18768590688705444,
-0.2590433359146118,
-0.12271298468112946,
-0.27724751830101013,
-0.09140325337648392,
-0.32364386320114136,
-0.0849563479423523,
-0.21835871040821075,
0.006572330370545387,
0.07216446101665497,
-0.25442585349082947,
0.6851329803466797,
0.2916340231895447,
0.430955410... |
https://pimcore.com/docs/platform//Datahub/GraphQL#queries | Queries
Depending on the configuration, the endpoint provides several queries to fetch data from Pimcore. As
Datahub always creates a proper graphQL schema, also have a look at the generated schema to get details
for the possible queries of a certain endpoint.
On the following pages certain generic aspects are explaine... | Queries | [
-0.11675194650888443,
-0.35246163606643677,
-0.28718116879463196,
0.35064417123794556,
-0.3868945240974426,
-0.4760574996471405,
-0.11332366615533829,
-0.288595974445343,
0.06858369708061218,
0.11469756811857224,
-0.41620907187461853,
0.3460657000541687,
0.38343489170074463,
0.270857006311... |
https://pimcore.com/docs/platform//Datahub/GraphQL#mutations | Mutations
Depending on the configuration, the endpoint provides several mutations to update data in Pimcore. As
Datahub always creates a proper graphQL schema, also have a look at the generated schema to get details
for the possible mutations of a certain endpoint.
See following pages for a general overview of possible... | Mutations | [
-0.17332810163497925,
-0.177700474858284,
-0.1738491803407669,
0.06871461123228073,
-0.1587657630443573,
-0.47385072708129883,
-0.198838472366333,
-0.23577459156513214,
0.002887710928916931,
0.23829177021980286,
-0.25603920221328735,
0.5732420682907104,
0.3176393210887909,
0.25550127029418... |
https://pimcore.com/docs/platform//Datahub/GraphQL#hands-on-testing-using-graphiql-explorer | Hands-On-Testing Using GraphiQL Explorer
GraphiQL explorer can be opened
for an endpoint in an iframe within Pimcore or as an additional browser tab.
| Hands-On-Testing Using GraphiQL Explorer | [
-0.285809189081192,
-0.23534037172794342,
-0.16300763189792633,
-0.16493414342403412,
-0.24810007214546204,
-0.38644856214523315,
0.2830558717250824,
-0.18244199454784393,
0.041985929012298584,
0.05612518638372421,
-0.2184598594903946,
0.2843465209007263,
0.04469461739063263,
0.64272946119... |
https://pimcore.com/docs/platform//Datahub/GraphQL#events | Events
It is possible to customize default behavior of graphQL endpoint with event listeners. For details
see Events Documentation. | Events | [
-0.24109795689582825,
-0.10538414120674133,
-0.16956904530525208,
-0.20208840072155,
-0.18001587688922882,
-0.4956505298614502,
0.0260529313236475,
-0.051133789122104645,
0.3019821047782898,
0.21860727667808533,
0.052072253078222275,
0.4847089350223541,
-0.1475459784269333,
0.3614052832126... |
https://pimcore.com/docs/platform//Datahub/GraphQL#output-cache | Output Cache
It is possible to keep a cache of the responses delivered by the endpoint, using the same default cache backend configured for Pimcore (Doctrine, Redis,...). This is specially useful to speed up the endpoint replies when it produces complex responses with many dependencies.
The cache can be enabled and con... | Output Cache | [
-0.4999474883079529,
-0.2071833610534668,
-0.13867269456386566,
-0.14958278834819794,
-0.21122808754444122,
-0.34428513050079346,
-0.04314573109149933,
0.2636968791484833,
0.11280989646911621,
0.24830655753612518,
-0.2300277203321457,
0.46565574407577515,
0.16407905519008636,
0.34565740823... |
https://pimcore.com/docs/platform//Datahub/GraphQL#disable-output-cache-for-a-single-request-(only-in-debug-mode) | Disable Output Cache for a Single Request (Only in DEBUG MODE)
Just add the parameter ?pimcore_outputfilters_disabled=true to the URL. This works in a similar way as the Pimcore's Full Page Cache. | Disable Output Cache for a Single Request (Only in DEBUG MODE) | [
-0.2920265793800354,
-0.24336330592632294,
-0.14062243700027466,
-0.0469571016728878,
-0.007717852480709553,
-0.22353042662143707,
0.12006546556949615,
0.2500695586204529,
-0.29381537437438965,
0.3349236845970154,
-0.2205648422241211,
0.3493008613586426,
0.22868862748146057,
0.089846141636... |
https://pimcore.com/docs/platform//Datahub/GraphQL#customize-the-cache-behaviour | Customize the Cache Behaviour
It is possible to customize some behavior of output cache with event listeners. For details
see Events Documentation. | Customize the Cache Behaviour | [
-0.3704378604888916,
-0.1891462355852127,
-0.2396983504295349,
0.00480743357911706,
-0.002080980222672224,
-0.3319539725780487,
0.2719632685184479,
0.1814555525779724,
0.09182898700237274,
0.36800527572631836,
-0.025989392772316933,
0.16236166656017303,
-0.0775035098195076,
-0.016739847138... |
https://pimcore.com/docs/platform//Datahub/GraphQL#note-on-debugging-with-igraplql-playground | Note on Debugging With iGraplQL Playground
Open the settings and change request.credentials to include. Otherwise the
XDEBUG_SESSION cookie header will get removed by default.
| Note on Debugging With iGraplQL Playground | [
-0.15260015428066254,
-0.12930892407894135,
-0.016190921887755394,
0.10086497664451599,
-0.02675456926226616,
-0.18821528553962708,
0.45445433259010315,
0.06406586617231369,
0.027479788288474083,
0.11735609173774719,
0.10909005254507065,
-0.12518073618412018,
0.22856222093105316,
-0.237396... |
https://pimcore.com/docs/platform//Datahub/Deployment#configuration-&-deployment | Configuration & Deployment
The configuration by default is saved in var/config/data-hub/example.yaml.
Additionally, a workspace permission index is kept in the database for better query performance when
checking for permissions.
When deploying configurations following steps are necessary:
Deploy configuration fil... | Configuration & Deployment | [
-0.01396904606372118,
0.06104196980595589,
-0.05325722321867943,
-0.21565820276737213,
-0.2702052891254425,
-0.18635569512844086,
0.24371173977851868,
0.0508611723780632,
0.17354503273963928,
0.2502274513244629,
-0.2535124123096466,
0.1013772115111351,
0.023193901404738426,
0.3366476297378... |
https://pimcore.com/docs/platform//Datahub/Deployment#configuration-storage | Configuration Storage
The configuration user interface utilizes the LocationAwareConfigRepository for storing the configuration. In the symfony tree the storage location can be configured, possible values are
symfony-config - write configs as Symfony Config as YAML files to /var/config/data_hub/<name>.yaml
se... | Configuration Storage | [
-0.23420703411102295,
-0.05316923186182976,
-0.04414205253124237,
-0.024426333606243134,
0.11688679456710815,
-0.14738139510154724,
0.15838120877742767,
-0.03899708390235901,
-0.18566414713859558,
0.23373407125473022,
-0.3038841485977173,
0.1783173680305481,
0.22478768229484558,
0.03262226... |
https://pimcore.com/docs/platform//Datahub/Deployment#example | Example
pimcore_data_hub:
config_location:
data_hub:
write_target:
type: 'symfony-config'
options:
directory: '/var/www/html/var/config/data_hub'
Additionally, it is also possible to define the configuration directly in a symfony configurati... | Example | [
-0.29519540071487427,
-0.1938919574022293,
0.00839808490127325,
-0.10557852685451508,
0.21733269095420837,
-0.13026335835456848,
0.11569368094205856,
0.013121605850756168,
0.016036417335271835,
0.16417600214481354,
-0.4203968942165375,
0.38798588514328003,
0.05917233228683472,
0.1877825558... |
https://pimcore.com/docs/platform//Datahub/Deployment#sample-configuration-file | Sample Configuration File
pimcore_data_hub:
configurations:
<name>:
general:
active: true
type: '<TYPE>'
name: '<NAME>'
description: '<DESCRIPTION>'
group: '<GROUP>
sqlOb... | Sample Configuration File | [
-0.42822256684303284,
-0.2536165118217468,
-0.13796822726726532,
0.16113318502902985,
0.05512208119034767,
-0.17554889619350433,
-0.11090028285980225,
0.19726057350635529,
-0.3288152515888214,
0.1329823136329651,
-0.24127702414989471,
0.5829201340675354,
0.09000591188669205,
0.096041813492... |
https://pimcore.com/docs/platform//Datahub/Testing#testing | Testing | Testing | [
-0.3187021017074585,
-0.6292931437492371,
-0.44741931557655334,
0.02607215754687786,
-0.18005584180355072,
0.19733116030693054,
0.3822784721851349,
0.1788274496793747,
0.13406631350517273,
0.33404791355133057,
0.33279454708099365,
-0.1533205807209015,
-0.29043683409690857,
0.11046007275581... |
https://pimcore.com/docs/platform//Datahub/Testing#perform-phpstan-analysis | Perform PHPStan Analysis | Perform PHPStan Analysis | [
-0.5184912085533142,
-0.5266047120094299,
-0.37792739272117615,
0.501386821269989,
-0.3074228763580322,
-0.10723704844713211,
-0.045658987015485764,
0.21224814653396606,
-0.07993872463703156,
0.17887715995311737,
0.27217692136764526,
-0.3639061152935028,
-0.08173155784606934,
0.08841408044... |
https://pimcore.com/docs/platform//Datahub/Testing#data-hub-only-context | data-hub only context
´´´bash
.github/ci/scripts/setup-pimcore-environment.sh
composer install
vendor/bin/phpstan analyse --memory-limit=-1
´´´ | data-hub only context | [
-0.49424248933792114,
-0.20034973323345184,
-0.30063989758491516,
0.28269168734550476,
0.0007379879825748503,
-0.267114520072937,
-0.031493790447711945,
0.23015649616718292,
-0.13529051840305328,
0.48644283413887024,
-0.14677169919013977,
0.07415039837360382,
-0.050552669912576675,
0.23831... |
https://pimcore.com/docs/platform//Datahub/Testing#pimcore-context | Pimcore context
´´´bash
composer require "phpstan/phpstan:^1.4" --dev
vendor/bin/phpstan analyse -c vendor/pimcore/data-hub/phpstan.neon --memory-limit=-1
´´´ | Pimcore context | [
-0.4751479923725128,
-0.3729047477245331,
-0.2524024546146393,
0.4595271348953247,
-0.05531270056962967,
-0.17836353182792664,
-0.1505734771490097,
0.12829172611236572,
-0.18050579726696014,
0.44265204668045044,
0.048399582505226135,
-0.03470447659492493,
-0.16128239035606384,
0.1544106751... |
https://pimcore.com/docs/platform//Datahub#datahub | Datahub
| Datahub | [
-0.2526533305644989,
-0.08400356024503708,
-0.26753681898117065,
-0.04401189088821411,
-0.15033908188343048,
-0.273767352104187,
0.3698197305202484,
0.025633150711655617,
0.11977966874837875,
0.29561659693717957,
-0.1315189152956009,
0.08328481763601303,
-0.07403601706027985,
0.64435380697... |
https://pimcore.com/docs/platform//Datahub#title:-datahub | title: Datahub | title: Datahub | [
-0.027113817632198334,
0.005324868950992823,
-0.3742572069168091,
-0.13832323253154755,
-0.1125074028968811,
-0.00524465786293149,
0.4274100363254547,
0.019442059099674225,
0.1661253720521927,
0.2525539994239807,
-0.024683181196451187,
0.04253862798213959,
-0.12275009602308273,
0.453623503... |
https://pimcore.com/docs/platform//Datahub#pimcore-datahub | Pimcore Datahub
Pimcore Datahub (data delivery and consumption platform) integrates different input & output channel
technologies into a simple & easy-to-configure system on top of Pimcore.
The basic configuration of Datahub comes with a GraphQL API, which is described in the next sections of this documentation... | Pimcore Datahub | [
-0.41281038522720337,
-0.32333412766456604,
-0.22337990999221802,
-0.27479490637779236,
-0.29306983947753906,
-0.24158410727977753,
0.06701575964689255,
-0.033527106046676636,
0.010320566594600677,
0.1596880853176117,
-0.28824344277381897,
0.49699246883392334,
-0.08035669475793839,
0.76846... |
https://pimcore.com/docs/platform//Datahub#features-in-a-nutshell | Features in a Nutshell
Easy-to-configure interface layer for data delivery and consumption
Tool of choice to connect Pimcore to any other systems and applications besides internal PHP API - whether they are backend applications like ERP systems or frontend applications like your storefront
Multiple endpoints definitio... | Features in a Nutshell | [
-0.3941020667552948,
-0.5574909448623657,
-0.30269455909729004,
-0.002230627229437232,
-0.060712844133377075,
-0.23279891908168793,
-0.08014240115880966,
-0.07992969453334808,
-0.1452811062335968,
0.20954321324825287,
-0.16239212453365326,
0.5642014741897583,
0.13741189241409302,
0.5169303... |
https://pimcore.com/docs/platform//Datahub#documentation-overview | Documentation Overview
Installation
Basic principle for configuring an endpoint
GraphQL [default and recommended endpoint]
Configuration & Deployment
Testing
| Documentation Overview | [
-0.06239507347345352,
-0.21822084486484528,
-0.24515900015830994,
-0.28336724638938904,
-0.10273293405771255,
-0.24495941400527954,
0.03491852432489395,
-0.2959718108177185,
0.25501176714897156,
-0.05101005360484123,
0.14341512322425842,
0.4207712709903717,
0.19702060520648956,
0.390702694... |
https://pimcore.com/docs/platform//Datahub#further-information | Further Information
On Pimcore Datahub adapters:
Datahub Simple Rest API
Datahub File Export
Datahub Productsup
Datahub CI Hub
| Further Information | [
-0.3902952969074249,
-0.13946391642093658,
-0.252110093832016,
-0.0928645208477974,
-0.08217035979032516,
-0.22398605942726135,
0.4799479842185974,
0.05946227163076401,
0.089537613093853,
0.260986864566803,
-0.33873844146728516,
0.373783141374588,
0.11087226122617722,
0.997211217880249,
... |
https://pimcore.com/docs/platform//Datahub#contributions | Contributions
As Pimcore Datahub is a community project, any contributions highly appreciated.
For details see our Contributing guide. | Contributions | [
-0.3825418949127197,
0.1622265726327896,
-0.37901368737220764,
-0.03331425413489342,
-0.3124522566795349,
-0.4049886167049408,
0.21959705650806427,
-0.05053448677062988,
-0.28484854102134705,
0.14985433220863342,
-0.11911245435476303,
0.2306632548570633,
-0.09574705362319946,
0.48848250508... |
https://pimcore.com/docs/platform//Data_Importer/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//Data_Importer/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//Data_Importer/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//Data_Importer/Installation#for-pimcore->=-10.5 | For Pimcore >= 10.5
To install Pimcore Data Importer for Pimcore 10.5 or higher, follow the three steps below:
Install the required dependencies:
composer require pimcore/data-importer
Make sure the bundle is enabled in the config/bundles.php file. The following lines should be added:
use Pimcore\Bundle\DataImp... | For Pimcore >= 10.5 | [
-0.3891493082046509,
0.2143753319978714,
-0.17556217312812805,
0.1134742870926857,
0.026612473651766777,
-0.18297399580478668,
0.16686049103736877,
0.11764676868915558,
-0.3728123903274536,
0.3316153585910797,
-0.23785516619682312,
0.4256260395050049,
0.02543097734451294,
0.173182085156440... |
https://pimcore.com/docs/platform//Data_Importer/Installation#for-pimcore-11 | For Pimcore 11
You need to follow the steps mentioned above and additionally run the following command:
composer require pimcore/admin-ui-classic-bundle
| For Pimcore 11 | [
-0.3934876322746277,
-0.08261220157146454,
-0.14979122579097748,
0.02371276170015335,
0.18444740772247314,
-0.16008318960666656,
0.08403971791267395,
-0.0007112571038305759,
-0.09843407571315765,
0.22060109674930573,
-0.15307468175888062,
0.492026686668396,
-0.010796979069709778,
0.1577836... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.