I do something similar, but I transact a new record into that ident before calling route-immediate …

:will-enter            (fn [app {:keys [sv-id] :as params}]
                            (let [is-new?      (= sv-id "new")
                                  sv-id        (if is-new?
                                                 (make-tempid)
                                                 sv-id)
                                  sv-ident     [:org.riverdb.db.sitevisit/gid sv-id]
                                  editor-ident [:component/id :sitevisit-editor]]
                              (log/debug "WILL ENTER" sv-id "NEW?" is-new? "PARAMS" params)
                              (when is-new?
                                (comp/transact! app `[(merge-new-sv ~{:sv-ident sv-ident})]))
                              (if is-new?
                                (dr/route-immediate editor-ident)
                                (dr/route-deferred editor-ident
                                  #(f/load! app sv-ident SiteVisitForm ...

the down side is that :will-enter runs 3 times so I’m creating 3 temp entities in state every time. I haven’t figured out yet a better strategy … maybe do a route-deferred and create the temp-id in the handler fn

I see that you do ± the same thing as me but I still don't understand how is the information [:org.riverdb.db.sitevisit/gid sv-id] combined with the component's query to make a query that can be resolved against the DB....

The router reads the component’s query and then uses that to read the ident location

is that what you mean?

the router changes its own query tree based on which component is currently active by reading the component’s query and then updating its own query tree with that new branch, and removing the branch of the old path

so you just need to make sure that data exists in the DB at that ident that fulfills the component’s query, and it will work

So the router changes its own query (in your case) to ...{[:org.riverdb.db.sitevisit/gid 123] (get-query current-target-lcass)}... ? I do not see that. What I see is

{::current-route `(comp/get-query ~(first router-targets))}
(map-indexed ... {(keyword (str "alt" idx)) `(comp/get-query ~s)}

App State is organised by ident so use Fulcro Inspect and think in terms of idents. There might be several components in one ident family.

Hm, I have PersonList with :ident :list/id and in the DB there is :list/id {0: .., 1: ..}which is the data from the initial state . But what props does the PersonList displayed on the page have?

The displayed one will be one of the ids (or many of them if it is a component that displays many). Each 'row' will have data determined by the query on the component.

In theory yes. But in practice the list is showing empty, so it is missing some props. That's why I would like to see the props it got - but don't how to. Perhaps the only solution is to add (println props) to its code...

Yes - but doing so will just be verifying that you don't have a rendering problem. Are you saying each row only has :list/id and there should also be :list/name etc.?

Which row??? The DB contains the data it should. But my component has an empty body. So there is something wrong in the transitions of values from the client db into the component (which I have put under a router, see my previous question, though there I mention Person not PersonList)

The id (of the ident, the second thing in it) gives the row, you can print it from the component rendering function.

There shouldn't be rendering problems if you use:

:optimized-render! keyframe-renderer2/render!

(or keyframe-renderer for that matter).

For printing purposes de-structure the id from the props.

In Inspect are the props in the list’s parent? If so, then they’re not getting passed to the list component. You can proceed in this manner through the tree to your component.