Hey Everyone!
We've added the Generate Schema Report tool to ArcGIS Pro 3.2 and want to hear your feedback about it. I've posted a blog post to add context to the project with a brief history and also a look at where we'd like to take it in the future.
We know X-Ray was a much-used tool and hope this can help with some of the same workflows. Moving forward we'll be addressing a key workflow many of you have asked for: The ability to make schema changes in the Excel output and then reimport to create a new geodatabase with those updates. We're hoping to get this into Pro 3.3.
The Schema Report is available now but it's also a work in progress and we'd very much like to hear from you:
Here are some links to related content:
I hope you find the tool helpful. Give it a try and let us know what you think.
Cheers!
Jonathan
REQUEST TWO:
In the HTML report, can the feature datasets be moved into a list of their own instead of being included in the same list as the feature classes? Having them in the same list is quite odd and disconcerting (did XRay have them all in the same list? I can't remember).
I haven't checked yet, but if (non-spatial) tables don't have their own separate list, they probably should.
REQUEST THREE:
I would like to be able to produce a report that shows the differences between two schemas. I think the 'Analyze Differences' tool in XRay used to do this, but I didn't use that tool while I was using Desktop, so not sure what the output was like.
Our schema is based on one of the ESRI models, with some modifications. I would like to be able report on these differences periodically.
Do we really have to use Data Reviewer for this? Seems like overkill. ('Geodatabase Schema Compare' will apparently be available in Dara Reviewer in ArcGIS Pro soon: ArcGIS Data Reviewer product roadmap (January 2024) (esri.com) )
Would be good to enable Feature Dataset(s), Feature Class(es) and Fields descriptions. Because you can't name something like dB 'SchemaReport' if there is no description (?!), then only name enumeration. When the .xlsx report is converted to an XML workspace document the description can be ignored or imported direct into the metadata.
Please enable Feature Dataset(s), Feature Class(es) and Fields descriptions... As a GIS Administrator, ensuring complete metadata—including field descriptions—is a crucial part of our workflow before any dataset is loaded into our enterprise system. With the ArcGIS Xray Add-In, we have been able to document field descriptions, make them available citywide, and publish them to our Open Data site. This makes it easier for staff to understand the data, especially as experienced employees retire and new staff take over responsibility for maintaining the datasets.
Our workflow relies on exporting the Xray metadata as an Excel sheet, allowing the requestor to populate field descriptions before we import them back into the FGDB. This ensures that when the feature class is published, users can access the metadata directly in ArcGIS Catalog to understand field values, data sources, and workflows (whether back-office or mobile collection).
It would be extremely beneficial for the new ArcGIS Pro Schema Report to support Feature Dataset, Feature Class, and Field descriptions. Without this capability, we lose an essential documentation tool that provides transparency and maintains data integrity across our organization. Ideally, when the .xlsx report is converted to an XML workspace document, the descriptions should be preserved or seamlessly imported into metadata.
I would love to see this functionality included so we can maintain our metadata-driven workflows in ArcGIS Pro!
Please add Schema Diagram Capability. SQL, Access, etc., Allow You to have a visual representation of how tables relate to each other. I have not found the way to generate a schema diagram in ArcGIS.
Thank you!
Good morning Jonathan,
will the generate schema report ever be able to be run on just a plain File Geodatabase, or will is always require the registered file geodatabase??
Thanks for the question @LauraleeGann25,
Can you clarify what you mean by a registered fileGDB vs and unregistered fileGDB?
Are you inquiring about registered tables inside of a fileGDB? or something else?