At present, when Use Code String Completion is enabled, the system applies the predefined code string completion rules in sequence and overrides any conflicting values provided in the external file. Conversely, when Use Code String Completion is disabled, the system fully relies on the values in the external file.
Currently, there is no functionality that allows both approaches to work together—i.e., using file provided values where available while applying code string completion for missing parts.
Therefore its important to have the below functionality:
-
When a code part value is provided in the external file, it should take precedence over the default value defined by code string completion.
-
If a code part is omitted from the file, the system should automatically fetch the default value from the code string completion rules.
When a business processes thousands of voucher rows every month, with varying code part values, manually resolving each conflict in such high volumes is impractical and inefficient, making an automated combined approach essential to maintain accuracy and streamline operations.