Ravindra BagaleCourses & study guides मराठी Track your progress

29. Practice Exercises and Final Assignment

29.12 Modules 25–27: Service, RLS and Performance

By Last updated:

  1. Explain to a colleague the difference between sharing a report and publishing an app.
  2. Configure scheduled refresh (if you have access) and note the maximum refreshes per day for your licence.
  3. Create static roles for each city and test them with View as.
  4. Build dynamic RLS with a User Security table (use the e-mails from Module 26, e.g. ravina@example.com sees Pune and Mumbai) and test with Other user.
  5. Run Performance Analyzer on your busiest page. Identify the slowest visual and one way to improve it.
  6. Remove Order DateTime and other unused columns and compare the file size before and after.

Practice files (fictional): rls_user_security.csv, performance_analyzer_sample.csv, visuals_orders_apr_may_2026.csv

Hints
  • Write expected results before you test.
Solutions (checked on the practice files)
  1. Share = one item with people; App = packaged content for an audience.
  2. Pro: up to 8 scheduled refreshes per day (more on capacity) – check current limits.
  3. Static roles: Pune ₹850, Nashik ₹800, Kolhapur ₹450.
  4. Dynamic RLS with the practice table: salman@example.com sees Pune + Nashik = ₹1,650 (6 rows).
  5. Practice file: Store matrix is slowest (3,650 ms of 4,135 ms); move it to a drill-through page.
  6. Removing high-cardinality columns such as Order DateTime reduces model size.

Ravindra Bagale's Tip

A common mistake is doing the RLS exercise without testing it. Use View as for every role, and write down what each role should and should not see before you test. Practise, and it will feel very easy.