Latest Contributions by TerriWaddell1

‎02-22-2023

Hello, We're in the process of migrating to Pro. I have general maps that are "ready to print", such as county-wide political maps, in Desktop. What I want to do is make a project with a single map (say, a specific fire district) but make map layouts for various print sizes (A, B, C, D, E). I've done one so far, and all was fine until I printed. That's when I noticed that the font sizes and line symbol sizes grow/shrink depending on the map being printed, and they look terrible. I need this to NOT happen, or at least, give me some more control over it. Thanks!

‎10-19-2022

Sorry if this chain is going too long, I'm hoping somebody else will find this information useful down the road. First, I tried turning off the INSERT trigger on the rule, then removed the INSERT section from the code. All was well except that there were now no error flags when I created a new feature and forgot to enter a value into display name. Next, I turned the INSERT trigger back on for the rule, and modified the code to return an error message if the DisplayName was NULL. This seems to break everything - - due to the error message, I'm unable to add the missing DisplayName into the attributes pane. It won't let me access the attributes in the pane because the feature hasn't been completed, and it cannot be completed because the attribute is missing. Clearly I'm missing something obvious here but can't seem to grasp it. On insert, I just want it to let me finish creating the feature and then go into to the attributes pane so I can enter everything else. I don't mind that pane nagging me that this field can't be NULL. So where am I going wrong here? Here is my modified version of your code: // Calculation Attribute Rule // field: DisplayName // triggers: Insert, Update if(IsEmpty($feature.DisplayName)) { //When you're inserting without DisplayName, return an error if($editcontext.editType == "INSERT") return {"errorMessage":"DisplayName must not be NULL" } // When you delete the value during editing, restore the previous value if($editcontext.editType == "UPDATE") { return $originalfeature.DisplayName } } // When DisplayName has a value, just return that return $feature.DisplayName Thanks again!

‎10-19-2022

Johannes, Thanks for that code, it was a bit advanced for me at first but I can now follow it and right now it's working, and I'll definitely use it elsewhere! I think the main problem is that the Attribute Table (where I was originally editing) handles the errors differently from the Attributes pane (which Hussein showed in his comment). After talking with staff, we've all agreed that we'll just edit from the pane moving forward and that solves most of our problems for this and future attribute rules as I come up with them. In your code where you have the INSERT option, do you think it would be okay for me to not include that and set the calculation rule to only trigger on Update? The reason I ask is that we don't have default value for these "must not be empty" fields. If I put in the return something like "Hey dummy, don't forget to edit me!" there is no guarantee that we'll actually notice the crazy text if we're doing fast data entry and not really watching the screen. I can have another calculation that looks for the dummy text, but then I have to write more rules to check for that, so just checking for NULL seems easier. Thoughts?

‎10-17-2022

Hello, Bear with me, Arcade is WAY over my knowledge level and this has been a struggle. We have some fields in a feature class that must never be NULL/empty. We will be editing in ArcGIS Pro 3.0, not a service and whatnot. Basically I'm editing directly in the attribute table on an existing feature, and I may enter data in many fields in that feature's row, tabbing between each. I want an error to come up if somebody accidentally empties out the contents of this field. I have come up with the code below for one field, and it's working, BUT, when the error pops up, it undoes any other edits made to that same row in the table, even though nothing was wrong with them/they didn't break rules. This will have staff fuming, so I need a nice/less sledgehammer way to have it flag an error but not undo other typing in other fields. I have tried the code below as both constraint and calculation types and still have the same hard error regardless of which rule type I use. if (IsEmpty($feature.DisplayName) == True){ return {"errorMessage":"DisplayName must not be NULL" } } Can anybody suggest more gentle way to handle errors? Huge thanks!

‎10-06-2022

Just wondering if you'd ever gotten anywhere with running an attribute rule manually? I have the same problem - - I used AUTONUMBER in Attribute Rules but under the manual option because I don't want every feature auto-numbered, just the occasional one. I don't see a way to make an attribute rule when I only need to run it occasionally.

‎10-04-2022

Yes please, we need this! Nobody needs to see our filenames.

‎06-29-2021

I have been struggling with this same problem for about a month. I just wanted to mention that a "repair" on my ArcMap (10.7) installation has fixed the issue for me, at least for now. So that may be an option if anybody else runs into this problem.

‎02-18-2021

I agree - - I've spent hours today trying to fill in the metadata for the few 2020 census files now available and I haven't been able to complete a single one yet. I finally had to give up and move on to other work. Viewing it correctly would significantly help (and an import option would REALLY help!!!)

‎02-17-2021

