[ANGULAR] Tree Structure in Scheduler Pro

[valereimann]

I ran into one problem, while implementing the Scheduler Pro.
I want to use the Tree Feature. What I did:

<bryntum-scheduler-pro
  #schedulerpro
  [columns] = "schedulerProConfig.columns!"
  [startDate] = "schedulerProConfig.startDate!"
  [endDate] = "schedulerProConfig.endDate!"
  [height]= "schedulerProConfig.height"
  [project] = "project"
  [features] = 'schedulerProConfig.features'
  [treeFeature]= 'schedulerProConfig.features.tree'
</bryntum-scheduler-pro>

---

<bryntum-scheduler-pro-project-model
  #project
  [resources]="this.data"
</bryntum-scheduler-pro-project-model> 

---

features: {
    tree: true,
  },
  columns : [
    {
      type: 'tree', field: 'name', text: 'Name', width: 300, sortable: false, readOnly: true,
    }...

-------------------------------------------------

 const store = new Store({
        tree              : true,
        transformFlatData : true,
        data: relevantObj})

-------------------------------------------------
I'm using a flat data set, that definitly works, because I'm using the same Data with the Bryntum Grid. But It just shows me the Data without giving a tree structure or any order in Scheduler.

Could you please help me?
Best Regards

[Animal]

The leaf nodes have a parentId field do they so that we know how to build the tree structure from the flat data?

[valereimann]

The Objects (from the backend) have a parentId:

{
  "id": 2200854400,
  "parentId": 2200852600,
  "name": "Low",
  "type": "VV",
  "launchStart": 1688166000000,
  "versionNo": 1,
  "state": "CONCEPT_CHECK"
}

I don't think that the Objects are the problem, because the exact same data works in Bryntum Grid as a Tree

[mats]

We could not reproduce this issue. To assist you with your question, please provide more details including a runnable test case (as described in our support guidelines).

To get the fastest possible support, provide a simple test case based on our standard examples.

[valereimann]

I attached the Config, ts and html File.

[valereimann]

This is Sample Data from the Backend:

[valereimann]

I solved it myself:

In the html I should have had:

[resourceStore]="resourceStore"

, not just the Data without including the Store. Because the tree attribute is stored in the Store not in the Data of the Store.

What I basically had before:

[resources]="resourceStore.data"

[tasnim]

Glad to hear that you've got it fixed.

If you have any other questions or concerns, please don't hesitate to reach out.

Good Luck