If you are removing a class you can do that through the DBC script associated with the product.xml, something like the following, which will remove the class from the INVUSELINE .ISSUETO when you run the updatedb.bat / sh.

I did not test this specific script so  you may need to adjust it.

<?xml version="1.0" encoding="UTF-8"?>

<script author="Alexey Potanin" scriptname="V1000_01">

    <description>Add Barcode Printing configurations.</description>

    <statements>     

      <modify_table name="INVUSELINE">

            <attrdef attribute="ISSUETO" classname="" />

        </modify_table>

    </statements>

</script>

If you are removing a class you can do that through the DBC script associated with the product.xml, something like the following, which will remove the class from the INVUSELINE .ISSUETO when you run the updatedb.bat / sh.

I did not test this specific script so  you may need to adjust it.

<?xml version="1.0" encoding="UTF-8"?>

<script author="Alexey Potanin" scriptname="V1000_01">

    <description>Add Barcode Printing configurations.</description>

    <statements>     

      <modify_table name="INVUSELINE">

            <attrdef attribute="ISSUETO" classname="" />

        </modify_table>

    </statements>

</script>

Blatant self-promotion, but if you are interested in using the product.xml and DBC scripts to manage your configurations, you might want to check out the blog I wrote on migrating screen changes with the mxdiff utility.

https://www.sharptree.io/blog/2022/2022-03-29-mxdiff/

The resulting mxs files can be used in the just like DBC scripts, which is pretty cool. 

A project that uses this can be found here.

https://github.com/sharptree/zebra-label

Cheers,

Jason