idea Create Unregistered Table GP Tool — Clearer error messaging when unsupported datatype used in ArcGIS Pro Ideas

Create Unregistered Table GP Tool — Clearer error messaging when unsupported datatype used

Bud — Mon, 08 Jan 2024 19:51:38 GMT

ArcGIS Pro 3.2.1:

I have a model that uses the Create Unregistered Table geoprocessing tool. If I accidentally use the model on a file geodatabase, instead of a mobile or enterprise geodatabase, then I get this error:

ERROR 999999: Something unexpected caused the tool to fail. Contact Esri Technical Support (http://esriurl.com/support) to Report a Bug, and refer to the error help for potential solutions or workarounds.

Getting an error is expected in that scenario; the docs and tool description in Pro say the tool is intended for mobile and enterprise geodatabases (implying that file geodatabases are not supported). However, when using the tool in a model (or Python script), the vague error messaging above is not very helpful; it doesn't tell us what the root cause of the problem is.

Could more specific error messaging be added to the tool when it's used on incorrect data types?

Also, could the docs be improved so that they explicitly state that the tool does not support file geodatabases (instead of implying it by omission)? New users might not be aware that it's impossible to create unregistered standalone tables in FGDBs (except when using the File Geodatabase API).

Re: Create Unregistered Table GP Tool — Clearer error messaging when used on unsupported datatypes - Status changed to: Closed

SSWoodward — Fri, 15 Dec 2023 19:19:33 GMT

Thanks for bringing this to our attention. Since this is a bug and not really an Idea, It will be closed. I'll make sure this gets to the team.

Re: Create Unregistered Table GP Tool — Clearer error messaging when unsupported datatype used

Bud — Mon, 18 Dec 2023 06:55:10 GMT

@SSWoodward

FYI - This applies to the Create Unregistered Feature Class tool as well. Same error.

Re: Create Unregistered Table GP Tool — Clearer error messaging when unsupported datatype used

Bud — Mon, 08 Jan 2024 18:20:47 GMT

@SSWoodward

Is this the kind of thing where you sent an email to the appropriate team about the bug, but there’s a chance it could fall through the cracks? In other words, should I submit a case to Esri Support to make sure it gets logged as a bug?

Or was a formal internal GitHub issue already created, and submitting a Esri Support case is not necessary?

Thanks.

Re: Create Unregistered Table GP Tool — Clearer error messaging when unsupported datatype used

SSWoodward — Mon, 08 Jan 2024 19:37:52 GMT

@Bud ,

Great question. You've reached the appropriate team already! I'm an engineer on the geodatabase team and have made sure that an issue has been opened for this bug. Logging a public bug may help the issue get prioritized in our queue, so feel free to do so if you wish.

Re: Create Unregistered Table GP Tool — Clearer error messaging when unsupported datatype used

Bud — Wed, 17 Jan 2024 03:55:06 GMT

Esri Case 03522825: Create Unregistered Table GP Tool — ERROR 999999 when unsupported datatype used

ENH-000164287: Improve error message returned when running the Create Unregistered Table tool in a file geodatabase to provide clearer information and reduce user confusion

Re: Create Unregistered Table GP Tool — Clearer error messaging when unsupported datatype used

KoryKramer — Fri, 09 Feb 2024 15:48:59 GMT

This should have been submitted as a bug. 999999 errors are considered bugs not enhancement requests. Here is the new reference number: [BUG-000164287: Improve the error message returned when running the Create Unregistered Table or Create Unregistered Feature Class tool in a file geodatabase to provide clearer information and reduce confusion.]