EASaveRecordsFromQuery

This document was generated using Claude.ai

Overview

Bulk saves entities identified by a SQL query. Extends EARecommitFromQuery but performs entity editing and saving operations instead of simple recommit, triggering full validation and business logic with transaction control.

When This Action Runs

Manual execution for bulk entity saving operations after data modifications, corrections, or when entities need full save processing to trigger business rules and validation.

How It Works

  1. Executes query - Runs the provided SQL query to find entities (must return entityType and id columns)
  2. Processes results - Extracts entity type and ID pairs from query results
  3. Optional pre-update - Runs optional update query after selection but before saving
  4. Starts editing - Calls startEditing() on each entity to prepare for modification
  5. Commits entities - Calls EntityMediator.commitFromBusinessAction() to complete the save
  6. Handles errors - Processes errors based on configuration (continue or stop)

Parameters

Parameter 1: Query (Required) - SQL query returning entityType and id columns

Example Query:

select entityType,id from StockIssue where fromDoc_id = {id} and n1 = 5

Parameter 2: Flush Before Starting (Optional) - true/false to flush database before starting (default: false)

Parameter 3: Do not Save cancelled Records (Optional) - true/false to skip cancelled DocumentFile entities (default: true)

Parameter 4: Flush After Each Save (Optional) - true/false to flush after each entity (default: false)

Parameter 5: Do In New Transaction - Continue on Errors (Optional) - true/false to continue processing if individual entities fail (default: false)

Parameter 6: Run Update Query After Selecting Entities, and Before Save (Optional) - SQL update query to run before saving

Database Tables Affected

  • Query Target Tables - Reads from tables specified in the query
  • Entity Tables - Updates entities through full save operation including validation
  • Related Tables - All tables affected by entity business logic during save
  • Optional Update Tables - Additional update query may affect other tables

Important Warnings

⚠️ Query Requirements

  • Query must return exactly 2 columns: entityType (string) and id (uniqueID)
  • Query should use proper WHERE conditions to avoid unintended mass operations
  • Use {id} placeholder to reference the current entity's ID in the query

⚠️ Save Operation Impact

  • Triggers full entity editing and save cycle including all business logic
  • May cause cascading effects on related entities and calculated fields
  • More comprehensive than simple recommit - includes editing state management

⚠️ Performance Considerations

  • Each entity goes through complete edit/save cycle which is more intensive than recommit
  • Database flushing options add additional overhead
  • Consider transaction settings for large operations

⚠️ Business Logic Impact

  • Save operations trigger all entity flows, validation rules, and business logic
  • Can modify calculated fields, accounting effects, and status updates
  • May affect entity relationships and dependent calculations

⚠️ Error Handling

  • Default behavior stops on first error unless "Continue on Errors" is enabled
  • Failed entities may leave incomplete save state
  • Monitor carefully when processing large numbers of entities

Module: core

Full Class Name: com.namasoft.infor.domainbase.util.actions.EASaveRecordsFromQuery

Related Actions: