PERSIST_COLUMN_LOCKMODES:String="columnLockModes": The lock modes of the column - left, right or unlocked. PERSIST_COLUMN_VISIBILITY:String="columnVisiblity" : Whether or not the column is hidden. PERSIST_COLUMN_WIDTH:String="columnWidth": The width of the columns. PERSIST_FILTER:String="filter": The filter values that the user currently has entered into the filter controls. PERSIST_SORT:String="sort" : The sort settings. PERSIST_VERTICAL_SCROLL:String="verticalScroll": The vertical scroll position of the grid. PERSIST_HORIZONTAL_SCROLL:String="horizontalScroll": The horizontal scroll position of the grid. PERSIST_FOOTER_FILTER_VISIBILITY:String="footerFilterVisiblity" : Whether or not the user has chosen to show or hide the footer and filter bars. PERSIST_PAGE_SIZE:String="pageSize" : The page size that the user has chosen. PERSIST_PRINT_SETTINGS:String="printSettings": Print settings, currently not applicable for HTML version of grid. Built in features If you set enablePreferences=true, you see the following icons in the grid: These are the settings and save settings pop-ups. When you click on the Settings Popup button, you see the below popup. When you click on the Save Settings Popup button, you see the following window: Together, these two windows allow you to configure the grid, as well as save the state of the grid. With client preferences, these are stored in local storage on the browser. For server based preference persistence, please refer to the next chapter. Persisting Preferences on the Server When you save preferences, where are the preferences persisted to?? The grid has a robust persistence preference mechanism that "just works" out of the box, but the preferences are stored on the client machine's localstorage by default. This enables the preference persistence mechanism to work without any additional coding on the part of the developers utilizing the library. While this may be sufficient for most people, this will not work in scenarios when the same user uses multiple machines to access your application, or if multiple users access the application using the same machine. For this, you will need to store preferences in the backend, and this post aims to show you how this is done. Attached is a simple example
PERSIST_COLUMN_LOCKMODES:String="columnLockModes": The lock modes of the column - left, right or unlocked. PERSIST_COLUMN_VISIBILITY:String="columnVisiblity" : Whether or not the column is hidden. PERSIST_COLUMN_WIDTH:String="columnWidth": The width of the columns. PERSIST_FILTER:String="filter": The filter values that the user currently has entered into the filter controls. PERSIST_SORT:String="sort" : The sort settings. PERSIST_VERTICAL_SCROLL:String="verticalScroll": The vertical scroll position of the grid. PERSIST_HORIZONTAL_SCROLL:String="horizontalScroll": The horizontal scroll position of the grid. PERSIST_FOOTER_FILTER_VISIBILITY:String="footerFilterVisiblity" : Whether or not the user has chosen to show or hide the footer and filter bars. PERSIST_PAGE_SIZE:String="pageSize" : The page size that the user has chosen. PERSIST_PRINT_SETTINGS:String="printSettings": Print settings, currently not applicable for HTML version of grid. Built in features If you set enablePreferences=true, you see the following icons in the grid: These are the settings and save settings pop-ups. When you click on the Settings Popup button, you see the below popup. When you click on the Save Settings Popup button, you see the following window: Together, these two windows allow you to configure the grid, as well as save the state of the grid. With client preferences, these are stored in local storage on the browser. For server based preference persistence, please refer to the next chapter. Persisting Preferences on the Server When you save preferences, where are the preferences persisted to?? The grid has a robust persistence preference mechanism that "just works" out of the box, but the preferences are stored on the client machine's localstorage by default. This enables the preference persistence mechanism to work without any additional coding on the part of the developers utilizing the library. While this may be sufficient for most people, this will not work in scenarios when the same user uses multiple machines to access your application, or if multiple users access the application using the same machine. For this, you will need to store preferences in the backend, and this post aims to show you how this is done. Attached is a simple example
Flexicious%20HTMLTreeGrid.docx