topic Re: A requested row object could not be located-Attribute rule for calculating and update value on relationshipclass. in Attribute Rules Questions

A requested row object could not be located-Attribute rule for calculating and update value on relationshipclass.

anilkumar — Tue, 14 May 2024 15:25:50 GMT

Hello all- I am working to set up our attribute rules. I would like to create a rule that will copy edited row of a feature class to another feature class when there is a status change from Attribute values. am following this error based on code provided in the forum: EW is relationshipclass maintaining parent GLOBALID(as CGUID) and comparing anc evaluating new lstatus

I am getting an error "

Update table row : EL
update table row failed.
A requested row object could not be located.
Rule Name : AR23
Triggering Event Update

ClassName: EL,
GlobalID :{XX--xx}"

Re: A requested row object could not be located-Attribute rule for calculating and update value on relationshipclass.

HusseinNasser2 — Tue, 14 May 2024 15:50:38 GMT

The error essentially say you tried to update a feature that doesn't exist. So we need to debug to see what the rule is passing..

I see you are using 2.9.10, is it possible to move to 2.9.12? we included many fixes for attribute rules and relationships there plus we also included the ability to print the console output to the debug diagnostics in Pro.

I included the updated rule with few changes..

Run the rule while ArcGIS Pro monitor is running (debug mode) (CTRL+ALT+M), and look for the console output , I added **** to make searching easy, see what output you get, this will tell us more.

Re: A requested row object could not be located-Attribute rule for calculating and update value on relationshipclass.

anilkumar — Tue, 14 May 2024 21:14:04 GMT

Thank you for the details.

currently am receiving an error message 'object not found updates' . As per your code, not wanting to update GLOBALID( here in child (relationship class ) which is CGUID. CGUID is mtaching with Parent GlobalID already. Only need to update lstatus as updated the records related to parent.

Re: A requested row object could not be located-Attribute rule for calculating and update value on relationshipclass.

anilkumar — Wed, 19 Jun 2024 18:05:07 GMT

Thank you for the inputs. I am unable to proceed with versions other than the current one. However, after testing, I found that the provided code does not produce any errors or the desired results. I have made the following updates. Could you please review? Additionally, note that CGUID is a child table field being compared with the parent feature’s globalid. I want to update the ‘LSTATUS’ attribute of the child feature (EW) to match the value of the parent asset’s LSTATUS when a user updates it.

Re: A requested row object could not be located-Attribute rule for calculating and update value on relationshipclass.

RavindraSingh — Fri, 28 Nov 2025 08:52:46 GMT

@HusseinNasser2I’m seeing the same error on the UN's ElectricDevice feature layer in a feature server while executing Calculation rule. Tried console() for logging in ArcGIS Pro, but no messages are being printed.

I am using ArcGIS Pro 3.3.1.

Background: In this calculation rule, I am returning edit payload to update three feature layers,

1. Another feature than $feature in ElectricDevice

2. ElectricJunction

3. ElectricLine

I this is the only calculation rule applied on ElectricDevice feature layer

Below is the error message:

Re: A requested row object could not be located-Attribute rule for calculating and update value on relationshipclass.

HusseinNasser2 — Fri, 28 Nov 2025 10:17:35 GMT

Yes this error means the globalid you passed to the dictionary to update a feature doesn’t exist. You can avoid this by querying the layer and verify that features exist.

Before you return the dictionary, do a console and enable logging on Pro arcgis monitor to see the arcade messages.

if this is service enable debug on arcgis server manager.

alternatively a trick I like to use is to return error message to force the rule to fail and display the message.

return {“errorMessage”: text(thedic) }

Re: A requested row object could not be located-Attribute rule for calculating and update value on relationshipclass.

RavindraSingh — Fri, 28 Nov 2025 14:28:01 GMT

Thank you @HusseinNasser2 for your input, it helped me to resolve the issue. However a console was not visible after enabling logging on Pro arcgis monitor to see the arcade messages.

Root cause: I was making edit return as:: {"edit": [{"className": "ElectricDevice", "objectid: 1234, "attributes": {"status": 4}}]}

Solution: As a fix I am now using "globalid" instead of "objectid" to uniquely denote the feature being edited as below:

{"edit": [{"className": "ElectricDevice", "globalid: "{dfd-23cf-dfd-dsf-3434df}", "attributes": {"status": 4}}]}

Reason I was using objectid earlier: Sometimes I encounter cyclic errors in certain calculation rules when using globalid. However, when I switch to objectid, the cyclic error does not occur. I’m not sure of the reason behind this behavior, but it’s something I’ve observed.

As a practice what shall we use 'globalid' or 'objectid'? I would appreciate your inputs, if you can suggest possible approaches to overcome the cyclic error?