Skip to main content
Announcements
Introducing Qlik Answers: A plug-and-play, Generative AI powered RAG solution. READ ALL ABOUT IT!
cancel
Showing results for 
Search instead for 
Did you mean: 
dineshm030
Creator III
Creator III

Section Access Is Not Working Based on Period

Hi All,

I have created the section access with the below script.

AuthBridge:

Load Upper(BusinessUnit) & Upper(Team_Level_1) & Upper(RegionDesc) & Upper(AMHQCode) & Upper(SAP_TerritoryDesc) as AuthID,
Upper(BusinessUnit) & Upper(Team_Level_1) & Upper(RegionDesc) & Upper(AMHQCode) & Upper(SAP_TerritoryDesc) as %AuthID
Resident Fact_Sales;

Load Upper(BusinessUnit) & Upper(Team_Level_1) & Upper(RegionDesc) & Upper(AMHQCode) & Upper(SAP_TerritoryDesc) as AuthID,
Upper(BusinessUnit) & Upper(Team_Level_1) & '*' & Upper(AMHQCode) & Upper(SAP_TerritoryDesc) as %AuthID
Resident Fact_Sales;

Load Upper(BusinessUnit) & Upper(Team_Level_1) & Upper(RegionDesc) & Upper(AMHQCode) & Upper(SAP_TerritoryDesc) as AuthID,
Upper(BusinessUnit) & Upper(Team_Level_1) & Upper(RegionDesc) & '*' & Upper(SAP_TerritoryDesc) as %AuthID
Resident Fact_Sales;

Load Upper(BusinessUnit) & Upper(Team_Level_1) & Upper(RegionDesc) & Upper(AMHQCode) & Upper(SAP_TerritoryDesc) as AuthID,
Upper(BusinessUnit) & Upper(Team_Level_1) & Upper(RegionDesc) & '*' & '*' as %AuthID
Resident Fact_Sales;

Load Upper(BusinessUnit) & Upper(Team_Level_1) & Upper(RegionDesc) & Upper(AMHQCode) & Upper(SAP_TerritoryDesc) as AuthID,
Upper(BusinessUnit) & Upper(Team_Level_1) & '*' & '*' & Upper(SAP_TerritoryDesc) as %AuthID
Resident Fact_Sales;

Load Upper(BusinessUnit) & Upper(Team_Level_1) & Upper(RegionDesc) & Upper(AMHQCode) & Upper(SAP_TerritoryDesc) as AuthID,
Upper(BusinessUnit) & Upper(Team_Level_1) & Upper(RegionDesc) & Upper(AMHQCode) & '*' as %AuthID
Resident Fact_Sales;

Load Upper(BusinessUnit) & Upper(Team_Level_1) & Upper(RegionDesc) & Upper(AMHQCode) & Upper(SAP_TerritoryDesc) as AuthID,
Upper(BusinessUnit) & Upper(Team_Level_1) & '*' & '*' & '*' as %AuthID
Resident Fact_Sales;

Load Upper(BusinessUnit) & Upper(Team_Level_1) & Upper(RegionDesc) & Upper(AMHQCode) & Upper(SAP_TerritoryDesc) as AuthID,
Upper(BusinessUnit) & '*' & '*' & '*' & '*' as %AuthID
Resident Fact_Sales;

Load Upper(BusinessUnit) & Upper(Team_Level_1) & Upper(RegionDesc) & Upper(AMHQCode) & Upper(SAP_TerritoryDesc) as AuthID,
Upper(BusinessUnit) & '*' & Upper(RegionDesc) & '*' & '*' as %AuthID
Resident Fact_Sales;

Load Upper(BusinessUnit) & Upper(Team_Level_1) & Upper(RegionDesc) & Upper(AMHQCode) & Upper(SAP_TerritoryDesc) as AuthID,
Upper(BusinessUnit) & '*' & Upper(RegionDesc) & Upper(AMHQCode) & '*' as %AuthID
Resident Fact_Sales;


Load Upper(BusinessUnit) & Upper(Team_Level_1) & Upper(RegionDesc) & Upper(AMHQCode) & Upper(SAP_TerritoryDesc) as AuthID,
Upper(BusinessUnit) & '*' & Upper(RegionDesc) & Upper(AMHQCode) & Upper(SAP_TerritoryDesc) as %AuthID
Resident Fact_Sales;

 

Some sales have been moved manually in the backend script to Supra region for Q3. The security file is linking by AUTHORISATIONKEY with this AuthBridge table.

dineshm030_3-1724844448064.png

 

The section access is functioning correctly according to our security file, but it doesn't operate as expected with time periods when manual backend changes are made.

When selecting Jun, the section access is working fine whereas in July supra data also visible.

dineshm030_1-1724844359768.pngdineshm030_2-1724844373524.png

Please help on this.

Thanks in advance.

Labels (4)
2 Replies
marksouzacosta
Partner - Specialist
Partner - Specialist

Hi @dineshm030,

I don't think this will solve your problem (maybe!), but it is a common and good practice to add a separator when combining strings. Please consider doing the following, it can save you a lot of headaches:

Load 
Upper(BusinessUnit) & '|' & Upper(Team_Level_1) & '|' & Upper(RegionDesc) & '|' & Upper(AMHQCode) & '|' & Upper(SAP_TerritoryDesc) as AuthID,

Upper(BusinessUnit) & '|' & Upper(Team_Level_1) & '|' & Upper(RegionDesc) & '|' & Upper(AMHQCode) & '|' & Upper(SAP_TerritoryDesc) as %AuthID
Resident Fact_Sales;

This will avoid any unwanted and unaware combination that sometimes can be really hard to catch.

 

Regards,

Mark Costa

Read more at Data Voyagers - datavoyagers.net
dineshm030
Creator III
Creator III
Author

Hi @marksouzacosta 

 

Thanks for your response. We need remove the access SUPRA region for Q3.