Latest Contributions by JenniferKennedy

Okay, thanks for the confirmation!   ... View more

Is this still applicable in the software today?  Run a longer process so you have time to uncheck that box? ... View more

Is this still true?  Is the only way to reset this setting to run a tool that takes a longer time to process, so you have time to uncheck that box on the running tool? ... View more

Are you working in ArcMap, or in ArcPro?  If you're working in ArcMap, check out X-Ray for ArcCatalog.  If you're working in Pro, there currently is no X-Ray equivalent at the moment, but there is an idea for X-Ray in ArcPro that you could vote for. X-Ray allows you to do this.  I would still recommend mocking up your "base" feature class - one that has all the standard fields you'd be adding to every feature class - in ArcMap or ArcCatalog.  Once you have that, you could use X-Ray to interrogate it, create a data dictionary and several Excel spreadsheets that you can use to update the schema.  At that point, you can make updates - adding new fields, specifying the data type and other properties (like field length, for text fields, etc.) in the Excel.  Then you'd save it, and import that new schema to a blank File Geodatabase. If you're using ArcMap and want more information about how to do this, don't hesitate to ask.  I use X-Ray a lot for developing and modifying schema. ... View more

Watching this thread for future discussion.  Unfortunately I don't know the answer, but on a related note, there is an idea for X-ray for Pro.  While this doesn't help us now, it would be useful to have.  I use X-ray a lot with ArcMap to export schema and data dictionaries. ... View more

Could you provide your data, or an example of what the data looks like?  Without a little bit more information about the data model, it's a little difficult to offer advice. However, even without more information, I'd suggest looking at the Summary Statistics tool (edit: here's the Pro documentation for this tool). It's a very powerful tool for summarizing data.  For example, if you have multiple records associated with one point, and you need to add up all the values in a field from the multiple records for each point, you can use the Summary Statistics tool to do it. If the Summary Statistics tool does turn out to be useful for you, then you can join the output of that tool back to your point features.  Of course, if you need these summaries to update based on changes to the CSV data, then you'd have to run the tool again, or devise some other methodology. ... View more

Thanks - that's good to know!  As a side note, in the current software (or at least 10.5.1 and up) - you can at least configure the Job Types and map templates not to repoint some layers.  This gets around needing to put layers in a basemap grouping, in order for them not to break when WMX launches ArcMap.  That's very helpful when you have reference data layers that come from sources other than your primary editing data source.  It would not necessarily solve all problems, if you really do need to repoint to multiple sources or create versions in multiple databases, though (that's not a use case I currently have). ... View more

That's essentially correct, the Data Reviewer table, by default, will just record the OID, the feature class name (origin table) and the Field Name that has the invalid value (in the Description/REVIEWSTATUS) field.  But... there is a workaround you could use.  This may not be helpful if you have a lot of different fields.  But it is possible to add user-defined fields to the Data Reviewer table.  You could, for example, add a MATERIAL field and PRESSUREZONE field to the Data Reviewer table, and then any results written to the Data Reviewer table that have those fields will get the field value added as well.  So, if a record had an invalid MATERIAL value, it would be returned as a result by the domain check, and the MATERIAL value would also be written to the Data Reviewer table.  You would, however, still need to use the REVIEWSTATUS field to determine which of the added fields had an invalid value.  ... View more

I do use Workflow Manager (WMX) and Data Reviewer a lot - but I've never auto-generated a report.  While I haven't tested this recently, I'd be surprised if a new tool for exporting the report has been added (looks like it doesn't exist in 10.6.1, in the Data Reviewer toolset).  While WMX can indeed be automated to various degrees, and while it can create Data Reviewer sessions and run batch jobs, I don't believe it has a built in way to generate the reports.  Well, let me clarify - WMX does have a reporting function - so maybe it does to some degree; but it would not be an easy GP tool button-click "export report"; you'd have to do extensive formatting and some SQL work to get the results you need (to the best of my knowledge). You do also have the ability to do those things mentioned - create a DR session, run DR batch jobs - outside of WMX, with the Data Reviewer GP tools.  That could definitely be run by a ModelBuilder tool, or a python script.  That toolbox does not have a tool for generating the report, though (in 10.6.1, that I can see). If you have python skills, it probably would not be impossible to interrogate the Data Reviewer workspace itself, perform some joins and export the Data Reviewer results to an Excel sheet.  One of my coworkers, I believe, has made tools that act on the Data Reviewer workspace and generate some derived outputs - exporting and reformatting the Data Reviewer results so that clients who don't have Data Reviewer could review the results.  Unfortunately I don't believe we've created a tool to generate a report, though. ... View more