klwilkinson wrote:I attempted to delete the duplicate callings by deleting the entire calling from MLS. However, after doing a unit data refresh, the callings were not being deleted, so I'd have to reenter the callings and try again.
Doing a unit data refresh should cause all of the duplicate callings from CDOL to show up in MLS. The deleting of the entire calling from MLS needs to happen AFTER you do the unit data refresh, not before. After the refresh, you should delete all of the callings for the duplicate calling type. Then do Send/Receive. The delete may not be immediately seen in CDOL. You have to wait for it. Adding back in the calling just so you can delete it is a sure way to cause orphaned callings in CDOL that will not be in MLS. Never add a calling just so you can delete it. That will not work, and, as you saw, it makes it worse. Just simply complete delete all of the callings that had duplicates, then press Send/Receive. Then wait; within a day those callings will disappear from CDOL. Note, though, that you have to have done a real full Unit Data Refresh before you delete those callings.
klwilkinson wrote:In MLS, it was only showing a single calling (it didn't have the duplicates present in CDOL)
After doing the Unit Data Refresh, MLS should have the duplicates present in CDOL. That's the purpose of doing a Unit Data Refresh, to make MLS callings list look like what is at CDOL. By the way, just to make sure we are all on the same page, doing a Unit Data Refresh is more than just simply going to File > Request Unit Data Refresh and selecting Membership data and pressing Send/Receive. That action just requests the Unit Data Refresh. To complete the Unit Data Refresh, you have to come back in a few hours (I was told 24 hours), then press Send/Receive again in order to get the unit data refresh file downloaded to your MLS.
klwilkinson wrote:However, when I would do a unit data refresh to correct the callings, the refresh would add the merged classes back into MLS.
That another reason why doing a Unit Data Refresh Download is a blunt tool that is not a good workaround to this problem; it undoes any merged classes, and it undoes any out-of-unit callings you had defined. Unfortunately it is the only tool we have right now for it. Refrain from merging the classes again after the Unit Data Refresh until a few days later after all of the callings are settled.
klwilkinson wrote:No teachers show up in MLS and they still don't show up after doing a unit data refresh.
My guess is that you are not doing the Unit Data Refresh correctly. Again, just selecting File > Request Unit Data Refresh and then doing Send/Receive is NOT doing a unit data refresh. That just queues up a request for one. To actually do the unit data refresh, you need to come back 24 hours later and do another Send/Receive
klwilkinson wrote:I wish the Sunday School information in CDOL and online could just be deleted and allow me to reenter the information in MLS, but it sounds like that is not an option.
I agree with you. The Unit Data Refresh Download is not an intuitive tool and requires much care and feeding to do it right. What we really need, the silver bullet in cases like this, is a "Request Unit Org Data Refresh UPLOAD" capability in MLS. The clerk would get MLS to appear just like it should be, then select that data refresh upload, then CDOL would magically look just like MLS. We seem to be going to great contortions because that capability is not present in MLS. I fear that a lot of clerks will spend a lot of effort continually trying to fix these synch problems between MLS and LDS.org, or the problems just won't get fixed and people will eventually learn to ignore the Org data at LDS.org because it is unreliable.