RussellHltn wrote:This is confusing.
RussellHltn wrote:Looking at the Geocode data entry screen, there are Ward Code and Stake Codes. Those are two separate fields and the two columns appear at both the Ward and Stake level.
Correct. And to further confuse matters, the stake geocode on the ward MLS is not the same as the stake geocode on the stake MLS.
RussellHltn wrote:The ward can enter values into either field. The Stake can only enter values into the Stake code. So for the stake code field, there is "Ward-entered Stake codes" and then there are "Stake-entered Stake codes".
Yes. And the stake geocode the ward sees is always and only the ward-entered code. (The stake code the stake sees can be any number of things.)
RussellHltn wrote:I did verify that under 3.3.0 and 3.3.1, any value entered into the Ward Geocode (by the ward) is automatically populated into an empty Stake Geocode upon closing the screen. The wards are unable to leave the stake geocode blank if the ward geocode is populated.
So far, so good. And this was on the ward MLS.
RussellHltn wrote:Now, someone help me out. Wasn't there at one time just one Geocode that had a complex behavior as Larry describes? If so, then that might explain things. What the ward enters, the ward sees. If the stake enters nothing, it sees what the ward enters. If the stake does enter something, then the ward never sees it.
Mostly true. Since the days of MLS, I think there has always been more than one geocode. Nevertheless, . . .
The purpose of the stake geocode field on the ward MLS is so that the ward can send a code to the stake that is different from the code the ward wants to use.
The ward enters a ward geocode. If they stop there, the code flows to the stake geocode field on the ward MLS.
The ward may choose to enter a different stake geocode (either on their own or at the request of the stake). If they do, the ward MLS will show different ward and stake geocodes on the ward computer.
Whatever the ward does, it is the stake geocode from the ward computer that attempts to flow to the stake and become the stake geocode. That code is either the ward code that also propagated to the stake field or the separate stake code that the ward manually entered.
Whatever the stake does, nothing will flow back to the ward. And at any time, the ward may change either the ward or stake geocode showing on the ward MLS.
The stake geocode from the ward computer tries to flow to the stake MLS. If there is not a stake code already present, the stake code from the ward becomes the stake geocode on the stake MLS. If there is already a stake code present, the stake code from the ward does not flow.
Separately, the ward geocode shows in stake MLS as the ward geocode. The stake cannot change it or do anything with it.
The stake may change, delete, or do anything it wishes with the stake geocode on the stake computer. Again, the ward will never know what the stake does with the code. If the stake deletes the stake geocode, the stake geocode from the ward computer will try once again to flow to the stake computer.
The stake can do nothing with the ward geocode displayed on the stake computer. (However, those geocodes also should not be populating the stake geocode dropdown list that is the discussion of another thread. If they are, there is a bug.)
Clear as mud.