actually I've tryed many ways of doing that, including calculating a field with values 0 / 1 , and defining a filter over these values.
that way was the closest I got to a working model, but when the file was reopened (through a xprj) I ended with a empty table...
but it gets stranger...
on the sequence I set to no filter, then I can see all registers as expected.
Then, I reselect the filter ( that has just resulted in a empty table... ) and I have the correctly filtered registers only...
Can it be any configuration problem?
tks for the help
I've found a solution for my problem, i think it can help the others.
when editing the filter for the version 9.01 of monarch, there are 3 tabs:
formula / advanced / test
on the formula tab I did no modifications to the existing filter that is causing problem
on the advanced tab you do the following
-select the option:
'select rows according to their uniqueness with respect to the specified keys'
-then check only the option:
-in the Duplicated rows select:
'all duplicated rows'
in the combo list in the right side, there is a list of fields that exists on the model called:
Here is the trick, you now have to select a field in the list where every value is the same for all register.
In my case I've choosen the 'Data' field that for my table was constant in every row
(sugestions for this step, create a calculated field with a constant value and use it!)
Now I have a perfect functional filter that accepts modifications and behave as expected
I hope I can help somebody
That's a really handy trick - it's not expected behaviour from Monarch, but it's nice to have found a workaround. Applying a "dummy" duplicate handling rule seems to force Monarch to think about the filter properly. Please could you confirm that this is for a filter applied to a database import or external lookup, as opposed to a normal filter within a table?