FacilityTypeApprovedProducts should not point to a specific version of an orderable. They should just reference the orderable by its ID.
From the mailing group:
FTAP should not need to reference an orderable by its version. The reason why it does that in this case is because of how our database schema is set up. FTAPs have a foreign key to the orderable, so when we made a new composite primary key of orderables, including the version id, the foreign key also had to reference the version. If we do drop the reference to orderable by its version, we’ll need to do that by removing the foreign key altogether.
FTAPs do not reference orderables by their version anymore
all FTAP endpoints should work as expected
response body should always contain the newest orderable
it is impossible to create FTAP with non-existing orderable - a user should get a meaningful message
Orderable update remains to work correctly
orderable id should not be changed after update
orderable version should be incremented
update does not affect the related FTAP