nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcGIS Pro 2.5 bug for displayXY - makes all text fields 5000 characters long!

FionaRenton1

This bug was logged yesterday. It seems like something that should be tested more thoroughly!

BUG-000130643 - XY Table to Point in ArcGIS Pro 2.5 does not retain the number of length for the text field from the file geodatabase table in the output point feature attribute table.

Status: New.

I broke my usual rule of not installing .0 versions of ESRI software!

Najděte více příspěvků označených jako

Accepted answers

FionaRenton1

Fixed in 2.7

All comments

FionaRenton1

Fixed in 2.7

FionaRenton1

ESRI changed their mind after having previously closed this as “not a bug” and will fix this in 2.7 It seems that outputting fields from displayXY with 5000 characters are not acceptable to at least one other person.

The status of Esri BUG-000130643 - In ArcGIS Pro 2.5, the XY Table To Point tool does not retain the length of the text field in the output point feature attribute table. - that you have been associatent Product Plan.
Public Explanation: Duplicate of BUG-000130328: While this was previously a known limit, an enhancement to the Create Feature Class tool and a refinement of the XY Table To Point code will result in the desired behavior in ArcGIS Pro 2.7.
Case Number: 02549047
Duplicate Bug Number: BUG-000130328

FionaRenton1

I agree. I'm reopening the case. I don't believe fields of 5000 characters can have no adverse effects unless they have already tested this with a million records in a map service.

JoshuaBixby

Lame-o response. Basically, it is just too much effort and they don't want to deal with it.

FionaRenton1

ESRI closed this and decided this is not a bug

So it is not in the product plan and is closed.

The response:

"Intermediate datasets are used to process the data. The datasets are created in the 'memory' workspace which makes the process very fast. The memory workspace sets all text field lengths to 5000, which gets transferred to the output. The longer field lengths do not have any adverse effects. To get the original field lengths: - Use CreateFeatureclass to create a new point FC, and specifying the original table as 'template'. - Append to transfer the features in the output of XYTableToPoints to this new FC."

Yeah I get there is a work around, but is this true?

"The longer field lengths do not have any adverse effects."??? Is this true in map services?

Does anyone know how to reopen a bug that is closed or should I escalate it?

FionaRenton1

The bug is still open and the development team are discussing it.

FionaRenton1

Ok thanks. I could not find it and they seems to have closed the Bug so I will reopen the ticket and see what is going on.

Robert LeClair

Fiona - in reviewing the internals I see that the bug listed in not yet fixed in AGP 2.5.1 nor is it listed in our AGP 2.5.x Release Notes I did a search for XY in the Release Notes and found 1 occurrence for a somewhat related BUG in the sense it had to do with the XY Table to Point. Those details are "BUG-000128741 - The XY Table to Point tool fails when the input table has fields with special characters in the names, such as Lat (degree symbol) and Long (degree symbol)."

I don't have the 2.6 AGP Help doc yet as it's not yet released.

BobPool1

I think I may have misspoke adding to this thread. It appears that I encountered this bug using the XYTabletoPoint, not displayXY. When I noticed that 2.5.1 was released and fixed the 'ToolValidator' object has no attribute 'isLicensed' bug I immediately downloaded it and reran my script. It worked! I assume both commands were hitting the same bug.

Not only that I can run the script in my IDE instead of just as an ArcGIS tool. Happy days.

Yes there is a list of bug fixes:

Release notes for ArcGIS Pro 2.5—ArcGIS Pro | Documentation

FionaRenton1

ESRI did not notify me. Is there a list of bugs fixed somewhere?

BobPool1

Hey, it looks like 2.5.1 fixed this bug!

FionaRenton1

You might be right. I was unaware that a text field could be 5000 characters long.

JoshuaBixby

I can almost guarantee that if you didn't install 2.5.0 and report the bug, that it would be waiting for you with 2.5.1.

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.