Activity
Mon
Wed
Fri
Sun
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
What is this?
Less
More

Memberships

Small Cap Momentum Lab

8 members • Free

TO
The Optimization Collective

14 members • Free

Sports Betting and Forecasting

28 members • Free

IT Connect

13 members • Free

Data Uncovered

6 members • Free

Arc Academy for Qlik

41 members • Free

Radicle Analytics

11 members • Free

PS
Princeton Sports Analytics

21 members • Free

RANDY’S COMMUNITY

4 members • Free

2 contributions to Arc Academy for Qlik
⚔️ Qlik Debate: ApplyMap() vs Left Join... What’s Your Default?
Quick community check… When a script needs to bring in a single attribute (example: Category Name, Region, Account Owner) from another table, which approach is the go-to? Vote in the comments with one option: 1. ApplyMap() 2. Left Join 3. Associate 2-column table on key 4. It depends (and explain when) To make it useful, include: - Why that’s the default - Any performance or maintenance lessons learned - A quick “rule of thumb” (if you have one) Best answers will be summarized and shared in the next Arc Newsroom as a “community best practices” takeaway.
0 likes • 24d
@Arc Analytics Thanks for accepting my request to Join the community and I’d really love what you’re building in your space and would love to be part of it. Just joined and really impressed by the energy here. I love seeing communities like this grow, I help new and existing skool community owners build genuinely and would love to share you some tips that would actually help your community stand out , let me know if you are open to it?
🧩 One Dashboard Rule You Always Follow (and why)...?
If you could give a new Qlik developer one rule to follow when building dashboards, what would it be? Examples: - “One question per chart” - “Never use more than 5–6 colors” - “Always start with KPIs before detail tables” - “If it needs a paragraph to explain, it’s too complex” - “Default selections should tell a story” Drop one rule + one sentence on why it matters. Best answers will get compiled into a Community Dashboard Playbook and shared in an upcoming Arc Newsroom.
0 likes • 24d
If it needs a paragraph to explain, it's too complex. Users should understand a dashboard at a glance, if it requires lengthy explanations, the design needs simplification.
1-2 of 2
Mentor Isaac
1
5points to level up
@mentor-isaac-4933
Skool Community Manager | Boosting engagement, crafting valuable content, and nurturing collaborative, growth-driven communities.

Active 2d ago
Joined Jun 15, 2026