Subtables are a great tool, but there are some nuances to their configuration and use. I wanted to share some things I have run across recently that initially loooked like bugs, but turned out to be configurations I could resolve on my own!
Deleting Subtable Records in Logic? Use “Delete Subtable Record,” Not a Regular Delete
If you are writing logic that deletes a subtable record, use the subtable delete action, not the regular delete action. Using the regular delete can cause the parent record and subtable to get out of sync mid-commit, resulting in unexpected errors on save.
The fix: Use the Delete Subtable Record action instead. This ensures the delete is handled in the right order and the parent record stays consistent through the commit process.
Can’t see the field action you configured on your subtable? Check Your Security Group
If you have configured a field action on a subtable field and it is not showing up, check your security. You need to make sure you have a permission that gives logic block access to the security group assigned to your logic block. When testing, make sure you are using a role that has this permission assigned. If that access is not granted, the field action will not display in the application.
The fix: Make sure you are using a permission where logic block access has been granted to the security group assigned to your logic block.
Hopefully, this informations save you some time and unblocks you before you spend time logging a bug!