Hi @ShaneONeill_144
To the contrary - to reach out this soon into finding something means I will have to spend a lot of time defining and mapping out every scenario where this may take place. A bug will not be lodged unless our locals can reliably replicate the issue - which we've found with some bugs is not possible due to their IT/security/machine/etc configs.
To protect commercial-in-confidence data I will have to create functional replicas of client data and hope it allows the problem to display itself. As you know, Excel files can get corrupted with no visual or functional cue inside Excel but break anything else trying to read them.
My hope is to ask the question here and find that others have experienced it and that Esri is aware of it and have a simple "update this runtime" or "uninstall this Windows update".
The funny thing is - the files work in QGIS and ArcMap so leaning more towards a Pro issue.
As I've said many times before - It seems that with Pro there is always something going on.
