crislapi wrote:Just tested this on a unit that has 3.3.0b4. The options are slightly modified so I'm attaching a screen shot.
The exports from this unit (running Windows 7) also do not contain MRN, even if that is the only field I select. After selecting "Family Data", you select "Customize" and can choose what fields to export. Because MRN is one of the options, I would assume that information has not intentionally been removed from the export. It is likely a bug.
I noticed there are also no headers in the export file.
I have tested this on another unit running 3.3.0b4 on Windows XP sp3. It still has the "Export Membership Data" option. However, the exported data does not contain MRN. It also has "export family data" and "export individual data" options. Neither of these show MRN in the export file even though it is selected in the "Customize" options.
Thanks for that effort. The dialog you illustrated is not what produces the Membership.csv file. By selecting Family or Individual data, the dialog has always created the PalmFamily.csv file or PalmIndividual.csv files respectively.
Whether or not the option to export Membership.csv appears depends on user privilege. If the user has the right privilege, Membership is listed as the top choice among the checkboxes in the first dialog. If not, the choice does not even show up. Perhaps the MRN data being suppressed in the output of PalmFamily.csv in that test was also a function of the lower privilege in that session.
However, I think your test on the other unit (the one running XP) is what matters. From your report of this test, it appears that the MRN column is still being dropped from Membership.csv in the latest build.
I suggest that the immediate action required is to find out if this is a bug or a deliberate design change. Presumably, those units who are in the 3.3.0 beta program have the standing to report bugs in the version. If it is a bug, it obviously needs to be fixed before production release.
If this is by design, or if it is a bug not fixed, that would be a big negative surprise not just for the beta units today, but for all units soon because 3.3.0 is supposed to be deployed generally. That change would break the software -- Ward Tools, etc. -- used by many stake and ward leaders.