Page 1 of 1

Read Only Custom Postions

Posted: Sun Aug 24, 2014 10:48 am
by daron
In MLS-> Organizations->Callings by Organization I've created some Custom Positions for RS, Primary, Other, etc. Some of these positions appear to Read-Only . For example I've added a position of "Emergency Preparedness Specialist" under "Other". The position column is not a link, but the words and the "remove" link is missing. These callings are behaving like positions from the stake. I can see but not change. I've talk with the stake specialist, thinking that the stake is setting a read-only flag somewhere and he assures me that they're not.

My questions are: 1) Why are these custom positions that I've added are read-only; 2) How do you make them update-able (I would like to update the set-apart flag on some of them); 3) If I cannot update them how could the be deleted; and 4) This seemed to have started right after the latest MLS update, could this be a MLS issue?

Thanks,
Bro. Baird
Ward Clerk
Lexington Park Ward, Suitland Maryland Stake.

Re: Read Only Custom Postions

Posted: Sun Aug 24, 2014 11:36 am
by eblood66
I can't say why that's happening. But to delete them I'd try deleting the entire custom position definition. Go to the organization screen and click on the Custom Positions tab on the left. If the custom position has a Remove link on that screen, try deleting the position. It should warn you about who currently holds that position and indicate that they will be released if you delete the position. Click OK to continue. Then if you still need the position add it again and re-enter the the specific members in the position as needed. You may want to write down the sustained dates before deleting the custom position if you need to re-enter them.

Re: Read Only Custom Postions

Posted: Mon Aug 25, 2014 8:26 am
by scgallafent
This is a known is that will be corrected in MLS 3.7.3. The update should be ready within a few weeks.

You can try a unit data refresh to see if that corrects it. There was another forum user who reported that didn't correct it for him, but that resolved the issue when we did our initial testing.