Skip-list when calling SAVE-ROW-CHANGE only relevant when creating records Cancel The title field is required!

1. Patrik Wikström

   

   70 posts
   Registered:
   15 Oct 2018
   03 Oct

   Link to this post

   This is a general Progress question, is the skip-list only relevant when creating records, not when updating?
2. Mike Fechner

   

   342 posts
   Registered:
   14 Sep 2016
   Answered

   03 Oct in reply to Patrik Wikström

   Link to this post

   Progress documentation is your friend:
   
   https://documentation.progress.com/output/ua/OpenEdge_latest/pdsoe/PLUGINS_ROOT/com.openedge.pdt.langref.help/rfi1424919982909.html#:~:text=Saves%20changes%20from%20one%20row,to%20the%20associated%20data%20source.
   
   skip-list
   
   An optional character expression that evaluates to a comma-separated list of field names for fields that should not be assigned after a new row is created (that is, fields to skip). For example, a key field or other fields assigned a value by a CREATE database trigger.
   
   
   
   If you think about it, it's not needed on updates - as the write trigger fires after SAVE-ROW-CHANGES.
3. Patrik Wikström

   

   70 posts
   Registered:
   15 Oct 2018
   04 Oct in reply to Mike Fechner

   Link to this post

   We thought it would prevent the updates of our Key-fields also...but we were sadly wrong...
   EDIT: Maybe the thought has been that there still has to be some way to update even those fields, that's probably the explanation why it was made this way...
   Maybe there would be a need for a separate skip-list for update?

   Last modified on 04 Oct 2024 05:10 by Patrik Wikström
4. Mike Fechner

   

   342 posts
   Registered:
   14 Sep 2016
   04 Oct in reply to Patrik Wikström

   Link to this post

   You can always use our ReadOnly Validate/VlidationHelper method.
   
   If you want to generalize this, this would be a very quick implementation in you override class to DataAccess, either in an override to SaveData or SaveRowChanges.