LDS Tools App is showing incorrect Primary class titles.
If I login to LCR on a computer, everything is correct.
In Tools, a combined Primary class is showing twice and the Valiant 9 class is showing as a second Valiant 10 class.
This image shows the correct listing from LCR online.
How do we get Tools to match the correct Primary classes in LCR?
LDS Tools App is showing incorrect class titles
-
hamptonc
- New Member
- Posts: 3
- Joined: Sun Jan 25, 2026 10:59 am
LDS Tools App is showing incorrect class titles
You do not have the required permissions to view the files attached to this post.
-
kd7mha
- Member
- Posts: 311
- Joined: Thu Mar 13, 2008 2:27 pm
- Location: Logan, Utah
Re: LDS Tools App is showing incorrect class titles
Have you tried "data refresh" (not to be confused with sync)
There are 11 types of people. Those who understand Gray Code and those that don't.
-
hamptonc
- New Member
- Posts: 3
- Joined: Sun Jan 25, 2026 10:59 am
Re: LDS Tools App is showing incorrect class titles
I did a complete stake data refresh and it didn't change anything. Still shows incorrect/extra classes. It is on everyone's app, not just mine.
-
hamptonc
- New Member
- Posts: 3
- Joined: Sun Jan 25, 2026 10:59 am
Re: LDS Tools App is showing incorrect class titles
We can't be the only ward in the entire church that has this issue... Does anyone have any suggestions?
-
jonesrk
- Church Employee

- Posts: 2613
- Joined: Tue Jun 30, 2009 8:12 am
- Location: South Jordan, UT, USA
Re: LDS Tools App is showing incorrect class titles
I was expecting our release near the first of this month to help with the problem. In some ways it did, now LCR shows the same thing as Member Tools does. One thing you can do to fix it is to take the class that has the wrong name and split it, then combine the split one back into other one and it should fix the name.
The reason that this works is that the incorrectly named class has a custom name left over from the old system and the new system doesn't allow a custom name unless a class is merged or split, so the recombining the two classes clears it out and lets the correct name show up.
The reason that this works is that the incorrectly named class has a custom name left over from the old system and the new system doesn't allow a custom name unless a class is merged or split, so the recombining the two classes clears it out and lets the correct name show up.