9 replies

Update action discrepancy

I have an update action:

    update :retire do
      change set_attribute(:status, :retired)
    end

    update :retire do
      change set_attribute(:status, :retired)
    end

    update :retire do
      change set_attribute(:status, :retired)
    end

    update :retire do
      change set_attribute(:status, :retired)
    end

on two resources. One returns ok tuple when called through a interface, the other a bulk result. What could be the reason for this?

Solution

are you calling them the same way? eg. with a single record?

Jump to solution

Ash Framework Join

The Elixir backend framework for unparalleled productivity. Declarative tools that let you stop wasting time. Use with Phoenix LiveView or build APIs in minutes for your front-end of choice.

2,182Members

View on Discord

Resources

Recent Announcements

Similar Threads

Custom on option on update action

AFAsh Framework / support

4mo ago

adding for update to a read action

AFAsh Framework / support

3y ago

get selected fields in create/update action

AFAsh Framework / support

3y ago

ash_graphql update without authorizing the read action

AFAsh Framework / support

3mo ago

Similar Threads

Was this page helpful?

Communities Docs About Terms Privacy