Versions Compared

Old Version 7

changes.mady.by.user Dmitry Donosiyan

Saved on

compared with

New Version 8

changes.mady.by.user Dmitry Donosiyan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Flag NameDescription
noLoadValidationFlag

Turns off the following checks for SMF:

Code Block
languagesql
<EDITCHECK EXPR="!(StringLength( :tag3931: )=0) OR (|noLoadValidationFlag|='Y' or :noLoadValidationFlag:='Y')" TAG="3931" ERRORMESSAGE="PROCESSING SECURITY TYPE IS REQUIRED" />
<EDITCHECK EXPR="!(StringLength( :tag11: )=0) OR (|noLoadValidationFlag|='Y' or :noLoadValidationFlag:='Y')" TAG="11" ERRORMESSAGE="INVESTMENT TYPE IS REQUIRED" />
<EDITCHECK EXPR="!(StringLength( :tag85: )=0 AND :tag3931: != 'FWXXXX') OR (|noLoadValidationFlag|='Y' or :noLoadValidationFlag:='Y')" TAG="85" ERRORMESSAGE="ASSET CURRENCY IS NULL" />
<EDITCHECK EXPR="StringLength( :tag1432: )!=0 OR (|noLoadValidationFlag|='Y' or :noLoadValidationFlag:='Y')" TAG="1432" ERRORMESSAGE="PRIMARY ASSET TYPE IS NULL" />
<EDITCHECK EXPR="StringLength( :tag961: )!=0 OR (|noLoadValidationFlag|='Y' or :noLoadValidationFlag:='Y')" TAG="961" ERRORMESSAGE="ISSUE NAME IS NULL" />


preserveNullThis parameter is linked with tag5284, which nulls DB fields during the process of update. For example, you have 10 fields populated in the table for a record. You send a file to update it with only 7 fields and preserveNull flag set to Y - as a result, 7 fields will be updated, 3 fields will be nulled. If the flag is set to N, only these 7 fields will be updated, the other 3 fields will be left unchanged
tagNochangecaseOriginates from panels, defines for which incoming tags case should not be changed
historyOnlyFlagToggles updating data in the composite table. Insert will always be performed, update can be switched off
accountingValidationFlag

When set to Y, enables load thru panel for the data file. 

There are times when we do not need it because the validation has been embedded in Eagle ML itself (SMF reference), or it is not applicable / appropriate (load variable rates) or there are times when it is valuable to do so (add entity)

The simple way to view the accountingValidationFlag is that it is used to route the messages to use the core panels which triggers the application of the panel logic and error handling. This mimics the user functionality and experience. Using the panels, it shows the missing required flags and provides a direction for debugging if there are errors.

When the flag is not passed, it attempts to do a direct insert into the database and it bypasses the logic. It is frequently used by our data management clients who do not require the same level of accounting checks.

For loading in accounting transactions, you should be using the accountingValidationFlag setting it to Y.

Code Block
languagexml
<accountingValidationFlag>Y</accountingValidationFlag>

accountingValidationFlag= N or null:
It does a direct load and missing data points necessary for accounting.

accountingValidationFlag=Y:
Additional accounting-related elements will be necessary to get a successful message. However, this flag is necessary for setting up messages that are intended to utilize Eagle’s accounting functionality.