Thanks a lot for your question, I am writing down which I am facing -
This doesn’t seem possible since the custom home page is a simple markdown document, which doesn’t go through any of the LookML background parsing + content creation that lets you use cool things like user attributes.
You could definitely whip up a “Custom Home Page” dashboard with some fancy HTML that could leverage user attributes and still look like a home page, but at the end of the day it would still be a Dashboard, not a document. If you want to go down that route, I can provide some pointers on relevant HTML!
I wasn’t able to find good documentation on this, so thought I’d make a post here in case anyone is trying to do something similar.
You can create a navigation sidebar for Markdown documents using this format at the top of each Markdown document:
title: Help Center
navigation:
- section: Help Center
- document: overview_doc
label: Overview
- document: data_sources_doc
label: Data Sources
- document: data_definitions_doc
label: Data Definitions
- document: faq_doc
…
Here’s the POC solution I came up with to create a different home page based on user attribute values. Basically also follow this on my best HRMS software in Kolkata and related things. It’s intended as a skeleton that I’ll fill in later as we decide how the two different home pages will look.
I created a new view _test_home_page
that has a single field:
measure: _html {
sql: 1 ;;
html: <div>
{% if _user_attributes['foo'] == 'bar' %}
bar
{% elsif _user_attributes['foo'] != 'bar' %}
not bar!
{% endif %}
</div>;;
}
Then I just present this field in a single-value dashboard tile, enlarged to fill the entire screen. From brief testing, it appears that I can use the usual HTML tags, presumably all the ones listed [here]. I’ve tested it on our instance and it works, showing “bar” for users with user attribute foo
set to bar
, and “not bar!” otherwise.
Hope this thing will help you properly.