2021.1 Not showing the "crosshairs" or the basics for FCF Position

Noticed it only takes the crosshairs out on the template "TEXTONLY_HEADER_EVERY_PAGE.RTP" template.

If I switch to "TEXTONLY.RTP," it does the crosshairs. But my company wants the header on every page for uniformity. 

This is just a guess, but have you tried right clicking in the report window on any of the labels and selected remove object modifications.

This next tip I learned recently from NinjaBadger  here https://nexus.hexagon.com/community/public/pc-dmis/f/pc-dmis-for-cmms/138475/report---1st-page-textreportobject-behavior-in-textonly-rtp-template/806242

This isn't the header every page template here, but the logic should still be the same

Go to File > Reporting > Clear Template Associated Data

I just realized, you were on 2020R1 and went to 2021.1. I believe 2020R2 is when PC-DMIS started using GeoTolerance, and before that it was Xact. Xact is similar, but not the same as GeoTolerance in the background. Before 2020R2 i believe there was no "segments" on dimensions like profile and the like. The migration error you get is probably causing this to happen. Have you tried re-creating the dimension in the 2021.1 application?

I noticed between our two images, yours doesn't have ISO Size or ASME Size in bold. I wonder if it has to do with some things not being used, or maybe this one here.

How does your ASME Tolerance look?

No setting under either one

For ISO Size / Tolerance, and ASME Size / Tolerance there is no settings like how mine looks?

What about the Tolerance ones right above those?

For the SIZE ones mine says Use Template SIZE_TOLERANCE.LBL but I don't know if that's the issue with yours, but note above that it says 

"TRUE_POSITION_INBETWEEN.LBL" but that isn't selected. So that's weird.

Give me about 15 minutes or so, having to close 2021.1 and open 2020 R1 to run an active program. lol

I think the best solution here may be just to install 2021.1 to a different location and steal the reporting files. It would be nice to figure out WHY it happened though.

No worries about needing time.

Would uninstalling 2021.1, then delete the 2021.1 folder under 'Users\Public\Documents\Hexagon\PC-DMIS\2021.1" (where the reporting files are located) then re-install also work?

Or what about running the installer, and choosing to repair?

You can try the repair option first, and see if all your files have the same "date modified" in the folder. Deleting the files after you uninstall is how I would do it if repair does not work.

So backing up here. At a previous company, we went from 2012 MR1 to 2018 R2. We simply copied the template and header from the 2012 Reporting folder to the 2018 R2 folder and set the now copied report template as default. I assumed doing the same thing in this case would yield same results, but with the major change from 2020 R1 to 2021.1 with Geo Tolerancing, this sounds like it is simply not the case.

So backing up here. At a previous company, we went from 2012 MR1 to 2018 R2. We simply copied the template and header from the 2012 Reporting folder to the 2018 R2 folder and set the now copied report template as default. I assumed doing the same thing in this case would yield same results, but with the major change from 2020 R1 to 2021.1 with Geo Tolerancing, this sounds like it is simply not the case.

Yes, that is definitely a major difference, i believe I mentioned it earlier in the thread, but they started using "SEGMENTS" for GD&T in 2020R2

Xact Dimensioning to GeoTolerance

Dumb question, but uninstalling 2021.1 wont affect my current 2020 R1 install?

No, it shouldn't mess with anything related to it

Hmm, so repairing the install did restore the template to original. However when selecting the template, it still shows the TP as a bar and not crosshairs and no summary. 

Selecting the TEXTONLY template makes the TP look like the pic below. Is this how your TP dims look like on your install (masked some info identifying my company/ part#)? 

This is my TEXTONLY on left TEXTONLY_Header_Every_Page on right

Interesting. They are the same, as it should be. Somehow my template is still corrupted then, in terms of the Rule Tree. I wonder if you can try exporting that rule tree and send it to me, and I can see if I can upload the setting here on my 2021.1 seat.

The reason why I choose 2021.1 is because it's the last version that will open very old programs, before WAI/Hex decided to the rolling compatibility described here: Conversion Utilities for PC-DMIS (hexagonmi.com)

Good news, William- the rule tree you sent fixed the issue. The one must have got corrupted when I did the copy/paste.