Yes, I had gone into Certs to test this out, each step of the way. Here's what I found:
https://d2r1vs3d9006ap.cloudfront.net/s3_images/1789042/RackMultipart20190513-94048-1lfyx8b-Cert6_inline.JPG?1557754840" width="194">
When I built the form for Certs, I listed all 9 jurisdiction spaces with their own name (Jurisdiction1, Jurisdiction2, etc). I had each one tie to the Jurisdiction name field and was not getting the pre-fill I was expecting.
So after going thru the relationship creation process again, I realized that now I had the choice of Related Jurisdiction plus my field names from the Jursidiction table available in blue.
So in the example above, I selected the all-caps JURISDICTION that was in blue, and replaced "TaxRate1" and "Address1" with the blue "Jurisdiction-TAXRATE" and "Jurisdiction-JADDRESS". That does lead to the expected pre-fill.
https://d2r1vs3d9006ap.cloudfront.net/s3_images/1789045/RackMultipart20190513-128916-1efintd-Cert7_inline.JPG?1557755703" width="240">
">https://d2r1vs3d9006ap.cloudfront.net/s3_images/1789046/RackMultipart20190513-54513-35rtob-cert8_inline.JPG?1557755783">
I have since replaced JURISDICTION with the "Related Jurisdiction" field making the relationship created and getting the same result, which is what I expect I was to do in the first place.
Now I have 8 Jurisdiction fields left to fix - "Jurisdiction2," etc. I know that I cannot select "Related Jurisdiction" again so what is my next step? Do I create the relationship again, do I copy Related Jurisdiction? And since I know that TAXRATE and JADDRESS in blue will copy all the way down the page if I use them in all 9 instances, how do I prevent that from happening when I select my second jurisdiction, since there were no "Related Rate" or "Related Address" fields created in the relationship?