BryanJBryce

BryanJBryce

Resources involved are Employee, Shift, and EmployeeShift

Employee and shift are related many_to_many, through EmployeeShift, however, since an employee can clock in and out multiple times during an shift EmployeeShift has it’s own id and isn’t unique by pairs of Employee and Shift ids:

  attributes do
    uuid_primary_key :id
    attribute :in_at, :utc_datetime_usec, allow_nil?: false
    attribute :out_at, :utc_datetime_usec

    create_timestamp :created_at
    update_timestamp :updated_at
  end

  relationships do
    belongs_to :employee, PointOfSale.Accounts.Employee do
      api PointOfSale.Accounts
      allow_nil? false
      attribute_writable? true
    end

    belongs_to :shift, PointOfSale.Stores.Shift do
      allow_nil? false
      attribute_writable? true
    end
  end

Additionally EmployeeShifts have a custom primary create action called start that takes arguments of employ_id and shift_id and set’s the start time:

create :start do
      primary? true
      accept [:employee_id, :shift_id]

      argument :employee_id, :uuid, allow_nil?: false
      argument :shift_id, :uuid, allow_nil?: false

      change set_attribute(:in_at, DateTime.utc_now())
      change set_attribute(:employee_id, arg(:employee_id))
      change set_attribute(:shift_id, arg(:shift_id))
    end

When I start a new Shift I want to be able to pass an array of Employee ids to manage_relationship so that the custom start create function is called on EmployeeShift so that the included employees are clocked in automatically as the shift starts:

Shift


    has_many :employee_shifts, PointOfSale.Stores.EmployeeShift

    many_to_many :employees, PointOfSale.Accounts.Employee do
      api PointOfSale.Accounts
      through PointOfSale.Stores.EmployeeShift
      join_relationship :employee_shifts
    end
create :start do
      accept [:till_id, :employee_ids]

      argument :till_id, :uuid, allow_nil?: false
      argument :employee_ids, {:array, :uuid}, allow_nil?: false

      change set_attribute(:start_at, DateTime.utc_now())
      change set_attribute(:till_id, arg(:till_id))
      change manage_relationship(:employee_ids, :employee_shifts, type: create)
    end

However, when I attempt to create a new Shift via this action I get an error saying that the required arguments of shift_id and employee_id for EmployeeShift are missing.

The shift_id should come from the shift that is created just before running the manage relationship. And I thought I would be accepting employee_ids via the manage_relationship function.

I see that I can pass a map instead of a list of ids, and maybe that is the way, but that doesn’t solve the passing in of the shift_id that I don’t have since it get’s created.

Showing Posts 1 to 10

zachdaniel

zachdaniel

Creator of Ash

Hmm…this rings a bell on a bug that was fixed in the not too distant past. How up to date is your ash version?

BryanJBryce

BryanJBryce OP

OK, updated everything, still no luck:

iex(4)> shift = Shift.start!(%{till_id: till.id, employee_ids: employee_ids}, tenant: "dreambean")
[debug] QUERY OK db=0.2ms idle=1367.8ms
begin []
↳ anonymous fn/3 in Ash.Changeset.with_hooks/3, at: lib/ash/changeset/changeset.ex:2186
[debug] QUERY OK source="shifts" db=3.5ms
INSERT INTO "dreambean"."shifts" ("id","created_at","updated_at","start_at","till_id") VALUES ($1,$2,$3,$4,$5) RETURNING "till_id","updated_at","created_at","end_at","start_at","id" ["e3758301-5c59-4b8b-8fbc-ae80f258b281", ~U[2024-02-08 16:44:03.213427Z], ~U[2024-02-08 16:44:03.213427Z], ~U[2024-02-08 16:29:33Z], "9f5d6205-70f0-43ca-8a74-dc5de13b7886"]
↳ AshPostgres.DataLayer.bulk_create/3, at: lib/data_layer.ex:1412
[debug] QUERY OK db=0.4ms
rollback []
↳ anonymous fn/3 in Ash.Changeset.with_hooks/3, at: lib/ash/changeset/changeset.ex:2186
** (Ash.Error.Invalid) Input Invalid

* argument employee_id is required    at employee_ids, 0

* argument shift_id is required    at employee_ids, 0

    (ash 2.18.2) lib/ash/api/api.ex:2711: Ash.Api.unwrap_or_raise!/3
    iex:4: (file)
zachdaniel

zachdaniel

Creator of Ash

ah, okay interesting. Sorry, didn’t notice this until now.

Try this:

      change manage_relationship(:employee_ids, :employee_shifts, type: :create, value_is_key: :employee_id)
BryanJBryce

BryanJBryce OP

That solves the employee_id :tada:

But not the shift_id

** (Ash.Error.Invalid) Input Invalid

* argument shift_id is required    at employee_ids, 0

    (ash 2.18.2) lib/ash/api/api.ex:2711: Ash.Api.unwrap_or_raise!/3
    iex:4: (file)
BryanJBryce

BryanJBryce OP

I’m wondering if I even need the many_to_many at this point because the join table now has its own attributes and id, so should it really be modeled that way? I’m going to see if it changes anything. I don’t expect it to since the function is operating on the has_many relationship.

BryanJBryce

BryanJBryce OP

Yeah, that didn’t change it. I wonder if it is because EmployeeShift doesn’t use shift_id or employee_id as primary keys.

BryanJBryce

BryanJBryce OP

Same result.

zachdaniel

zachdaniel

Creator of Ash

Ah, okay I think its because its using the primary create action on the join resource which you’ve configured with required arguments.

zachdaniel

zachdaniel

Creator of Ash

You’ll need to point it at a different create action and/or make those arguments optional (because manage_relationship writes to the attributes, it doesn’t set arguments).

BryanJBryce

BryanJBryce OP

Ah, I see, lemme throw in new action in there. Does it always use the primary action or is there a way to specify?

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
kpanic
Hi everyone, I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding. I sta...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
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
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
apz
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New

Other Trending Topics Top

GenericJam
Edit: 2026 May 15 - This post is archived. Mob is alive!! Main docs: mob v0.7.11 — Documentation A bit of explanation for the slightly c...
New
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

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews