Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
1. Not trying to be harsh, as you will see below I have lots of suggestions, but I do want to point out that simply throwing out a blob of code and saying "explain this to me" isn't the kind of thing that anyone appreciates. At least put forth some type of effort to indicate what you are trying to do, what you have done to debug the code, what error messages you are getting, what you have done to try to correct the problems etc.
2. Ask your teammate that shared their code to start commenting their code so that it is maintainable. Whether it is Qlik Script or any language Commenting code is essential. You can actually make the comments fun by utilizing emojis as call outs. When you solve a complex problem celebrate it by telling the world what you have achieved ... in the comments:
3. Take each word you don't understand and simply do a Google search. Not trying to sound contrite, but the best way to learn is to dig in. For example the first thing in the code is NoConcatenate. If you search for that word and Qlik Sense you will immediately get a link to the Qlik Help Document for it so that you can read more, and in many cases, like this one, you will find other Qlik Community posts that contain narrative from others about the topic.
4. At any point in qlik script code you can add an Exit Script statement that will allow you to stop the load processing so that you can see what you have in your data model up to that point. If you place it in a point where you shouldn't you will get an error message. If you place it, per my example, right after your first table called Hierarchies is loaded you can then look at the data model so that YOU can see what the code is doing.
Hierarchies:
NoConcatenate
Load
NTNAME,
ATTRIBUTE,
DATAFIELD,
If(WildMatch(DATAFIELD, '*Global*')>0,Trim(Mid(DATAFIELD,1,Len(DATAFIELD)))) as GLOBAL,
If(WildMatch(DATAFIELD, '*GEO L1*')>0,Trim(Mid(DATAFIELD,9,Len(DATAFIELD)))) as GEO,
If(WildMatch(DATAFIELD, '*GEO L2*')>0,Trim(Mid(DATAFIELD,9,Len(DATAFIELD)))) as COUNTRY
Resident UAM;
Exit Script;
5. You can refer to this community post that I wrote called Making Sense of Section Access in Qlik Sense. https://community.qlik.com/t5/Documents/Making-Sense-of-Section-Access-in-Qlik-Sense/ta-p/1493716
6. You have posted in Qlik Sense forum but looking at the script I imagine it was written for QlikView. Things like that are important to share for the community so that others can immediately offer help like ... "QlikView used NTNAME but Qlik Sense does not. It looks for USERID field name instead. See this post to see the other differences. https://community.qlik.com/t5/App-Development/Differences-between-Section-Access-in-QlikView-and-Qli...
