I am trying to load a book, update it and update the associated record like this: Multi.new() |> Multi.run(:get_book, fn _ -> Mango.Books.get_book!(line.book_id) end) |> Ecto.Multi.run(:update_book, fn %{book: book} -> Books.update_book(Books.get_book!(book.book_id), %{status: 1}) end) |> Ecto.Mu…

[image] acrolink: I have to start with: Update is a different kind of call, it is better to use though, but still, run requires {:ok, result}/{:error, reason} and I bet that one of those were not.

I think you just need to name your first Multi.run(:get_book... as Multi.run(:book... ?

I wil l try but I believe that is only a name, will not make any difference.

[image] acrolink: I wil l try but I believe that is only a name, will not make any difference. The name is how you reference that step in later steps though. Ecto.Multi very much is a named monadic pipeline. Elixir really needs some monad stuff built in better so umpteen libraries don’t hav…

[image] acrolink: Ecto.Multi.run(:update_book, fn %{book: book} -> It could also be failing on your .get_zzz!s but if it’s that, when corrected it would still fail when you use fn %{book: book} as you need to use a key that refers to a previous multi “step” I guess - I just recently started u…

I have tried the suggestions above, like this: multi_result = Multi.new() |> Multi.run(:bookA, fn _ -> Mango.Books.get_book!(line.book_id) end) |> Multi.run(:bookB, fn %{bookA: bookA} -> IO.inspect bookA Books.update_book(Books.get_book!(bookA.id), %{status: 1}) end) …

Solved.. I have to start with: Multi.new() |> Multi.update(:book, Book.changeset(Repo.get(Book, line.book_id), %{status: 1}))

[image] acrolink: But I am getting the same error message. A couple of things now that I have time to look: Books.update_book(Books.get_book!(book.book_id), %{status: 1}) What is this returning? An {:ok, result} term? Records.update_record(Records.get_record!(book.record_id), %{ …

As @OvermindDL1 states, check the retuning value of the Multi.run functions: Ecto.Multi — Ecto v3.14.0

[image] joaquinalcerro: check the retuning value of the Multi.run functions: Or rather what you return ‘from’ that function. :slight_smile:

[image] OvermindDL1: Update is a different kind of call, it is better to use though, but still, run requires {:ok, result} / {:error, reason} and I bet that one of those were not. When I set the run methods to return {:ok, result} it did not work because in the next line I was getting error l…

Strange error in Ecto.Multi

Questions & Help Questions

OvermindDL1 May 25, 2018, 9:38pm 13

I’m not sure what ‘next line’ is being spoken of though? It doesn’t sound like exiting a run function?