Skip to main content
  • EN

So, in the "List" table, I have, as far as I've seen, some duplicate entries. For example, in this image, rows with ID 2404 and 2405 are duplicates of IDs 1 and 2. I believe I have duplicate entries for all lists like that. Could someone help with how to solve this, or rather, how to delete duplicate entries?

xIn the "RecordBoundaries" table, I must not have records with the same ID. I should do the following only for duplicate IDs because they belong to the same document: for example, let ID_Record 357 be one record, and the "creation date" is always an older date (January 1, 1861), while for the "confirmation date," the attribute from the duplicate record should be used (January 1, 1863). So, the process should be done only for duplicate IDs because there must be one record each for themselves.

yP.S. I have attached both files, "Popis" and "ZapisnikOmedjivanja," so you can immediately try with them and send back the edited files to me.

Best regards.

@geomancer​  Hello, just so you can see the question more quickly, if you know, I would be glad if you could help.

Hi, I think in both cases you need a DuplicateFilter. You will probably want to put a Sorter before it to make sure the features you want to keep enter first (especially for the "RecordBoundaries" table). Something like this:

image

Can you send me your .fmw file? I got a difference in the number of data after applying the model.

I am not certain I used the right attributes to filter on, so that may be the reason you get other results.

Also note the attribute Datum izrade in this case did not contain a real date, but always '1.1.year', so it could be sorted by alphabet in descending order to keep the most recent date.

 

Yes, I understand. The model is good, everything is fine. I've looked closely now, and the only thing we haven't done is specify that from those duplicates in table "ZapisnikOmedjivanja", we need to put the creation year into the confirmation year (for example, for number 357, I should have 1.1.1861 - 1.1.1863). Do you have any ideas just for that?

That calls for a different approach. I would use a list for this.

In this setup features with a ID_Zapisnik that occurs only once are also processed. You can filter them out afterwards if you want to.

image 

Thanks!

Reply


Community Stats

30,162
Posts
114,482
Replies
37,809
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.