Differences

This shows you the differences between two versions of the page.

--- newdevs:code:save-grid-settings [2025/06/12 13:23] – tmccanna
+++ newdevs:code:save-grid-settings [2025/06/12 13:31] (current) – [Determine the Setting Name] tmccanna
@@ Line 7: / Line 7: @@
 ===== Make the Save Grid Settings Option Visible =====
-If the Save Grid Settings option doesn't appear at all, it likely needs to have a persistKey assigned.
+If the Save Grid Settings option doesn't appear at all, it likely needs to have a persistKey assigned to the grid.
-<eg-grid #grid idlClass="asv" [dataSource]="gridDataSource" persistKey="admin.local.survey"
+<code>
-[sortable]="true">
+<eg-grid #partsGrid idlClass="bmp" [dataSource]="gridDataSource" [sortable]="true"
+    persistKey="catalog.record.parts"
+    hideFields="label_sortkey,deleted,record"
+    class="mt-3">
+</code>
 ===== Determine the Setting Name =====
-An easy way to determine what the missing setting should be called, check your browser console for the error that appears when you click on Save Grid Settings. It should say something like:
+As above, you can identify the persistKey in the code to determine what the name of the new setting should be.
-Error saving columns: No user or workstation setting type exists for: "eg.grid.catalog.record.parts".
+You can also tell via the browser console. The error you see when clicking on Save Grid Settings should should say something like:
+<code>
+Error saving columns: No user or workstation setting type
+exists for: "eg.grid.catalog.record.parts".
+</code>