I have a bit of a strange case here. I have a basic portal that displays what jobs a candidate has applied to. This connects the candidate table and jobs table via a join table that represents each time applied. The portal is for the join table. On the portal I have a button that uses the Go To Related Record command to jump to the related job. This has always worked normally until I converted to FM 12. Now it doesn't take you to the correct job. It usually takes you to one of the jobs in the portal, and that is typically the oldest of the related records. There are no sorting options selected on the relationships. The portal itself is sorted reverse chronolocigally. I tried rebuilting the indexes on the id fields but that didn't do anything. I tried changing the options on the Go To command so it only included records related to that particular candidate. The resulting found set is correct but still goes to the wrong one. Has anyone had a similar issue during their conversion? I could write a new script that takes care of this but I'd rather not have to do that for every Go To that causes trouble.

Try moving the button that is defined to Go To Related Record, up, then down a pixel. This will ensure it is "attached" to the portal. I don't know if this is what's causing it, but I have noticed (in FM12) that placing an object in a portal doesn't always make it belong to the portal - but moving it a little bit usually does.