Is there a way to access the selected resource_ids within the fields of an action? I'm wanting to show a select that is filtered based on what the user has checked on an index action. On the show action it works great I can use a belongs_to with an attached scope which gives me access to the parent record to filter the dropdown. I've been trying for hours to find a way but I've had no luck, thank you!

I have a field which is a reference to another resource with

:belongs_to

, but I'd like to display a field that is more meaningful than the object id (namely the

:description

field of the associated resource)

Is there a way to make this external_image field link to a resource path? field :photo, as: :external_image, name: "Main Photo" do record.photo.url end

When using

attach_fields

, is there anything special I need to add to my model or controller somewhere? I have the following "Company" field:

tab "Companies" do
                field :companies, as: :has_many, through: :coaster_companyables,
                    attach_scope: -> { query.order(name: :asc) },
                    searchable: true,
                    show_on: :edit,
                    linkable: true,
                    attach_fields: -> {
                        field :role, as: :text
                    }
                # field :companyables, as: :has_many
            end

And when i try to attach a company and type a Role in, I just get Avo stating "Failed to attach Company". No errors in the log, just this line:

rocessing by Avo::AssociationsController#create as TURBO_STREAM
20:58:39 web.1    |   Parameters: {"authenticity_token"=>"[FILTERED]", "fields"=>{"related_id"=>"intamin-amusements", "role"=>"trains"}, "button"=>"", "view"=>"show", "resource_name"=>"attractions", "id"=>"this-one-at-this-place", "related_name"=>"companies"}

Just wondered if i'm missing something before I spin up a demo app.

Hey all. So it looks like on an edit form with a belongs_to, the select box of possible associations can be massive if there is a huge number of possible records that can be associatied (I guess just showing all possible records of the given type?). Is there a lazily loaded/search powered alternative?

Hi all, This is more of a "Is there an option I haven't thought of approach" type of question: Ok, So I have a Company model which is connected to my Attraction and Venue models via a polymorphic has_many : through association. The join model is called Companyable and is used to store the Role that a Company had in a particular Attraction or Venue. This is all great and works in Avo amazingly! Ok, here's where i'm unsure what approach to take. On the Attraction side, I wish to store the Model and SubModel of each one. Models and SubModels are only necessary for SOME companies NOT all. Some Attractions I only have a Model and no SubModel. I'm thinking that I can keep my current associations as they are, but create new Rails Models for Model and SubModel. Then on my edit page I can use the Avo Stimulus functionality to be able to choose a Company, Then a Model, and then a SubModel. In this case I need to find out how to only submit the deepest select box value (eg, don;t submit SubModel if no SubModel was chosen). This sounds like it should work fine, BUT we COULD get to a scenario where an Attraction has a Model and SubModel selected for a Company that isn't associated. This obviously does not make any sense. Ideally i'd like to be able to have the dependent selects ONLY show Companies in the first of the three selects (Companies, Models, SubModels), that have been associated. This is fine if the Model/SubModels are being associated after the Attraction exists, but if i'm creating a new Attraction, due to not being able to attach the Company at creation time, I can't do this. One thing I COULD do is to have some sort of check on the Index view that highlights or tags all records where the Model/SubModel Company does not match one of the regular attached Companies and then i can fix it. I'm trying to build this with Avo in mind. Just happy to hear some other people's thoughts on approaches I could take.

Hello, Just a follow on question to the above. I pretty much have come up with a solution to the above, just now trying to implement a decent UI. What I want is a set of 3 dependent Select boxes. Company => Model => Submodel. I've been tearing my hair out trying to get an example of this working by following the example in this guide: https://docs.avohq.io/3.0/stimulus-integration.html#custom-stimulus-controllers That's great and all but due to some differences in what i'm aiming for i'm really struggling. My associations look like: Companyable: belongs_to :company belongs_to :companyable, polymorphic: true belongs_to :model, optional: true belongs_to :submodel, optional: true Company: has_many :companyables has_many :models Model: belongs_to :company has_many :submodels Submodel: belongs_to :model My Company field on the Companyable Resource looks like: field :company, as: :belongs_to, html: { edit: { input: { data: { companyable_resource_target: "companyFieldInput", # Make the input a target action: "input->companyable-resource#onCompanyChange" # Add an action on change } } } } The Model field on the Companyable Resource looks like: field :model, as: :belongs_to, html: { edit: { input: { data: { companyable_resource_target: "modelFieldInput" # Make the input a target } } } } Just wondering if someone had an example where the fields were

belongs_to

and not `select`s. I'd appreciate a bit of help with getting this up and running and i've been scrabbling for days on this. Sigh

Are fields with a

:has_one

relationship suppose to trigger scope? In the documentation has_many relationships are not suppose to trigger a scope through association, only index. https://docs.avohq.io/3.0/authorization.html#associations shouldn't the behavior be the same for has_one? https://cdn.discordapp.com/attachments/1141725718364045394/1293156682368553021/image.png?ex=67065982&is=67050802&hm=d5a4c19377850d3d5062d60621351eb65357d62470933929e67ef0029a10374e&

Hey everyone, is there a way to filter out specific values to display in the belongs_to select? I would like to display fields of study that are related to selected macro major and not all of them also ideally have field of study greyed out until macro major is selected

class Avo::Resources::Listing < Avo::BaseResource
  # self.includes = []
  # self.attachments = []
  self.search = {
    query: -> { query.ransack(name_cont: params[:q], description_cont: params[:q], m: "or").result(distinct: false) }
  }
  self.title = :description

  def fields
    field :id, as: :id
    field :name, as: :text
    field :occ_macro_major, as: :belongs_to, searchable: true
    field :occ_field_of_study, as: :belongs_to, searchable: true
  end
end

class OccMacroMajor < ApplicationRecord
  has_many :occ_field_of_studies, inverse_of: :occ_macro_major, dependent: :destroy
  has_many :listings, inverse_of: :occ_macro_major
end

class OccFieldOfStudy < ApplicationRecord
  belongs_to :occ_macro_major, inverse_of: :occ_field_of_studies
  has_many :listings, inverse_of: :occ_field_of_study
end

Any way to use tags that have commas in them?

https://docs.avohq.io/3.0/stimulus-integration.html#pre-made-stimulus-methods is there a way to toggle visibility depending on field value (true or false) instead of on click event? in the provided example it does not matter what value is when editing the resource, visibility is updated on checkbox click

Thread automatically created by John Ngo in #1141725718364045394

Thread automatically created by John Ngo in #1141725718364045394

Hello Guys, anyone having trouble to setup default value in fields?

def fields
    field :id, as: :id
    field :name, as: :text, name: "Nome", required: true
    field :email, as: :text, required: true
    field :password, as: :password, only: [:new, :edit]
    field :role, as: :select, enum: ::User.roles, name: "Acesso a plataforma", default: "super_admin", readonly: true
  end

I haven't thoroughly investigated yet, but it seems that the limit restriction on has_many may no longer work. avo: 3.17.3 rails: 8.0.1

field :foo, as: :has_many, scope: -> {
      query.limit(3) # limit does not work
    }

has_many :foo, -> { limit 3 }  # limit does not work

Has anybody built a rating field? Like 4 out of 5 stars (or thumbs, moneybags, skulls, etc)?

Hi, I'm trying to pass a list of id's through to an action like so:

action Avo::Actions::MakeMainPhotoFor,
            arguments: -> do
                {
                    attractions: record.attractions.pluck(:id)
                }
            end

but in the fields method I try to output that and I get the id of a record from a totally different class. Any ideas?

Hey hi hello @lemon-wall-20836 , we've found an odd rendering issue. It's about

index_field_wrapper

where custom ERB content gets ignored when the underlying field value is blank. The

render_dash?

method checks

@field.value.blank?

rather than whether custom content was provided, so users' ERB blocks execute (?) but their output is discarded in favor of showing "—". It creates a confusing UX where providing custom content doesn't work unless you remember to add

dash_if_blank: false

. The option name

dash_if_blank

is also misleading - it sounds like it only controls dash display, but it actually determines whether custom content renders at all. It took me quite a while to figure out why my custom field wasn't rendering, and even then only discovered the fix by analyzing your implementation. The issue also masks errors since the ERB runs but never renders, so you don't get feedback when your custom code has problems. Would you consider checking if custom content exists before falling back to blank detection? Something like:

def render_dash?
    return false if content.present?

    if @field.type == "boolean"
      @field.value.nil?
    else
      @field.value.blank? && @dash_if_blank
    end
  end

Something like that would respect user intent when they provide custom rendering while preserving the current behavior for standard field display.

Hey all, I've inherited a Rails app with a custom admin, which I am switching out to use Avo. Just started off by setting up the basics and i've reached a part where Pages have a Template defined and the template defines what fields each page has. The content is a hash so in my Page Resource I have this: # Dynamically add fields from the template's structure template = record&.template return unless template&.structure_fields template.structure_fields.each do |name, settings| type = settings["type"] case type when "SingleText" field name, as: :text do record.content.fields[name] end when "RichText" field name, as: :textarea do record.content.fields[name] end when "Image" field name, as: :file else field name, as: :text do record.content.fields[name] end end end This dynamically builds the fields for each type. The issue is that when I Edit the Page, those fields do not show up. Any ideas as to why?

Hey guys, how are you? A quick question. The [status field](https://docs.avohq.io/3.0/fields/status.html) works like a text input when creating a new record from AVO. Is it possible to change it to behave like a select with the Model.statuses options? Because I really like how it looks when it's defined as a status in the index view with those well-defined labels.

Hello! Greetings everyone. I need a little help. I am trying to set the default value of a Money field. I use the

default

option on the field and set it using a Money object but it doesn't work. The form only displays

0.00

in the field. I've also tried setting the default value with the

_cents

field or with a static value such as

1000.00

. Nothing works, the value loaded in the form is always

0.00

. This is the code:

field :labor, as: :money, currencies: [ "EUR" ], name: "Labor", required: true, default: project&.default_phase_labor

Any idea what is wrong here? Thanks for the support!

Hi everyone, I'm currently facing an issue when I try to add filterable: true to one of the fields I use. Here is the resource config(Look at the name field):

class Avo::Resources::GamAccount < Avo::BaseResource
  self.title = :name
  self.includes = [:mcm, :currency]

  def fields
    field :id, as: :id
    field :name, as: :text, filterable: true
    field :network_code, as: :text, required: true
    field :account_type, as: :select, enum: GamAccount.account_types
    field :currency, as: :belongs_to, can_create: false
    field :mcm, as: :belongs_to, can_create: false
    field :status, as: :select, enum: GamAccount.statuses
    field :utm_campaign_key_id, as: :text
    field :channel_custom_dimension_key_id, as: :text
    field :blogs, as: :has_many, can_create: false
    field :gam_account_shares, as: :has_many
  end

  def actions
    action Avo::Actions::GamAccountImportKeyValueMetrics
  end
end

I do have ransackable_attributes defined on my model

def self.ransackable_attributes(auth_object = nil)
    ["name"]
  end

But I'm getting the error

undefined method 'avo_dynamic_filters' for an instance of #<Class:0x00007fbbb6bdad20>

Thread automatically created by Arthur in #1141725718364045394

Thread automatically created by Arthur in #1141725718364045394

Hi everyone, how are you? I'm not sure how to address the following: - I have a User STI model (AdminUser and PortalUser) - In AVO, I'm showing both AdminUser and PortalUser as separate resources. - the User model has_many :notifications, class_name: "Noticed::Notification", foreign_key: :recipient_id, inverse_of: :recipient, dependent: :destroy How should I set the has_many field in the PortalUser and AdminUser resources?

resource = Avo.resource_manager.get_resource_by_model_class(@reflection.active_record.name).new(params: helpers.params, view: view, user: helpers._current_user)

undefined method 'new' for nil

thanks!

Hello, Is there a way to re-order attachments in the files field? I have 5 images added to this field on a record, but I need the slightly change the order they are returned.

Hey, I've just done some searching around but can;t find a solution. Is there a way to change the text that appears in the select box for a belongs_to association? I know I can change the title method on the resource, but I wish that to stay as it is. I just need to use another method for the text in the select box.

Restricting the information (not the field) based on policies.

I'm currently wondering a bit about date fields... 1. The fields can be formatted with Luxon tokens. I seriously never heard of these and wonder why you didn't choose strftime, which is the same as Rails uses, or why you are not reusing rails localize method? (https://www.bairesdev.com/tools/strftime/) 2. When using the luxon token

cccc

, which should give the day of the week like

Wednesday

, this is not translated into my locale, but will always be english... 3. I could work around this by using

format_display_using

, but this does not seem to exist for this field type? 4. I wonder if we could have an option to disable flatpickr on desktop, too, as I'd prefer the native date pickers there (native datetime pickers are another story, firefox still only has a very basic one, but the date pickers are all right). They are also more accessible and work natively when testing with capybara.

I wanted to add a style-attribute to a file field, to make the image smaller. I read https://docs.avohq.io/4.0/html.htm and added a style, however, it is ignored. The simple test case with a text field:

field :city, as: :text, html: { show: { content: { classes: "my-test-class", style: "background: red; text: white;" } } }

This applies the class, but not the style. Looking at https://github.com/avo-hq/avo/blob/main/app/components/avo/field_wrapper_component.html.erb, I can see that style, data and classes are applied on lines 3-5 for the wrapper component, and the classes and data being applied for the content on lines 22 and 23 - but it seems like the style was simply forgotten there? 😅 (Same for the label) Besides that, is there an easy way to make the preview image for a file field smaller? E.g. 512px squared, currently it takes up all available space 😄