Unable to use primary key as the detail field in master:detail

Steve,
this restriction is applied to auto-increment field in the detail table.

Selection of autoincrement field is a consequence of bad design of database and these relationships won't work in 99% cases.

Maybe change to a warning then as in this case it's 100% correct to be an autoincrement.
E.g let's say we have an orders system, the order detail record will have a part number, the part number table has an autoincrement ID field which is correct. The order detail record has a partnumberID, I want to allow the drilldown to the part number (there will only be one) from the order detail.

Steve,
auto-increment means that you can't change field value, this value is generated automatically in the database.

When you add new record to the detail table you need to save value from master table in the auto-increment field. It's not good.

You can do it only in MySQL database, but all other databases do not allow to change auto-increment field.
You can use your schema in your project but I'm not sure it's common issue.

This restrictions was added in order to avoid different errors with incorrect foreign keys.

Thank you for understanding.

Hi Jane,
I think you're missing the point, changing the value isn't going to happen, there is no requirement to edit, I just need to allow hover viewing and the view of the full record.
Look at the example and you'll understand.
Any chance you could remove this and replace with a "don't do this" in the documentation or a popup warning in the designer as the ability to do this will be required on quite a few projects I'm working on.

Steve,
I see what you're saying.

Unfortunately we do not plan to change this restriction.