I don't have metadata in most of our feature classes (I know, BAD GIS person, BAD!). I'll keep the idea above in mind for when I get to that happy time where I am finally been able to work on our metadata. In the meantime, I figured I'd share what I've been doing. It's as clunky as can be, and tedious to keep up with, but I've been making do for now. ESRI, please come up with some sort of management software we can use that does this for us! 🙂 I use Excel simply because it's been years since I've used Access and don't want to spend time to re-learn it and design the database. My column headings are "Feature Class or Table", "Field", "Domain", "Affected Item", and "Item Location". As an example, I have a feature dataset called "Roads" which has a field called "Status", which uses the "Road_Status" domain. For each item in our system that uses the Roads feature class and may be affected by a change to the Status field, and/or the Road Status domain, I have one row entry. So right now, I have 22 separate listings for Roads / Status. Each listing is one of the following: - specific MXDs or projects that would need to be updated if there were a change to Roads / Status. For example, all of our pre-made political maps used by others in our organization have to be updated if there is a change. I list just one "Political Maps" item in the affected item and then the folder where the political map documents are stored in Item Location, because there are hundreds of maps and I have trouble keeping up with this as it is. In the perfect world I'd have one entry for each map, but that's not going to happen any time soon. - vendor-specific items that have to be updated if there is a change to Roads/Status. This might be any 3rd party products you use, ESRI apps, etc. - any automated scripts that run (such as data backups or copying data out for use by your police CAD system, things related to your data upload to the EGDMS or MSAG systems, etc.) - I have a listing to remind me to update the metadata once I finally get to that. - specific/special projects that always have to be updated when there is a change, such as our Road Atlas - Each Data Reviewer check I have that in any way uses Roads / Status. This is where my list gets very long, as this particular item is used in 17 different Data Reviewer checks. - Any procedure documents or other documentation where this appears. So doing it this way has created an absolutely gargantuan Excel file. But what I do is just sort by whatever changed, and then I get a list of all the things that MAY be affected by a particular change. Downside is I've only managed to get items into this Excel file for NENA/NG-911 related feature classes since that has been my sole focus for going on two years now. Eventually I'll get everything else in there. It's also VERY easy to forget to update this file. I would *love* a better/easier way. I hope this at least gives you some ideas, maybe somebody can take this and run with it and come up with something better.

‎02-17-2021

I also have this question.

‎04-23-2020

Thanks for that clarification. We only have one license, so it's back to the drawing board to see if I can better optimize what runs when. Appreciate the answer!

‎04-15-2020

Hello, I'm in the process of setting up my Data Reviewer batch jobs to run as tasks under Task Scheduler. For reference, Task Scheduler calls a .bat file, which calls my Python file. Currently I have 19 of these that need to run, as they each have at least one Data Reviewer check that take several hours to finish. If I were to run them sequentially one after another, it would not finish during the time we have available at night. When I ran them manually, I would open up an ArcMap document for each batch job, then run the batch job. They all ran at the same time in ArcMap without issue (other then really slowing down my computer!) The Python "checks out" the Data Reviewer extension. If I have this same step in each of the python scripts that run, and have Task Scheduler start them 1 minute apart, is that a problem? I wasn't sure if a "checked out" extension means only one of these tasks can run at a time. I've already tried this and several of them run but never seem to finish, while others give a time out error, and others work just fine. I'm trying to troubleshoot if running so many at about the same time is the problem, versus some other random thing I cannot seem to find. Thanks! Terri

‎10-02-2019

Hello, As our needs have changed over the years, we have far more apps, custom tools/scripts/models, Data Reviewer tests, etc., then we've ever had in the past. If one field name or value is changed in our SDE database, it is possible that numerous things downstream would need to be updated to reflect that one small database change. These are a nightmare to keep up with. While we try not to change anything in our database now, sometimes it is inevitable (shout out to all of you who are preparing for NG-911, I feel your pain!) I was wondering how you keep track of all of your agency's data dependencies. I started out with an Excel document that had the feature class name, field name, and domain name, with another column for the "item" that I might need to update if the field or domain changed. It's up to more then 2300 listings and I haven't even finished plugging in the names of all of my Data Reviewer tests. Now I'm leaning towards making an Access database that would run in a similar fashion but be easier to search on; I've done quite a bit of research and other then coming across this link for Item Dependencies (Mapping Item Dependencies Across ArcGIS Enterprise with Python and d3), I haven't found any programs that could help, no useful advice. There has to be a better way. I'd love to hear how you've been keeping track of all of your data and everything tied to it. -Terri Waddell Aiken County Government

‎10-30-2017

I have a polygon layer and a line layer. They are in different feature datasets, so topology won't work here. I need the Data Reviewer equivalent to polygon must be covered by line so that I can find where the polygon and line are not lined up properly. I've been trying different options in Geometry on Geometry with Relations and have had some partial luck but nothing has fully worked. I'm on DR for 10.5 if that matters. Has anybody run into this and come up with a workable solution that I might be able to mimic? Many thanks!

‎01-11-2017

I understand that I can update the attributes with a field calculator, however all new records have this problem which means I have to constantly run field calculates just to get Data Reviewer to stop flagging these issues. I need a way to tell Data Reviewer not to look for this problem at all. I've tried to exclude the problem fields from the domain check but nothing I've tried has worked.

Online Status	Offline
Date Last Visited	2 weeks ago

My Ideas

Latest Contributions by TerriWaddell1

Need layout advice

Re: Attribute rule error message that doesn't undo previous attribute edits?

Re: Attribute rule error message that doesn't undo previous attribute edits?

Attribute rule error message that doesn't undo previous attribute edits?

Re: Execute an attribute rule manually

Re: Add option to remove attachment filename from popup in new Map Viewer

Re: ArcMap 10.4.1 Arc segment features display as line

Re: U.S. Census Bureau TIGER shapefiles released with ISO metadata, can't read it in ArcGIS

Re: How do you keep track of data and item dependencies?

Re: U.S. Census Bureau TIGER shapefiles released with ISO metadata, can't read it in ArcGIS

Re: Can multiple Data Reviewer batch jobs be run at the same time using Task Scheduler?

Can multiple Data Reviewer batch jobs be run at the same time using Task Scheduler?

How do you keep track of data and item dependencies?

Data Reviewer equivalent of polygon must be covered by line?

Re: Domain check has trouble with NULLs

Need layout advice

Re: U.S. Census Bureau TIGER shapefiles released w...

How do you keep track of data and item dependencie...