nallwhy

nallwhy

I’m a bit stuck on how to correctly use aggregates on a resource.

Let’s say I have the following resource:

defmodule MyApp.Invoice do
  use Ash.Resource

  attributes do
    uuid_v7_primary_key :id
    attribute :amount, :decimal, allow_nil?: false
    attribute :settled, :boolean, default: false, allow_nil?: false
  end
end

I want to get the sum of all amounts where `settled is false, so I defined this aggregate:

aggregates do
  sum :total_amount, [], :amount do
    filter expr(not settled)
  end
end

But:

  1. I’m not sure what the proper way to fetch this aggregate is.
  2. When I tried using Ash.aggregate(MyApp.Invoice, {:total_amount, :sum}), it didn’t seem to apply the filter.

I’m not sure if this is a bug or if I’m misunderstanding how it’s supposed to work.

I only shared the relevant code here, but if it helps, I can create a minimal repo to reproduce it.

Thanks in advance!

Showing Posts 1 to 5

FlyingNoodle

FlyingNoodle

Aggregates are “per instance of this resource”.

I think something like this:

# in your resource
defmodule MyApp.Invoice do
  actions do
    read :not_settled do
      filter expr(not settled)
    end
  end
end

# in your domain
defmodule MyApp.MyDomain do
  resource MyApp.Invoice do
    read :get_not_settled_invoices, action: :not_settled
  end
end

# consumer
MyApp.MyDomain.get_not_settled_invoices() |> Ash.sum(:amount)

but I don’t know if thats the best way to do it? I mean you can also put this function in your domain or wherever you like.

nallwhy

nallwhy OP

MyApp.Invoice |> Ash.Query.filter(expr(not settled)) |> Ash.sum(:amount) works for me.

FlyingNoodle

FlyingNoodle

Generally you want to move these things to read actions though and not just freestyle it everywhere.

ken-kost

ken-kost

I think what you want is to put the aggregate into the parent resource and then you can just load the aggregate from the parent resource. Something has those invoices right?

zachdaniel

zachdaniel

Creator of Ash

Ash.aggregate(Resource, {:total_amount, :sum}) should be requiring that you specify a field to be summing, i.e Ash.aggregate(Resource, {:total_amount, :sum, field: :amount}).

Ash.aggregate is for aggregating information about a query/resource as a whole. i.e

Resource
|> Ash.Query.filter(not settled)
|> Ash.aggregate(Resource, {:total_amount, :sum, field: :amount}

will get you back something like this:
{:ok, %{total_amount: #Decimal<10.0>}}, and is the “sum of of all amounts that are not settled”.

The aggregates declared in a resource are different, they are more like a calculation. They are for summary information about related data.

# on a customer resource for example
sum :total_unsettled_invoices_amount, [:invoices], :total_amount do
  filter expr(not settled)
end

This allows you to say:

customer |> Ash.load!(:total_unsettled_invoices_amount)

which return something like

%Customer{total_unsettled_invoices_amount: #Decimal<10.0>}

That total_invoices_amount is “for the given customer(s), the sum of all related invoices, which are not settled”

Hopefully that helps!

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews