yeah, dynamic queries are a little tricky… I should have mentioned that earlier…it passed through my mind but I was in a hurry

No problem! it is also in the book so I should have been more careful checking against that too

@tony.kay Would you be interested in a PR to add a support for overriding the default formatter of a column based on its type, similarly as e.g. [:com.fulcrologic.rad.form/type->style->control :instant :default] can be used for a form? (I see it is currently hardcoded in com.fulcrologic.rad.report/formatted-column-value )

@holyjak I am interested in solving the problem of defaults for that yes, and a PR would be great. You’re thinking of putting the lambda to do the formatting in the UI control map? That actually seems pretty reasonable, since you might want to return react elements.

have you thought about how that might also affect read-only elements in forms?

at the moment I’m relying on the form inputs themselves to have a read-only mode…and I think that is probably right. What you’re dealing with is strictly reports

so I guess that is proper

Is :componentDidMount the right place to conditionally load-field! data of the component (excluded from the initial load! via :without) based on the values of some of its props? (imagine a Department component that only loads its Teachers if it isn't the dept of Secrecy)

what happens when it gets passed new props after mounting that should trigger the change?

I am trying to find out how to do this: I want to add a row action to a RAD report that fetches and displays some additional info in a popup. In normal Fulcro, the popup's query would be included in the parent's query and excluded from load! via :without . But I (think I) can't do that with the report. Can I load! the data to a well known location such as :current/details and have a link query [{[:current/details '_] [:details/info1 :details/more-info]}] in the popup component? It would effectively be outside the normal data tree, reading directly from the root DB...