The current rvm implementation does not support programmatically enabling/disabling a filter from the xml. The filter attribute of a column appears to only evaluate on init. The following does not currently work in 4.83.2.
<object-table label="test" query="data" empty-message="Your items will appear here">
<column filter="$: view.enable_filters" hide-if="$: !view.show_column" heading="Number">{num}</column>
<column filter="true" heading="Integer">{integer}</column>
<column filter="true" heading="Date" display="{date}" />
</object-table>
However, it is possible to control this behaviour with a controlled object-table.
See this post which leads to a comprehensive template app using controlled object tables.
A controlled object table has the ability to provide many performance and customisability benefits, however implementing filtering is not always a trivial affair. I have opened an issue for this bug. Feel free to submit a support ticket so that you can keep track of it’s progress