{"id":2140,"date":"2020-07-11T12:30:56","date_gmt":"2020-07-11T17:30:56","guid":{"rendered":"https:\/\/www.teamdesk.net\/blog\/?p=2140"},"modified":"2021-09-28T08:04:57","modified_gmt":"2021-09-28T13:04:57","slug":"multi-level-tree","status":"publish","type":"post","link":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/multi-level-tree\/","title":{"rendered":"Multi-level tree of related records"},"content":{"rendered":"\n

If a table contains nested records, it means that there is a multi-level tree of related records.
In this blogpost you may read how the multi-level tree of related records can be configured.
Let\u2019s assume that within your database you need to register and calculate energy consumption of engines containing modules and submodules. The structure would look like a multi-level tree including the following levels: Engine(Parent)->Modules(Children)->SubModules(Grandchildren). The number of levels may be unlimited. The goal is to calculate the total energy consumption from the lowest level to the highest. Besides, if the highest-level record is deleted, all the related records will be deleted automatically.<\/p>\n\n\n\n

You may order a free trial of the pre-built \u201cExample: Multi-Level Tree\u201d database<\/a> to review the setup described below.<\/p>\n\n\n\n

This example contains a single table \u201cEngines\u201d. You may see this table structure on the screenshot:<\/p>\n\n\n\n

\"Multi-Lrevel<\/figure>\n\n\n\n

The multi-level tree has three levels: Engine->Modules->SubModules.
Building such a tree takes the following steps:<\/p>\n\n\n\n

1. First, you need a single-reference<\/a> column in the \u201cEngines\u201d table, while the table should refer to itself. One record is related to another the way a child is related to a parent. Each parent can be related to many children, while each child can be related to one parent. Let\u2019s name this reference column \u201cParent\u201d. In our example one Engine can be related to many Modules, while each Module can be related to many SubModules.
The \u201cParent\u201d single-reference column settings are shown on the screenshot below:<\/p>\n\n\n\n

\"Parent<\/figure>\n\n\n\n

2. You should also create the \u201cOld Parent\u201d single-reference column. This column participates in workflow actions making records recounting. It is needed as an auxiliary column, therefore the \u201cOld Parent\u201d reference column should be hidden on the form and removed from views.<\/p>\n\n\n\n

\"Old<\/figure>\n\n\n\n

3. In our example every engine or module or submodule has an energy consumption value, which is kept in the \u201cEnergy Consumption\u201d column. You would also need to calculate the energy consumption of related lower levels (Modules and SubModultes) and store this value within the Parent record, in the \u201cConsumption of Lower Levels\u201d numeric column<\/a>. Also, the \u201cNeed Recalculate\u201d checkbox column<\/a> should be created as it will be used for the assignments added to the workflow actions. You may see these three columns in the column list of the \u201cEngines\u201d table:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

4. Moreover, in the relation built by the \u201cParent\u201d reference column you would need to add two auxiliary columns that will be used in workflow actions. Firstly, lets create the \u201cCount Consumption of Lower Levels\u201d summary column<\/a>. It summarizes Energy Consumption values stored in related lower level records. Secondly, you should add a RecordSet column<\/a>, let\u2019s name it \u201cLower Levels Recordset\u201d. This column displays internal record IDs of related lower level records.<\/p>\n\n\n\n

\"Multi-Level<\/figure>\n\n\n\n

5. The last column that is obligatory to be created is the \u201cTotal Energy Consumption\u201d formula<\/a>-numeric column.<\/p>\n\n\n\n

\"Formula<\/figure>\n\n\n\n

6. Now you can configure workflow triggers of the Record Change type<\/a>.<\/p>\n\n\n\n

\"Workflow<\/figure>\n\n\n\n

The main advantage is that these triggers work as a cascade due to the \u201cExecute Triggers\u201d option activated in the workflow actions<\/a> stored in these triggers. Therefore, if an Energy Consumption value is added or changed in a record of a lower level (for example in SubModule), the system recalculates the total energy consumption in higher levels, such as \u201cModule\u201d and \u201cEngine\u201d records in our example.<\/p>\n\n\n\n

7. The first trigger is \u201cAdd\/Edit Trigger\u201d. It includes three actions of the Update Record type<\/a>:<\/p>\n\n\n\n

\"Add<\/figure>\n\n\n\n

If a Parent value is changed in a record, the \u201cRecalculate Parent\u201d action initiates the request to recalculate the Energy Consumption for the Parent record.<\/p>\n\n\n\n

Therefore, the \u201ctrue\u201d value is set in the \u201cNeed Recalculate\u201d checkbox column.<\/p>\n\n\n\n

\"Recalculate<\/figure>\n\n\n\n

The second action \u201cRecalculate Old Parent\u201d initiates the request to recalculate Energy Consumption for the Old Parent record.<\/p>\n\n\n\n

\"Recalculate<\/figure>\n\n\n\n

Please note that the \u201cExecute Triggers\u201d option is active in both of the above-mentioned actions.<\/p>\n\n\n\n

The third action is the \u201cUpdate Old Parent\u201d action. It is needed to update the Old Parent value by the Parent value after all recalculations had been made.<\/p>\n\n\n\n

\"Update<\/figure>\n\n\n\n

8. The \u201cRecalculate Trigger\u201d includes both the \u201cRecalculate Children\u201d action and the existing \u201cRecalculate Parent\u201d action described above.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The first \u201cRecalculate Children\u201d action assigns the \u201cCount Consumption of Lower Levels\u201d summary column value to the \u201cConsumption of Lower Levels\u201d numeric column. Also, it sets \u201cNeed Recalculate\u201d checkbox value to \u201cfalse\u201d. This last assignment is needed to stop the related details recalculation if such a recalculation is finished.<\/p>\n\n\n\n

The settings of the \u201cRecalculate Children\u201d action are displayed on the following screenshot:<\/p>\n\n\n\n

\"Recalculate<\/figure>\n\n\n\n

The second action is the \u201cRecalculate Parent\u201d action which is also used in the \u201cAdd\/Edit Trigger\u201d.
This action is needed to initiate the recalculation of records on higher levels.<\/p>\n\n\n\n

9. \u201cDelete Trigger\u201d allows to delete all Children records when a Parent record is deleted. There are three actions in this trigger:<\/p>\n\n\n\n

\"Delete<\/figure>\n\n\n\n

The first action is the \u201cDelete Children \u201d action<\/a>. It allows to delete related details listed in the \u201cLower Levels Recordset\u201d column when a Parent record is deleted.
\u201cExecute Triggers\u201d option is active in this action.<\/p>\n\n\n\n

\"Delete<\/figure>\n\n\n\n

The second \u201cClear Parent\u201d action is needed to clear a Parent value within deleted records. It allows to exclude deleted record from recalculation of the energy consumption value within the Parent record.<\/p>\n\n\n\n

Deleted record may be restored from the Recycle Bin, however, a restored record will not be related to any Parent automatically since its Parent field is empty.<\/p>\n\n\n\n

\"Clear<\/figure>\n\n\n\n

The third \u201cRecalculate old Parent\u201d action is an existing action that also participates in the \u201cAdd\/Edit Trigger\u201d described in the item # 7. Due to this action the deletion is repeated from the lowest level to the highest.<\/p>\n\n\n\n

10. If you would like to review the described setup, please try the \u201cExample: Multi-Level Tree\u201d template<\/a> from the database library.<\/p>\n\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

Here you may read how the multi-level tree of related records can be configured. For example such nested records: Engine(Parent)-> Modules(Children)-> SubModules(Grandchildren)<\/p>\n","protected":false},"author":3,"featured_media":2169,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[187,186,188,237],"class_list":["post-2140","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tips-tricks","tag-multi-level-tree-2","tag-multi-level-tree","tag-multilevel-tree","tag-nested-records"],"yoast_head":"\nMulti-level tree of related records - TeamDesk Blog<\/title>\n<meta name=\"description\" content=\"If a table contains nested records, it means that there is a multi-level tree of related records. In this blogpost we describe how the multi-level tree of related records can be configured. To review the described multi-level tree setup, try the \u201cExample: Multi-Level Tree\u201d template from the database library.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/multi-level-tree\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Multi-level tree of related records - TeamDesk Blog\" \/>\n<meta property=\"og:description\" content=\"If a table contains nested records, it means that there is a multi-level tree of related records. In this blogpost we describe how the multi-level tree of related records can be configured. To review the described multi-level tree setup, try the \u201cExample: Multi-Level Tree\u201d template from the database library.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/multi-level-tree\/\" \/>\n<meta property=\"og:site_name\" content=\"TeamDesk Blog\" \/>\n<meta property=\"article:published_time\" content=\"2020-07-11T17:30:56+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-09-28T13:04:57+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2020\/07\/Multi-Level-Tree-2.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1034\" \/>\n\t<meta property=\"og:image:height\" content=\"479\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Mila\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Mila\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/multi-level-tree\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/multi-level-tree\\\/\"},\"author\":{\"name\":\"Mila\",\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/#\\\/schema\\\/person\\\/63bd8646f2f4720f503116e38a190a6e\"},\"headline\":\"Multi-level tree of related records\",\"datePublished\":\"2020-07-11T17:30:56+00:00\",\"dateModified\":\"2021-09-28T13:04:57+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/multi-level-tree\\\/\"},\"wordCount\":951,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/multi-level-tree\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/07\\\/Multi-Level-Tree-2.png\",\"keywords\":[\"multi level tree\",\"multi-level tree\",\"multilevel tree\",\"nested records\"],\"articleSection\":[\"Tips & Tricks\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/multi-level-tree\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/multi-level-tree\\\/\",\"url\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/multi-level-tree\\\/\",\"name\":\"Multi-level tree of related records - TeamDesk Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/multi-level-tree\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/multi-level-tree\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/07\\\/Multi-Level-Tree-2.png\",\"datePublished\":\"2020-07-11T17:30:56+00:00\",\"dateModified\":\"2021-09-28T13:04:57+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/#\\\/schema\\\/person\\\/63bd8646f2f4720f503116e38a190a6e\"},\"description\":\"If a table contains nested records, it means that there is a multi-level tree of related records. In this blogpost we describe how the multi-level tree of related records can be configured. To review the described multi-level tree setup, try the \u201cExample: Multi-Level Tree\u201d template from the database library.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/multi-level-tree\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/multi-level-tree\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/multi-level-tree\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/07\\\/Multi-Level-Tree-2.png\",\"contentUrl\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/07\\\/Multi-Level-Tree-2.png\",\"width\":1034,\"height\":479,\"caption\":\"Multi-Level tree\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/tips-tricks\\\/multi-level-tree\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Multi-level tree of related records\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/\",\"name\":\"TeamDesk Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/#\\\/schema\\\/person\\\/63bd8646f2f4720f503116e38a190a6e\",\"name\":\"Mila\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/939a25c18364af1ceffe1d698a8fd01e1a18d8e1cf906fe3a6ac1cad64bc653f?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/939a25c18364af1ceffe1d698a8fd01e1a18d8e1cf906fe3a6ac1cad64bc653f?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/939a25c18364af1ceffe1d698a8fd01e1a18d8e1cf906fe3a6ac1cad64bc653f?s=96&d=mm&r=g\",\"caption\":\"Mila\"},\"url\":\"https:\\\/\\\/www.teamdesk.net\\\/blog\\\/author\\\/mila\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Multi-level tree of related records - TeamDesk Blog","description":"If a table contains nested records, it means that there is a multi-level tree of related records. In this blogpost we describe how the multi-level tree of related records can be configured. To review the described multi-level tree setup, try the \u201cExample: Multi-Level Tree\u201d template from the database library.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/multi-level-tree\/","og_locale":"en_US","og_type":"article","og_title":"Multi-level tree of related records - TeamDesk Blog","og_description":"If a table contains nested records, it means that there is a multi-level tree of related records. In this blogpost we describe how the multi-level tree of related records can be configured. To review the described multi-level tree setup, try the \u201cExample: Multi-Level Tree\u201d template from the database library.","og_url":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/multi-level-tree\/","og_site_name":"TeamDesk Blog","article_published_time":"2020-07-11T17:30:56+00:00","article_modified_time":"2021-09-28T13:04:57+00:00","og_image":[{"width":1034,"height":479,"url":"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2020\/07\/Multi-Level-Tree-2.png","type":"image\/png"}],"author":"Mila","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Mila","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/multi-level-tree\/#article","isPartOf":{"@id":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/multi-level-tree\/"},"author":{"name":"Mila","@id":"https:\/\/www.teamdesk.net\/blog\/#\/schema\/person\/63bd8646f2f4720f503116e38a190a6e"},"headline":"Multi-level tree of related records","datePublished":"2020-07-11T17:30:56+00:00","dateModified":"2021-09-28T13:04:57+00:00","mainEntityOfPage":{"@id":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/multi-level-tree\/"},"wordCount":951,"commentCount":0,"image":{"@id":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/multi-level-tree\/#primaryimage"},"thumbnailUrl":"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2020\/07\/Multi-Level-Tree-2.png","keywords":["multi level tree","multi-level tree","multilevel tree","nested records"],"articleSection":["Tips & Tricks"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.teamdesk.net\/blog\/tips-tricks\/multi-level-tree\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/multi-level-tree\/","url":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/multi-level-tree\/","name":"Multi-level tree of related records - TeamDesk Blog","isPartOf":{"@id":"https:\/\/www.teamdesk.net\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/multi-level-tree\/#primaryimage"},"image":{"@id":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/multi-level-tree\/#primaryimage"},"thumbnailUrl":"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2020\/07\/Multi-Level-Tree-2.png","datePublished":"2020-07-11T17:30:56+00:00","dateModified":"2021-09-28T13:04:57+00:00","author":{"@id":"https:\/\/www.teamdesk.net\/blog\/#\/schema\/person\/63bd8646f2f4720f503116e38a190a6e"},"description":"If a table contains nested records, it means that there is a multi-level tree of related records. In this blogpost we describe how the multi-level tree of related records can be configured. To review the described multi-level tree setup, try the \u201cExample: Multi-Level Tree\u201d template from the database library.","breadcrumb":{"@id":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/multi-level-tree\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.teamdesk.net\/blog\/tips-tricks\/multi-level-tree\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/multi-level-tree\/#primaryimage","url":"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2020\/07\/Multi-Level-Tree-2.png","contentUrl":"https:\/\/www.teamdesk.net\/blog\/wp-content\/uploads\/2020\/07\/Multi-Level-Tree-2.png","width":1034,"height":479,"caption":"Multi-Level tree"},{"@type":"BreadcrumbList","@id":"https:\/\/www.teamdesk.net\/blog\/tips-tricks\/multi-level-tree\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.teamdesk.net\/blog\/"},{"@type":"ListItem","position":2,"name":"Multi-level tree of related records"}]},{"@type":"WebSite","@id":"https:\/\/www.teamdesk.net\/blog\/#website","url":"https:\/\/www.teamdesk.net\/blog\/","name":"TeamDesk Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.teamdesk.net\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.teamdesk.net\/blog\/#\/schema\/person\/63bd8646f2f4720f503116e38a190a6e","name":"Mila","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/939a25c18364af1ceffe1d698a8fd01e1a18d8e1cf906fe3a6ac1cad64bc653f?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/939a25c18364af1ceffe1d698a8fd01e1a18d8e1cf906fe3a6ac1cad64bc653f?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/939a25c18364af1ceffe1d698a8fd01e1a18d8e1cf906fe3a6ac1cad64bc653f?s=96&d=mm&r=g","caption":"Mila"},"url":"https:\/\/www.teamdesk.net\/blog\/author\/mila\/"}]}},"_links":{"self":[{"href":"https:\/\/www.teamdesk.net\/blog\/wp-json\/wp\/v2\/posts\/2140","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.teamdesk.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.teamdesk.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.teamdesk.net\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.teamdesk.net\/blog\/wp-json\/wp\/v2\/comments?post=2140"}],"version-history":[{"count":16,"href":"https:\/\/www.teamdesk.net\/blog\/wp-json\/wp\/v2\/posts\/2140\/revisions"}],"predecessor-version":[{"id":2501,"href":"https:\/\/www.teamdesk.net\/blog\/wp-json\/wp\/v2\/posts\/2140\/revisions\/2501"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.teamdesk.net\/blog\/wp-json\/wp\/v2\/media\/2169"}],"wp:attachment":[{"href":"https:\/\/www.teamdesk.net\/blog\/wp-json\/wp\/v2\/media?parent=2140"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.teamdesk.net\/blog\/wp-json\/wp\/v2\/categories?post=2140"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.teamdesk.net\/blog\/wp-json\/wp\/v2\/tags?post=2140"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}