Setting nodeId in data.nodeId of read action

[Sean Hamilton]

The API returns the nodeId and parentID correctly when requested:

        {

            "name": "A",

            "size": 8,

            "dateModified": "Wed May 29 09:53:19 GMT 2019",

            "dateCreated": "Wed May 29 09:53:19 GMT 2019",

            "hasChild": false,

            "nodeId": "8",

            "parentID": "-1",

            "type": "",

            "filterPath": "",

            "file": false,

            "isFile": false

        },

        {

            "name": "C",

            "size": 9,

            "dateModified": "Wed May 29 09:53:19 GMT 2019",

            "dateCreated": "Wed May 29 09:53:19 GMT 2019",

            "hasChild": false,

            "nodeId": "9",

            "parentID": "-1",

            "type": "",

            "filterPath": "",

            "file": false,

            "isFile": false

        },

        {

            "name": "F",

            "size": 10,

            "dateModified": "Wed May 29 09:53:19 GMT 2019",

            "dateCreated": "Wed May 29 09:53:19 GMT 2019",

            "hasChild": false,

            "nodeId": "10",

            "parentID": "-1",

            "type": "",

            "filterPath": "",

            "file": false,

            "isFile": false

        }

But when requesting, for example the folder called A the request generated is:

{  
   "action":"Read",
   "path":"/A/",
   "showHiddenItems":false,
   "data":[  
      {  
         "name":"A",
         "size":8,
         "dateModified":"2019-05-29T09:53:59.000Z",
         "dateCreated":"2019-05-29T09:53:59.000Z",
         "hasChild":false,
         "nodeId":"fe_tree_0_2",
         "parentID":"-1",
         "type":"",
         "filterPath":"",
         "file":false,
         "isFile":false,
         "iconClass":"e-fe-folder",
         "icon":"e-fe-folder",
         "htmlAttributes":{  
            "class":"e-large-icon",
            "title":"A"
         }
      }
   ]
}

All the other properties can be correctly set, only nodeId cannot. 

Thanks.

[Christopher Issac Sunder K]

Hi Sean, 

Greetings from Syncfusion support. 

We checked your reported query - “Not able to set nodeId in the FileManager’s read request“. The reason for this issue is that we have used the nodeId as an internal variable and we have processed the treeview by using nodeId as its id. So, even if the nodeId value is set initially in the read request it will be overridden in the source side. We will change the names of the internal variables used in the request so that it will be possible to modify the requested data without being overridden. We will make these changes and include them in our upcoming 2019 Vol 2 Main Release which is expected to be released in the month of June, 2019 You can track the status of this through the below feedback portal link, 

https://www.syncfusion.com/feedback/6610/provide-separate-variable-in-file-managers-ajax-requests-for-local-data-utilized-in-the-source 

However, for now, you can resolve this issue by changing the id name(nodeId) passed in the read request which will be added to it. 

Let us know if you have any concerns 

Thanks,
Christo 

[Sean Hamilton]

Thank you, setting custom id names has solved the issue.

[Keerthana Rajendran]

Hi Sean,  

 

We are glad to know that the provided suggestion helped you to resolve the issue. Please get back to us if you need further assistance on this.  

 

Regards, 

Keerthana.