New Field Types in 3.2 Make FGDBs and FCs appear locked to earlier versions?

valenj88

Not only does Pro 3.2 make it impossible to publish services to Enterprise 11.1 or earlier due to these new field types, if 3.2 publishes ANY featureclasses to a FGDB it renders that FGDB inaccessible to any other versions of Pro.  Furthermore, any FCs published to SDE are also inaccessible (thankfully it doesn't kill access to the entire database) to any versions below 3.2.  This has killed a ton of our automated scripts and resulted in having to revert to Pro 3.1.  Is there a fix planned to not force the use of new field types that are unavailable to earlier versions of Enterprise/Pro?

MErikReedAugusta

To clarify: Do you mean these FCs are version-locked even if you don't use the new data types?

Because that's going to be make convincing our IT department to finally roll out 3.2 that much more difficult.  And there's quite a bit of functionality in 3.2 that I've been waiting for, but we're still currently stuck on 3.1.3.

At least with things like Attribute Rules that are Pro-specific, you only get version-locked when you finally "pull the trigger" and add your first rule, so we haven't booted our lingering Desktop users, yet.