Latest Contributions by DrewDowling

‎12-12-2022

@AmirBar-MaorI've opened a case and I'm waiting to hear back. Case number #03219406. Do you want a .bak file from the database? I can also create a user for you if you want to log in and look at the data. It's still a development database. We are supposed to go live this weekend.

‎12-08-2022

@jcarlsonThanks for the suggestion. I logged the event from the Diagnostic monitor but nothing stood out. I don't see any warnings in the log but I do see where the server returned edit operation failed. If I check the ArcGIS Server server logs I see SEVERE Dec 8, 2022, 11:24:24 AM The index passed was not within the valid range.. HRESULT = 0x80040202 Landbase/Landbase.MapServer

‎12-08-2022

Building the parcel fabric in certain extents has started throwing the error: Edit operation failed. ERROR: The index passed was not within the valid range. Adjacent areas build no problem, it seems to be localized. I tried shrinking the parcels to seeds and reconstructing them but the error persists. Has anyone encountered this? We are using version 5 of the fabric and Pro 3.0.3

‎12-02-2022

@DenverBillingI just ran into this issue with an editor yesterday and your post helped me solve it. Thank you. We are changing are workflows so that the very first thing an editor does is run the SLACA tool (love that acronym) against all parcel types in the area.

‎12-02-2022

@AmirBar-MaorOh yes I didn't think about historical parcels. They will have lots of gaps over time. Thank you.

‎12-01-2022

Does the same apply to the must not have gaps topology rule? Should we remove this as well from our topology? And FYI our current workflow is to run a topology check when editing is finished but before a version is submitted to the manager for rec and post.

‎11-10-2022

Thanks for the suggestions @AmirBar-Maor . The sub types in the fabric points are necessary, if I can get them working. Our roads are part of the connection lines and the emergency service agencies have very strict requirements on what they can load to their emergency dispatch CAD systems. Road center-lines need to be covered by an end point, or intersection point in our terminology. And the endpoint and it's road centerline need to be linked by unique IDs. I have a couple of attribute rules that help enforce this relationship on the fabric points that is set to the intersection point subtype. A topology rule has previously helped enforce this. But this is no longer an option as the default Fabric topology rules applied at the class level prevent custom rules at the subtype level. On a related note I think the attribute rules at the subtype level are bugged. They don't fire for me when applied at the subtype level but work fine when applied to the whole feature class. Has anyone reported anything like this? I'm about to file a bug report.

‎10-11-2022

Love the videos. Thank you and keep it up!

‎09-19-2022

@TimHodsonThank you so much for your detailed reply. Sorry for the late response, covid, but I've finally had a change to test using your suggestions and the software interface bug #1 that you mention is the problem that I was having. I changed the subtype code to 2 instead of 0 and everything showed up in the topology properties window. However this lead me to another issue. I can't tailor topology rules using subtypes since the default fabric topology rules create a feature class level rules. Adding a subtype level topology rule for the same feature class results in: ERROR 160172: Topology rules cannot be specified at both the class and subtype level for a given class and rule type. Basically I have a connection line subtype, "Road", that needs to be covered by a fabric point subtype, "Intersection". The default parcel fabric topology rule is preventing this. So I sincerely hope that you allow these rules to be edited in a future release. Finally I think I have found another bug that results when using fabric point subtypes. If I don't set a default point subtype then build parcels tool fails. ArcGIS Server records many topology error messages in it's logs. The workaround was to create a new point subtype for parcel corners and set it as default subtype. After this the buiuld parcels tool worked correctly.

‎08-23-2022

I am having an issue with Topology rules when there are sub types on my fabric connection lines and points. In my model I have 2 connection line subtypes, tie line and road centerlines. But only one sub type is being added to the topology attribute rules when I enable fabric topology. No rule is create for the other sub type and I cannot add others Further more I have 3 fabric point subtypes. I would like to also create custom rules for these type but they do not appear in the the standard topology rules. When I try to manually create or modify rules they are disabled. The attached screen grab shows the default rules that are created. Only the parcel line road subtype is added. The Remove rule button is grayed out and the Add rule button doesn't do anything. No new windows appears for adding rules. So my questions are 1. Are subtypes supported in Parcel Fabric lines and points 2. Is the parcel fabric topology modifiable? I am using ArcGIS Pro 3.0 version of the fabric and I have tried this in both FGDB and EGDB copies of my data.

‎08-03-2022

Sadly this is still an issue.

‎07-14-2022

Did you every find a solution to this? I have a similar issue with RowChangedEvent not firing for any edit on a branch versioned feature service. RowChangedEvent and RowDeletedEvent work fine.

‎07-06-2022

Thank you @jcarlson

‎07-06-2022

My question is about the Create Parcel Records tool. It operates on a singe parcel type. But what happens when a record name already exists for a different parcel type? e.g. If I build parcel records for Subdivisions parcel types then a new record '2021-3586' gets created with related subdivision polys. What happens when I subsequently build parcel records for Lots parcel type that also have '2021-3586' in the record name field? Will they get associated with the existing record? We are still in the planning stages of the migration so I want to know what best practice is in cases like this.

‎06-28-2022

I've run my nextsequencevalue rules as "immediate" rule type instead of batch. Does that make a difference? Also have you checked the log files in ArcGIS server? Sometimes they record more details about the error than the edit window warning shows.

Online Status	Offline
Date Last Visited	‎04-29-2026 12:59 PM

My Ideas

Latest Contributions by DrewDowling

Re: Build parcel bric extent throwing error

Re: Build parcel bric extent throwing error

Build parcel bric extent throwing error

Re: Cannot remove unwanted vertex from parcel line(s)

Re: Fixing "Must Not Overlap" Attribute Rule

Re: Fixing "Must Not Overlap" Attribute Rule

Re: Topology rules and Parcel connection line subtypes

Re: How to extend the parcel fabric information model

Re: Topology rules and Parcel connection line subtypes

Topology rules and Parcel connection line subtypes

Re: Publish a standalone to Enterprise (by reference)

Re: RowChangedEvent or RowCreatedEvent not firing on Split tool in Branch version

Re: Can Fabric records have different parcel types?

Can Fabric records have different parcel types?

Re: Issues with Using Attribute rules to assign parcel number in the Parcel Fabric Service

Re: Recommended startup order (and delay) of the A...

Re: Copy or Export/Import XML fail due to DBMS seq...

Re: Email warnings when Velocity feed fails

Re: How to create a view layer for public facing p...

Re: Tax Parcel Points