Extract Values to Points - Error at v3.4 input path contains spaces

[KevinGrootendorst1]

Using v3.4.

It seems the 'Extract Values to Points' and 'Extract Multi Values to Points' now require that the input point features reside on a network path with no spaces.   For previous versions, this was never an issue.

Why has this now changed?  You're forcing people to create interim datasets to work around this new requirement.  Network paths without spaces are not always possible in a corporate work space.

[ChristinaMacNeil]

I am having the same issue but with a different tool - trying to use Snap Pour Point tool and, after several months of using it without any issues, all of a sudden it won't run from our shared folder and I have to create a local copy.  Wondering if there is a fix in the works?

[JérémieTranchant]

Same issue here, incredibly frustrating.

[KatyAppleton1]

---

@KevinGrootendorst1 wrote:

Network paths without spaces are not always possible in a corporate work space.

---

Same is true in a teaching environment. It's frustrating trying to explain this to students who did not have to consider this before we upgraded. Would be great to get some sort of response from Esri as to why it changed and whether it will change back again in future.