I think there is no functionality with which you could ensure that any renamed fields are further captured within the section access.
This means you need to address this topic on an administrative level, like:
- any change is thoroughly communicated between all developers
- each change must be checked/approved from a master-developer
- carefully checks with end-user credentials
- very strict rules how datamodels/applications are developed in regard to settings, structure, namen-pattern and so on and of course who changed/developed what when and where and everything is well documented
The more the work is divided the more administrative overhead is needed to control a proper development, testing, maintaining of the whole environment. It could become much more difficult as to handle the tool itself - and it's not only related to Qlik else this challenge exists for every tool.
In your case I could imagine that a general prohibition of renaming fields within the normal load-statements may the easiest way to avoid such problems. Of course you will need various renaming but to do this with a mapping which has an external source - maybe in an Excel or any database which is also the source for the section access.
Not trivial, not easy to implement and of course causing some efforts and it won't be never a guarantee that it worked in all circumstances which means you will always need a careful check of the application returns the right information (not only in regard to any access control) before publishing it.
- Marcus
