Symptoms

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 billing.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'

Cause

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.

Resolution

  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">
          <elements>
                <input type="INT"  id="CustomerClassClassID" label="Class ID" required="yes" title="ID of the Customer Class. " value="0"/>
          </elements>
    </window>
    

    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">
          <elements>
                  <input id="CustomerClassClassID" value="0"/>
          </elements>
    </window>
    
  2. Restart www for changes to apply.
  3. Check the billing.www.log to verify that the warning does not appear.

Internal content