Skip to main content
Question

Migrating overwritten entity read-trigger

  • April 22, 2026
  • 2 replies
  • 11 views

Roger Wallin
Forum|alt.badge.img+3

Hi
Now I’m on thin ice.
I have a Uniface9 service (self-contained) that has changed an entity's read trigger, i.e. what is in the data model's read trigger is overwritten in the form.
When exporting and importing to Uniface 10.04.3_038, that what is in the entity's read trigger is still used. Is this correct?

Does it have something to do with this?
; Migration Logical: Specify whether precompiler directives are generated to prevent 
; triggers and entries from being inherited in selected cases. 
    ; 0 = do not generate 
    ; 1 = generate precompiler directives (default)
MIGRATION_SCRIPT_V9_INHERITANCE = 1

Regards RogerW

2 replies

Juliano Anoar Haoach Garcia
Forum|alt.badge.img+1

It hasn’t changed — the behavior is still the same. If you have overridden the trigger in the component, the component’s trigger will take precedence.


Juliano Anoar Haoach Garcia
Forum|alt.badge.img+1

These are the migration parameters we are using:

; Migration Logical: Specify whether precompiler directives are generated to prevent
; triggers and entries from being inherited in selected cases.
; 0 = do not generate
; 1 = generate precompiler directives (default)
MIGRATION_SCRIPT_V9_INHERITANCE = 1

; Migration Logical: Enable or disable addition of a comment at the beginning and end of each
; migrated ProcScript module with Uniface 9 trigger name.
; 0 = disable (default)
; 1 = enable
MIGRATION_SCRIPT_ADD_INFO = 0

; Migration Logical: Enable or disable addition of an 'end' statement to migrated ProcScript modules.
; 0 = disable
; 1 = enable (default)
MIGRATION_SCRIPT_ADD_END = 0

; Migration Logical: Specify whether non-functional code is migrated for components.
; 0 = non-functional code is migrated
; 1 = non-functional code is removed from normal components only
; 2 = non-functional code is removed from all components (default)
MIGRATION_SCRIPT_CLEANUP_COMPONENTS = 2

; Migration Logical: Specify whether the <$triggerAbbr> constant is defined at
; the start of migrated non-empty triggers.
; 0 = <$triggerAbbr> is never defined
; 1 = <$triggerAbbr> is always defined
; 2 = <$triggerAbbr> is defined if the keywords <$triggerAbbr> and #include are found (default)
MIGRATION_TRIGGERABBR = 1

; Migration Logical: Specify whether a constant scope block (#startdefine and #enddefine) is added
; to a migrated, non-empty trigger definition, and to each group of migrated operations.
; 0 = do not add
; 1 = add for all triggers and operation groups
; 2 = add when the trigger contains #define or #include or <$triggerAbbr> keywords (default)
MIGRATION_SCOPEDEFINE = 1

; Migration Logical: Specify whether internally-defined constant mappings that were used to bind data in
; Uniface 9 are migrated to the Declarations container of the derived component.
; 0 = migrate internally-defined constant mappings (default)
; 1 = remove internally-defined constant mappings
MIGRATION_REMOVE_MAPPING_DERIVED_COMPONENTS = 0