You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| `IsDirectory` | Whether the item is a directory. If its value is `false` the item is considered a file and not a directory.
241
-
| `DateCreated` | The creation date of the file.
242
-
| `DateCreateUtc` | The creation date of the file in UTC. Required.
243
-
| `DateModified` | The modification date of the file.
244
-
| `DateModifiedUtc` | The modification date of the file in UTC. Required.
236
+
|`Name`| The name of the file.|
237
+
|`Size`| The size of the file.|
238
+
|`Path`| The path of the file.|
239
+
|`Extension`| The extension of the file.|
240
+
|`IsDirectory`| Whether the item is a directory. If its value is `false` the item is considered a file and not a directory.|
241
+
|`DateCreated`| The creation date of the file.|
242
+
|`DateCreateUtc`| The creation date of the file in UTC. Required.|
243
+
|`DateModified`| The modification date of the file.|
244
+
|`DateModifiedUtc`| The modification date of the file in UTC. Required.|
245
245
|**Item relations**||
246
-
| `Id `| The unique identifier of the file. Required for [**binding to flat data**](slug:filemanager-data-binding-flat-data).
247
-
| `ParentId` | Identifies the file's parent. Required for [**binding to flat data**](slug:filemanager-data-binding-flat-data). Set to `null` for root items. Do *not* use `ParentId` with hierarchical data.
248
-
| `HasDirectories` | Determines whether the item has subdirectories. Required for binding to [**flat data**](slug:filemanager-data-binding-flat-data) If `true`, the directory will show an expand arrow. With [**hierarchical data**](slug:filemanager-data-binding-hierarchical-data), the FileManager renders expand icons based on `Directories`, but `HasDirectories` will take precedence.
246
+
|`Id `| The unique identifier of the file. Required for [**binding to flat data**](slug:filemanager-data-binding-flat-data).|
247
+
|`ParentId`| Identifies the file's parent. Required for [**binding to flat data**](slug:filemanager-data-binding-flat-data). Set to `null` for root items. Do *not* use `ParentId` with hierarchical data.|
248
+
|`HasDirectories`| Determines whether the item has subdirectories. Required for binding to [**flat data**](slug:filemanager-data-binding-flat-data) If `true`, the directory will show an expand arrow. With [**hierarchical data**](slug:filemanager-data-binding-hierarchical-data), the FileManager renders expand icons based on `Directories`, but `HasDirectories` will take precedence.|
249
249
| `Directories` | Defines the item subdirectories. Required for [binding to **hierarchical data**](slug:filemanager-data-binding-hierarchical-data).
250
-
| `Items` | Defines all the subitems (directories and files) of the item.
250
+
|`Items`| Defines all the subitems (directories and files) of the item.|
251
251
252
252
## Data Bindings
253
253
254
254
All [FileManager item features](#fileManager-item-features) map to model properties. The properties of a treeview item match directly to a field of the model the treeview is bound to. You provide that relationship by providing the name of the field from which the corresponding information is to be taken. To do this, in the main `TelerikFileManager` tag, use the parameters described below:
255
255
256
-
| FileManager Parameter |DEFAULT VALUE|
257
-
|----------|----------|----------|
256
+
| FileManager Parameter |Default Value|
257
+
|---|---|
258
258
|**Item features**||
259
-
| `NameField`| `"Name"`
260
-
| `SizeField`| `"Size"`
261
-
| `PathField`| `"Path"`
262
-
| `ExtensionField`| `"Extension"`
263
-
| `IsDirectoryField`| `"IsDirectoryField"`
264
-
| `DateCreatedField`| `"DateCreated"`
265
-
| `DateCreateUtcField`| `"DateCreateUtc"`
266
-
| `DateModifiedField`| `"DateModified"`
267
-
| `DateModifiedUtcField`| `"DateModifiedUtc"`
268
-
|**Item relations**|||**Item relations**||
269
-
| `IdField `| `"Id" `
270
-
| `ParentIdField`| `"ParentId"`
271
-
| `HasDirectoriesField`| `"HasDirectories"`
272
-
| `DirectoriesField`| `"Directories"`
273
-
| `EntriesField`| `"Entries"`
259
+
|`NameField`|`"Name"`|
260
+
|`SizeField`|`"Size"`|
261
+
|`PathField`|`"Path"`|
262
+
|`ExtensionField`|`"Extension"`|
263
+
|`IsDirectoryField`|`"IsDirectoryField"`|
264
+
|`DateCreatedField`|`"DateCreated"`|
265
+
|`DateCreateUtcField`|`"DateCreateUtc"`|
266
+
|`DateModifiedField`|`"DateModified"`|
267
+
|`DateModifiedUtcField`|`"DateModifiedUtc"`|
268
+
|**Item relations**||
269
+
|`IdField `|`"Id" `|
270
+
|`ParentIdField`|`"ParentId"`|
271
+
|`HasDirectoriesField`|`"HasDirectories"`|
272
+
|`DirectoriesField`|`"Directories"`|
273
+
|`EntriesField`|`"Entries"`|
274
274
275
275
>important Do not use `ParentId` with hierarchical data. This will confuse the FileManager that it is bound to flat data and the component may not render any items. If the model must have a `ParentId` property, set `ParentIdField` to a non-existent property.
0 commit comments