| 不具合 ID 番号 |
BUG-000174960 |
| 送信されました | March 12, 2025 |
| 最終更新日 | June 24, 2025 |
| 適用対象 | ArcGIS Pro |
| 見つかったバージョン | 3.4.2 |
| オペレーティング システム | N/A |
| オペレーティング システムのバージョン | N/A |
| ステータス | As Designed
開発チームによる確認後に、この動作が設計どおりであると判断されました。 詳細については、「参考情報」セクションをご参照ください。
|
参考情報
This is by design.
In 2.9.13/3.x we fixed a bug with relationships and attribute rules where the rules were not triggering. That is why it "worked" in 2.9.3 because the rule was never triggering.
Now with the fix, the Add new to relationship translates to two edits
-> create a new row on the destination
-> update the row to set the foreign key (this didn't happen before which was not correct)
the second update doesn't have field value populated which causes the attribute rule to fail.
To fix this you have can allow the update to happen if the foreign key is being updated by changing the rule as follows
//prevent the edit only when the user makes an update, not when the foreign key gets updated
if ( $feature.field == null && ($originalFeature.foreignkey == $feature.foreignkey) ) return false;
//else allow the edit
return true;
alternatively you can set a default value for "field"
対処法
Open the attribute table of the feature class, select a row or feature and click the Menu button (three lines) in the upper-right corner. Navigate to Related Data, select the related table and add rows directly.
再現の手順