Good day,
I have seen that issue as well. I have a function that prior to running
a backup is saves the users and groups to a blob using user to blob and puts
them in the database. I have seen this issue where when a restore the users and
groups the memberships in the groups get botched. This mostly affects new users
or settings that were changed prior to my uploading the new .4db code. It
really can make a mess of things if I took a few months to create a new .4db
file and was working on features. I think the issue may be that while the users
and groups are replaced the users group memberships are restored to the saved
values and if anything causes a change or is different the memberships do not
restore right.
I am hoping that the new v18 way of holding this data in the JSON file
will help alleviate the problem since I can use Version tracking on the JSON
data file to monitor and fix things. But I have not seen how the JSON file
works since I am not running the v18 beta.
> On Jan 13, 2020, at 10:45 AM, Doug Hall via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> I thought I'd replace hand-written code I got from Mark Mitchenall many
> years ago, since 4D had since come out with two commands (since 15.4?)
> which theoretically, would make that code unnecessary -- blob to users and
> users to blob.
>
> From what I understood, the users, groups, and modifications made by the
> Administrator user would be deleted and replaced upon execution of blob to
> users. Great! I could create a routine which would export those changes
> when bringing down the server, and import them when starting the server!
>
> Well, as it turns out, for some reason, the modifications (membership)
> changes made by my Administrator changes are not all being retained. I
> tried this two different ways, too: First, by executing blob to users in 4D
> local mode, when signing in as Designer on my development and production
> machines. This way, when I built the resulting compiled structure, it would
> be up-to-date already. The second way, was as I described above, by simply
> executing blob to users in the "on 4D Server Startup" method. Neither
> method retained my change. To test this, I logged in as Administrator and
> simply changed one membership status of a person added by the
> Administrator. The Groups were all added by the Designer user, since I
> don't want these particular groups to ever disappear. Does it matter that
> the groups were created by the Designer? The way the documentation reads,
> any group "created or modified by the administrator" should be affected.
>
> I am using the latest hotfix of 17.3. Where did I go wrong?
>
> Thanks,
> Doug
> **********************************************************************
> 4D Internet Users Group (4D iNUG)
> Archive: http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub: mailto:4d_tech-unsubscr...@lists.4d.com
> **********************************************************************
**********************************************************************
4D Internet Users Group (4D iNUG)
Archive: http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:4d_tech-unsubscr...@lists.4d.com
**********************************************************************
