hi,
i have cought, something what was working well in earlier version,

when you drag and drop the foreign key (not going inside that table columns)
to form

earlier it was possible
to link directly by autoincremented ID,
now it doesnt work.

(in collection that kind of drag and drop works to show that id)

Yes, now in the form, it take the default field if you do that. It is normal.

If you want to see the ID, you need to fork the XML form or the template. ID is always available.
The reason is that it makes no sense to edit ID. so it block it, and also it is much easier for beginners.

Basicaly it is not an issue, just a change.

ok, but i would argue
or me it was usefull,

for example when you have some
insertions from external forked script,

and you want to edit record,
now all forms need to be forked,

the old way to get every column,
and the id was ok,
it had all options,
now it is limited,

Another example:
you have a onlne shop
you dont want to give every order a unique id manually,
you want to attach 2 documents to 1 order
how would you assign them in documents form?
or
you want to serch by order id id orders collection?

For me that modification made some things that were unconfortable
to impossible level (cant bind data without forking) - hard time beginners

I don't understand your point.

Use the FK normally, it is working. Only when you take the FK node in fields tree without opening the node, it will take the default field for making it more easy.
For the search, you are true. I consider I can avoid the fallback and fix that. But for simple FK Filter it takes the default field it is much better for ergonomy.

Do you think that with a Control Keyboard key pressed it in the same time you would like it ? So it would take the REAL id field and not the default field ?

thx

considering usability,
idea thay You have written in another post:

"ID field visible in the list, so you can take it as a normal field. "

would be very intuitive and clear.

I ve been working wiht builder for more than 100 hours and
I love j-cook for data integrity and iterative data binding process
(working out best solution)

Having ID in form makes possible even making many to many realation,
only thing is to upgrade insertion interface,
but before you fork is good to have everting more or less in place,
sometimes you know that after long experimetations and trials.
because to that having id in draft form is essential my opinion.

We can talk a lot, if you like, about ideas and impovents linke nesting collections in tabs,
custom buttons with redirections to pages, and links to collection in modals,
but dont want to lose the point