Bishopric members all under custom positions - lost financial authorization

giffordrb · #31

TinMan wrote:Thanks. Again. I appreciate your personal attention to this. I know it probably hasn't been a pleasant week for you at work.

Thanks - It has been a busy week (past few weeks actually), and stressful at times, but that's how software releases go. MLS upgrades usually go fairly smooth. This one is a huge release for MLS, with both CDOL and CUBS functions going through major changes. It has been nice getting the feedback that we have, and it's nice having the ability to get it right rather than being tied to specific release date regardless of quality.

giffordrb · #32

rontilby wrote:If the CDOL Refresh might result in removal or addition or re-arrangement of callings in MLS, then that should be clearly stated, with a recommendation for printing a full callings by organization report before and after the CDOL Refresh with review and correction afterwards.

Good point. If after the upgrade callings and classes were fixed and sent to CDOL then this won't have to be done again because the CDOL refresh will contain the changes made post upgrade. It's worth keeping in mind, but if CDOL looks correct post initial upgrade then the class reset will not happen again. It was a one time operation going from 3.4.3 to 3.5.

giffordrb · #33

Here are the steps for this fix, once the patches are released (later today):
1. Send/Receive to get the patches
2. Restart MLS and verify you are running 3.5.0_20988 or greater
3. Call LUS and mention that you are a beta unit and your standard positions are appearing as custom positions. They will setup a file to come down to your unit.
4. Send/Receive when that has been completed.
5. Another Send/Receive to pull down CDOL positions file
6. From MLS, click on File->Request Unit Refresh Data, then check Membership Records, then OK.
7. Send/Receive to send the refresh request up. This will cause CDOL to create a refresh file for your unit.
8. Wait a period of time (usually 30 minutes) and then do another Send/Receive to pull down the refresh file.

As you can see the fix is very timing specific. You must be running the latest MLS when receiving the file mentioned in steps 2 - 5 . Then the CDOL refresh must be processed after that file. Then there will be smiles all around.

And to clarify - this is a specific fix related to standard positions showing as custom positions.

TinMan · #34

Then this must be done when LUS is available? Like Friday during the day?

How long between steps 3 and 4? Minutes? Hours? While on line? How will we know when it is completed?

Again. Thanks for your help

giffordrb · #35

TinMan wrote:Then this must be done when LUS is available? Like Friday during the day?

How long between steps 3 and 4? Minutes? Hours? While on line? How will we know when it is completed?

Again. Thanks for your help

There shouldn't be a wait between steps 3 and 4. Once LUS stages the file for your unit it can be pulled down right then. Staging it takes seconds on their part so it can be done while on line with them. They can verify that you received it. You will know it came down as well by watching the send/receive status. You will see something related to MLS Swap, like in the image below:

Then you can move on to step 5. I apologize for all these steps - it was a strange bug and those require strange fixes at times.

TinMan · #36

Yeah. Well most think we are a strange ward anyway. So it all fits.

Just curious: Of the 4000 tests sent out, how many units were affected?

giffordrb · #37

FYI

The files coming down in step #5 look like this in the Send/Receive status:

giffordrb · #38

TinMan wrote:Yeah. Well most think we are a strange ward anyway. So it all fits.

Just curious: Of the 4000 tests sent out, how many units were affected?

It's hard to say how many were affected because there isn't a way to identify units experiencing this outside of support requests. CDOL still shows the affected positions as standard positions, and MLS doesn't log an error so we can't easily grep through log files. I only know of a handful from this thread and a few calls to support. I'm sure others will crop up though - not everyone reads this forum or calls LUS when there is an issue. New units just coming on to 3.5 won't get to experience this.

giffordrb · #39

Patches for this are live for all beta units.

TinMan · #40

Thanks. We will give it a try in the morning.