Troubleshooting
Problem
Setting HasHistory attribute to True/False causes generateTruncateTransactionData.xml to fail
Symptom
1. The MCF/MCSF 8.x Customization Guide (or Extending the Database Guide as of SFS 9.0) states that the HasHistory attribute, used when extending the database with a custom or hang-off table, should use the values "True" or "False".
2. Using True or False works fine as advertised. In fact, using
"Y" or "N" also works with the HasHistory attribute. The problem is, the
generateTruncateTransactionData.xml script ONLY recognizes Y/N for the
HasHistory attribute.
3. But since the HasHistory attribute is
documented to only recognize True/False, if a customer uses only True/False,
then the generateTruncateTransactionData.xml will fail to properly generate the
transaction data truncation lists.
N/A. No resulting transaction data trunction lists are produced.
Resolving The Problem
The MCF/MCSF 8.x Customization Guide (or Extending the Database Guide as of SFS 9.0) should be changed to indicate that the valid values for the HasHistory attribute are Y/N instead of True/False. Then, generateTruncateTransactionData.xml script would properly produce transaction data truncation lists without any changes to it.
Historical Number
NFX9418
Product Synonym
[<p><b>]Function Area[</b><p>];Extending the Database;Truncation List generator;[<p><b>]Escalation ID[</b><p>];154773;[<p><b>]Severity[</b><p>];Normal;[<p><b>]Type[</b><p>];NormalFix
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21553658