| Bug ID Number |
BUG-000158869 |
| Submitted | June 6, 2023 |
| Last Modified | May 1, 2025 |
| Applies to | ArcGIS Pro |
| Version found | 3.1.2 |
| Operating System | Windows OS |
| Operating System Version | 10.0 64 Bit |
| Status | Under Consideration
The issue has been reviewed by the development team. It has not been prioritized into a release plan and will be monitored to determine its overall impact. Factors that are considered in the prioritization process include the number of users affected or requesting the functionality, business impact, whether a workaround exists, among others. If a bug is adversely affecting your business, see How To: Escalate a defect (https://support.esri.com/en/technical-article/000024129).
|
Workaround
First workaround:
- Exit the tool by clicking the back arrow in the top left corner of the geoprocessing window to reset the parameters.
- Open the tool again and use the COA_FC_NoSpacesInAlias table as the Input Event table.
- Tool Parameters
- Input Event Table: COA_FC_NoSpacesInAlias
- Input Event Table Properties
- Route Identifier Field: route_id
- Event Type: LINE
- From-Measure Field: from_measure
- To-Measure Field: to_measure
- Overlay Event Table : city911_locatefeature
- Overlay Event Table Properties
- Route Identifier Field: RID
- Event Type: LINE
- From-Measure Field: FEMAS
- To-Measure Field: TEMAS
- Type of Overlay: Intersect
- Output Event Table: <a valid table name>
- Output Event Table Properties
- Route Identifier Field: route_id
- Event Type: LINE
- From-Measure Field: from_measure
- To-Measure Field: to_measure
- Check all boxes
- Click run
The tool now successfully completes.
Second workaround: Use the python window and use the python tool syntax to run the tool. This can be done with the table that has spaces in the field aliases.
Third workaround: Do not fill in the Output Event Table properties and running the tool with the table with spaces in the field aliases.
Steps to Reproduce