I did test what you where saying with the setting for Submitted already there. Which does add a primary fact for all those ordinances marked that way. When you add a new ordinances fact it will mark the new one sent over to RM as primary. That is why it's displaying in the view. Except, for the sealing to parent, the old submitted one is still left primary. I have noted that behavior in our tracking system, so it is consistent.
On the Edit Person screen you will now have two facts for every ordinances. One with the status Submitted and the other with the actual date. RootsMagic through the FT API will never write over or replace ordinances you already have in the database. There just isn't a smooth way for us to do that, especially with multiple sets of parents and spouses. We can only add a new fact.
I personally don't use the old statuses any more for that very reason. I don't want to delete 6 different ordinances afterwards. What I did instead was created a custom fact called FSFT and in the description field I mark what I have done with those ordinances using a system of codes I made up. In the notes I record who has a card, etc. I started to use the date field now that we have a two year limit on reservations. This way I can customize the People View and have the FSFT date field showing, then sort to see who's work I need to hurry and get done. I can also create groups based on "codes" I have on my FSFT fact, In the People View I can display just those people. On the FamilySearch Person Tools sidebar index the top level filter can be set to those groups too. It's a lot more flexible than the old status codes from Temple Ready that are not even searchable.
As for forcing controls on the sort dates in the Edit Person screen that's an enhancement request in our tracking system.
