_russellb
I need to build a crm-like dashboard to present customer data to the logged in user.
Would you implement the dashboard as property of the customer using something like
schema "customers" do
has_one(:dashboard, Dashboard )
end
Or would you just have a Dashboard controller (not a table) and only make it available on certain routes?
For example let’s say the logged in user is viewing the customer show page. I could then get customer from the params and look
them up in the database then present the customer data on the dashboard.
Both ways would work but which is less error prone? Or is there another way to do this that I’m not seeing?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Practical resources that improve the lives of professional developers.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #metaprogramming
Our Sponsors
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
sobojack
Hi, @_russellb, I think it would be considered best practices to go the controller route. Phoenix promotes MVC( Model, View, Controller ) principles designed just for this. If I were you I would create a controller for your dashboard, along with that I would create a dashboard template in yourAppWeb/templates/dashboard/index.html.eex and a dashboard view in yourAppWeb/views/ dashboard_view.ex. You can call functions to load your data in your controller and pass that data to your template, in your template you can render the data in your CRM like fashion. You can use your view file to call functions for any logic needed in your template.
Inside your router you can create a route for this page, you can also restrict the route to only allowing certain usesr to view it.
_russellb
Thanks, that’s the way I’ve been writing this feature. I just wanted some extra opinions on how to do it.