Search Engine: Elastic

Article ID: 118127, created on Oct 23, 2013, last review on Jul 14, 2018

  • Applies to:
  • Business Automation 5.5
  • Business Automation 6.0


There is a customization of some specific window, it works as expected, but when accessing a customized screen, warning about code redundancy appear in the www.log, for example:

[13-10-17 09:40:37.173 Parser RQ35828 WRN] Redundant code. Trying to customize existing element <id=TaxZoneIDTaxZoneID> with label_='Tax Zone ID'


In the customization files created there is a redundant code (a code which is the same as in the initial file). According to the documentation: all elements and their attributes that are not used in customization must be removed.


  1. Remove the redundant code from the customization file created.

    To determine redundant code, compare you customization file with the initial file, which is usually in /usr/local/bm/conf/wnd/<CONT_NAME>/<window_name>.xml or in /usr/local/bm/conf/wnd/<CONT_NAME>/customization/<window_name>.xml. If the same property is present in one of these system files and is also present in your customization file, it means it is redundant.

    For example, there is a customization file:

    <window id="Account_AddCustomerWin">
                <input type="INT"  id="CustomerClassClassID" label="Class ID" required="yes" title="ID of the Customer Class. " value="0"/>

    In the initial /usr/local/bm/conf/wnd/BM/Account_AddCustomerWin.xml we see

    <input type="INT" src="refCustomerClass, 0, 1"  id="CustomerClassClassID" label="Class ID" required="yes" title="ID of the Customer Class. "/>

    type, label, required, title are examples of redundant code in the manually created customization file. The id="CustomerClassClassID" is not redundant - by id we specify a place to be customizaed. The correct customization , without redundant code will look like:

    <window id="Account_AddCustomerWin">
                  <input id="CustomerClassClassID" value="0"/>
  2. Restart www for changes to apply.
  3. Check the www.log to verify that the warning does not appear.

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 801221f8cd76fba7300d1e6817c8e08b 92711db0799e8aefe8e51f12dace0496 e12cea1d47a3125d335d68e6d4e15e07 3627d36199b8ff577605df76e2fa222b bb7e9177fb03488961a3ea554120f328

Email subscription for changes to this article
Save as PDF