POST
|
@AndrewHayden1 I do not believe the database was ever named just 'SDE'. We have multiple databases within our Enterprise configuration and they've always been named accordingly to properly differentiate. We are planning to go from 11.1 to 11.2 in a few weeks so hopefully this doesn't happen again!
... View more
08-20-2024
01:00 PM
|
0
|
0
|
129
|
POST
|
Hi there. I am attempting to do pretty much the same thing. Do you know if what you described is applicable to Enterprise EB as well? Could you provide more detailed steps (possibly with some screenshots) of what you are describing? I am new to configurations within EB. Thanks!
... View more
06-27-2024
07:06 AM
|
0
|
0
|
297
|
IDEA
|
Just adding another voice to the benefits that this functionality would bring during field collection!
... View more
06-06-2024
01:33 PM
|
0
|
0
|
488
|
POST
|
@MikeMillerGIS Thanks for the script adjustments, I'll give it a go! I didn't know about that matrix; that's really interesting. I guess I never paid much attention to the minimum release information in the design view. I believe we're upgrading to 11.2 later this year. Odd that the minimum release for that rule is showing 11.3 in Pro despite the error prompt saying minimum release was 11.2. The matrix shows 'N/A' for v 1.24.
... View more
05-28-2024
08:00 AM
|
0
|
0
|
474
|
POST
|
@MikeMillerGIS I have tried a handful of checks using examples I've come across but none have worked so far. I might have to create 2 of them because neither a record for Table 1 nor Table 2 will exist when a new feature is created and this script is using Table 1 to get to Table 2. Is there a specific example you could point me to that may work in this scenario? Or something creative you can think of? Also, something that I've never seen before, this particular script/rule (even the functional version that solely updates the Table 2 record) can't be published in my current Enterprise version (11.0). I get an error (00396) saying "The dataset version is later than is supported by your server. Minimum version 11.2". As soon as I delete the attribute rule, the message goes away and all datasets containing all other rules publish without issue. Some of the other rules use very similar scripts...so I'm not sure what it is about this particular script that can't be supported in publishing until Enterprise 11.2.
... View more
05-28-2024
06:29 AM
|
0
|
2
|
482
|
POST
|
@MikeMillerGIS I spoke a little bit too soon. The script I included in my previous message does function how it should, however, only if an existing record is present in Table 2. If there isn't one, I'm not even able to enter an Assembly ID value in the feature class to begin with. I receive a "feature expected" error. This is with the rule trigger being set to only "update" (I tried it with all triggers checked on as well). Is there a way to make the rule only run if a corresponding record exists in Table 2? Or, is there another way to account for this?
... View more
05-24-2024
11:37 AM
|
0
|
0
|
532
|
POST
|
No worries! Your last response did the trick. I combined how you created the variables with part of the attribute rule I was using within a single relationship class. The following works as a two-step "jump" I guess I'll call it. if ($originalfeature.Assembly_ID == $feature.Assembly_ID) {
return
}
var table1FS = FeatureSetByRelationshipClass($feature, "OCGIS.DPW_TESTING_REL", ["Assembly_ID"], false);
var table2FS = FeatureSetByRelationshipClass(First(table1FS), "OCGIS.DPW_TESTING_Secondary_Table_REL", ["globalid","Assembly_ID"], false);
fields to update
var updates = []
for(var f in table2FS) {
if(f.GlobalID == $feature.GlobalID) { continue }
if(f.Assembly_ID == $feature.Assembly_ID) continue;
var u = {
globalID: f.GlobalID,
attributes: {
"Assembly_ID": $feature.Assembly_ID
}
}
Push(updates, u)
}
return {
edit: [{
className: "OCGIS.DPW_TESTING_Secondary_Tabe",
updates: updates
}]
} Thanks for your help!
... View more
05-23-2024
12:50 PM
|
0
|
1
|
555
|
POST
|
Hi Mike - bear with me as I'm just reading about this function for the first time. I also don't know what DML is or how to use it. From the ESRI documentation I'm reviewing, I need to select an Association Type; would this be 'Content' in this case since I'm just dealing with a single value? The examples I'm seeing almost exclusively return a count value as the result, as well. I found this blog post but the example is wayyy more complicated than what I'm trying to do. Would the attribute rule be set on the feature class since it's pushing the value all the way down to Table 2? Thanks!
... View more
05-23-2024
09:59 AM
|
0
|
3
|
569
|
POST
|
I have a feature class related to Table 1 (for illustration purposes) then Table 1 is related to Table 2. The relationship classes are both based on GlobalID to GUID...all datasets are in an SDE environment. Each of the 3 datasets contains the identical field 'Assembly_ID'. I want the 'Assembly_ID' value to be updated in Table 2 when the feature class field is updated. Currently, I have a functional attribute rule that will update the 'Assembly_ID' field in Table 1 when said field in the feature class is updated. I have another functional rule that will update the 'Assembly_ID' field in Table 2 from said field in Table 1 when some other field is updated in Table 1. I don't want to have to perform an edit/update in Table 1 for the value to pass thru to Table 2. Is there a way to pass the value directly from the feature class to Table 2 (I DO NOT want to create a relationship between the feature class and Table 2...that field is the only common field between the feature class and Table 2) OR have the value pass from Table 1 to Table 2, passively, without some trigger being activated in Table 1?
... View more
05-23-2024
09:16 AM
|
0
|
9
|
583
|
POST
|
I am wondering if there is a way to locate all attribute rules present in an Enterprise SQL Geodatabase thru queries in SQL Server Management Studio? Currently, the only way I know how to view an attribute rule in SQL is looking at the definition column within the GDB_ITEMS list. However, you must already know which feature class/table to look at. I would like to be able to view a quick inventory of all attribute rules present in a geodatabase thru a single query of some sort. Is this possible?
... View more
05-13-2024
08:39 AM
|
2
|
0
|
242
|
POST
|
Hi @HusseinNasser2 . I am re-reviewing the previous link/example you provided. In that case, the user was working within a feature class and needed the rule to perform an update based on a common value (GemeindeID in his case) amongst features. I have a 1-to-many relationship where there are multiple table records to a single feature (no common value field; just GlobalID to GUID relationship) and I am transferring values between datasets. I am not sure how to set up the code you used to apply that example to my situation or where to create the dummy field (or how to use it). I'm willing to try using an extra field...assuming the rest of the concept is feasible!
... View more
05-06-2024
08:03 AM
|
0
|
0
|
368
|
POST
|
The 2 rules I've been referring to are not set to fields within the attribute rule settings. I assume this is because the code takes care of everything and this isn't needed. Would specifying the field in the settings - vs leaving blank - alter how the triggering works? I apologize for my naivety with all of this! I'm trying to soak up as much as I can because I find these rules to be incredibly helpful.
... View more
05-02-2024
12:49 PM
|
0
|
1
|
430
|
POST
|
I don't quite understand how this looping occurs when the rules don't involve the same fields. Whether an edit is made by a user or rule, if the rules use totally different fields (with the exception of calling out the relationship) why would they be continuously triggering each other? In my current example - using the code last updated with your help - my 2 rules work harmoniously within the constraint of existing child records. Updates to various fields in both datasets can pass thru they way they're intended to. It isn't until a new related child record is added to the relationship that the parent-to-child rule throws the error.
... View more
05-02-2024
11:46 AM
|
0
|
3
|
442
|
POST
|
Thanks for the quick reply @HusseinNasser2 The adjustment worked a little bit. I was able to get the parent update to push thru given the presence of existing child table records (which immediately prompted the cyclical error previously). However, as soon as I add a new child record and the 2nd rule activates (this rule carries the most current value from a child field to a parent field based on a date field in the child table), the same error is thrown. I did read the example you posted but got lost when the resolution involved creating new fields to accommodate the situation, which I would rather not do.
... View more
05-02-2024
08:56 AM
|
0
|
5
|
457
|
POST
|
I have a basic AR that updates the value in a child table field when the corresponding parent field is updated (Enterprise Geodatabase...GlobalID to GUID relationship). When this is the only AR enabled, everything works as it should. However, when used in conjunction with another AR set on the child table, I receive the error "The evaluation of attribute rules is cyclic or exceeds maximum cascading level" when I update the parent field value. Note: The 2 rules I'm using in conjunction do not use any of the same fields See the code below. Any help would be greatly appreciated! @JohannesLindner @HusseinNasser2 if ($originalfeature.PARENT FIELD == $feature.PARENT FIELD) {
return
}
var fs = FeatureSetByRelationshipName($feature, "RELATIONSHIP CLASS");
var updates = []
for(var f in fs) {
if(f.GlobalID == $feature.GlobalID) { continue }
var u = {
globalID: f.GlobalID,
attributes: {
"CHILD FIELD": $feature.PARENT FIELD
}
}
Push(updates, u)
}
return {
edit: [{
className: "CHILD TABLE NAME",
updates: updates
}]
}
... View more
05-02-2024
07:31 AM
|
0
|
7
|
481
|
Title | Kudos | Posted |
---|---|---|
1 | 10-15-2021 11:37 AM | |
1 | 04-12-2024 10:48 AM | |
1 | 04-12-2024 09:16 AM | |
2 | 05-13-2024 08:39 AM | |
3 | 03-27-2024 01:08 PM |
Online Status |
Offline
|
Date Last Visited |
08-20-2024
09:00 PM
|