Qlik Community

App Development

Discussion board where members can learn more about Qlik Sense App Development and Usage.

Announcements
Join “Do More With Qlik” with Mike Tarallo to get a first-hand look at the New Authoring Experience, June 29th: REGISTER HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
Jared
Contributor III
Contributor III

Renaming a field that is Omitted

Hi All,

 

I have a scenario where Section Access has set a column to be omitted, however in some cases other developers would like to rename that field.

Is there a way to set the section access to omit the field for some users, and have that carried with the field if it gets renamed?

 

I have tested and confirm that it doesn't appear to move with the naming, but wonder if perhaps there is some trick that you may have come up with to handle this kind of scenario.

 

Thanks,

 

Labels (2)
1 Solution

Accepted Solutions
marcus_sommer
MVP & Luminary
MVP & Luminary

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

View solution in original post

3 Replies
Ksrinivasan
Specialist
Specialist

marcus_sommer
MVP & Luminary
MVP & Luminary

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

Jared
Contributor III
Contributor III
Author

Thanks Marcus,

That is pretty much what I was thinking - nice to have it confirmed.

We do actually do the sorts of thing you suggest where in our development we do have an external excel sheet that maintains our standard naming for fields in all apps, and any apps to be published for business consumption go through a small team (2 people) who can control this sort of thing. I was hoping that we could find a way to govern it a little more automatically - as you rightly point out it can be a challenging job to ensure this given the freedom users have when they create a data load script.

 

Still I guess at this point it's going to be a matter of reviewing load statements and rename statements to look for any cases.

Thanks,

Jared