Differences

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

--- newdevs:code:save-grid-settings [2025/05/19 13:00] – created tmccanna
+++ newdevs:code:save-grid-settings [2025/06/12 13:31] (current) – [Determine the Setting Name] tmccanna
@@ Line 5: / Line 5: @@
 https://bugs.launchpad.net/evergreen/+bug/1975852
-===== Update Open-ILS/src/sql/Pg/950.data.seed-values.sql =====
+===== 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 to the grid.
+<code>
+<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 =====
+As above, you can identify the persistKey in the code to determine what the name of the new setting should be.
+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>
+===== Create Seed Data for New Installs =====
+Update file: Open-ILS/src/sql/Pg/950.data.seed-values.sql
 <code>
@@ Line 18: / Line 46: @@
 );
 </code>
+===== Create Upgrade Script for Existing Installs =====
+New file: Open-ILS/src/sql/Pg/upgrade/XXXX.data.monograph_parts_grid.sql
+Don't worry about trying to predict what the next sequential script number will be, just use "XXXX" and the core committer will update it at commit time.
+<code>
+BEGIN;
+-- SELECT evergreen.upgrade_deps_block_check('XXXX', :eg_version);
+INSERT into config.workstation_setting_type (name, grp, datatype, label)
+VALUES (
+    'eg.grid.catalog.record.parts', 'gui', 'object',
+    oils_i18n_gettext(
+        'eg.grid.catalog.record.parts',
+        'Grid Config: catalog.record.parts',
+        'cwst', 'label'
+       )
+);
+COMMIT;
+</code>