Ash Framework•4mo ago

Creating a resource from another endpoint

Hey everyone! I’m running into a bit of a challenge and could use your input. I have an endpoint called locations, and I want to allow users to create leads as part of a POST request to: {{url}}/api/json/location The idea is to allow creating a location along with multiple leads in a single request. Here's an example of the payload I’m trying to send:

{
  "data": {
    "type": "location",
    "attributes": {
      "name": "Test Lead",
      "location": {
        "lat": 32323,
        "long": 23232,
        "address": "dsdsds"
      },
      "images": ["url1", "url2", "url3"],
      "leads": [
        {
          "type": "lead1",
          "description": "description1",
          "priority": "1"
        },
        {
          "type": "lead2",
          "description": "description2",
          "priority": "2"
        }
      ]
    }
  }
}

{
  "data": {
    "type": "location",
    "attributes": {
      "name": "Test Lead",
      "location": {
        "lat": 32323,
        "long": 23232,
        "address": "dsdsds"
      },
      "images": ["url1", "url2", "url3"],
      "leads": [
        {
          "type": "lead1",
          "description": "description1",
          "priority": "1"
        },
        {
          "type": "lead2",
          "description": "description2",
          "priority": "2"
        }
      ]
    }
  }
}

- What I’ve Tried Checked Ash JSON API relationship manipulation docs - Attempted to manually create the leads inside a change block using Ash.Changeset.manage_relationship/4 relevant code:

# my domain
#... code for doamins 
      base_route "/location", ProjectX.Leads.Location do
        post :create
      end

# my domain
#... code for doamins 
      base_route "/location", ProjectX.Leads.Location do
        post :create
      end

---

# location resource
  actions do
    create :create do
      accept([:name, :location, :images])
      argument(:leads, {:array, :map}, allow_nil?: true)

      change(fn changeset, _ctx ->
      # should I do it here
      end)
    end

# Ash.Changeset.manage_relationship(changeset, :leads, leads, type: :create) # should I do it as a relashionship?


  relationships do
    has_many :leads, ProjectX.Leads.Lead
  end
end

# location resource
  actions do
    create :create do
      accept([:name, :location, :images])
      argument(:leads, {:array, :map}, allow_nil?: true)

      change(fn changeset, _ctx ->
      # should I do it here
      end)
    end

# Ash.Changeset.manage_relationship(changeset, :leads, leads, type: :create) # should I do it as a relashionship?


  relationships do
    has_many :leads, ProjectX.Leads.Lead
  end
end

45 Replies

bod123OP•4mo ago

# lead resource

  actions do
    defaults([:create])
    # create :create do
    #   accept([:type, :description, :priority])
    # end
  end

  attributes do
    uuid_primary_key(:id)

    attribute :type, :string do
      allow_nil?(false)
      public?(true)
    end

    attribute :description, :string do
      allow_nil?(false)
      public?(true)
    end

    attribute :priority, :string do
      allow_nil?(false)
      public?(true)
    end

    attribute :location_id, :uuid do
      allow_nil?(false)
      public?(true)
    end
  end

# lead resource

  actions do
    defaults([:create])
    # create :create do
    #   accept([:type, :description, :priority])
    # end
  end

  attributes do
    uuid_primary_key(:id)

    attribute :type, :string do
      allow_nil?(false)
      public?(true)
    end

    attribute :description, :string do
      allow_nil?(false)
      public?(true)
    end

    attribute :priority, :string do
      allow_nil?(false)
      public?(true)
    end

    attribute :location_id, :uuid do
      allow_nil?(false)
      public?(true)
    end
  end

the close that I am rg is getting the following:

  "errors": [
    {
      "code": "required",
      "id": "8c27cdcc-2b61-4d77-a9c3-d30937fc6d29",
      "meta": {},
      "status": "400",
      "title": "Required",
      "source": {
        "pointer": "/data/attributes/leads/0/type"
      },
      "detail": "is required"
    }, ///......

  "errors": [
    {
      "code": "required",
      "id": "8c27cdcc-2b61-4d77-a9c3-d30937fc6d29",
      "meta": {},
      "status": "400",
      "title": "Required",
      "source": {
        "pointer": "/data/attributes/leads/0/type"
      },
      "detail": "is required"
    }, ///......

This seems odd since "type" is clearly included in the payload. I’m not sure if I’m missing something in how the leads are being parsed or managed. - Should I use manage_relationship/4 inside the change block to handle the creation of leads? - Is there a better pattern for handling nested creates like this in Ash? - Do I need to change something in the relationship or action definitions? Thanks in advance! 🙏 Any pointers are appreciated.

Gaming

Programming

Creating a resource from another endpoint

Did you find this page helpful?