You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Server Version: 2.36.3
CLI Version (for CLI related issue):
Environment
Community
What is the current behaviour?
Computed Fields when used in the Post Update check does not reflect the updated value as per the updated row.
Scenario:
Need to limit the total number of rows in a table where status is active.
Upon updating a row for Inactive to Active, using a post update check where count of Active <= 5, allow the row to be updated even if the existing count of Active is 5.
What is the expected behaviour?
Upon updating a row for Inactive to Active, using a post update check where count of Active <= 5, should disallow the row to be updated since the existing count of Active is 5.
Need for post update check is the fact that any row with Active status should be allowed for non status field updates but a new row with previous status != Active to status Active need to be blocked.
How to reproduce the issue?
create a table with two fields, status and comment.
2.
add 2 rows to table with one status = Active, other with status = Inactive
3.
create a computed field in the table to get the count of total active rows in the table
4.
create a post update check with computed field <= 1
5.
update row where status = Inactive to status = Active.
This allows the update to go through successfully
Screenshots or Screencast
Please provide any traces or logs that could help here.
Any possible solutions/workarounds you're aware of?
None
Keywords
Computed Fields, Post Update Check
The text was updated successfully, but these errors were encountered:
Version Information
Server Version: 2.36.3
CLI Version (for CLI related issue):
Environment
Community
What is the current behaviour?
Computed Fields when used in the Post Update check does not reflect the updated value as per the updated row.
Scenario:
Need to limit the total number of rows in a table where status is active.
Upon updating a row for Inactive to Active, using a post update check where count of Active <= 5, allow the row to be updated even if the existing count of Active is 5.
What is the expected behaviour?
Upon updating a row for Inactive to Active, using a post update check where count of Active <= 5, should disallow the row to be updated since the existing count of Active is 5.
Need for post update check is the fact that any row with Active status should be allowed for non status field updates but a new row with previous status != Active to status Active need to be blocked.
How to reproduce the issue?
create a table with two fields, status and comment.
2.
add 2 rows to table with one status = Active, other with status = Inactive
3.
create a computed field in the table to get the count of total active rows in the table
4.
create a post update check with computed field <= 1
5.
update row where status = Inactive to status = Active.
This allows the update to go through successfully
Screenshots or Screencast
Please provide any traces or logs that could help here.
Any possible solutions/workarounds you're aware of?
None
Keywords
Computed Fields, Post Update Check
The text was updated successfully, but these errors were encountered: