Select to view content in your preferred language

Verify test data

442
12
3 weeks ago
CarlaNardinocchi
Emerging Contributor

Hello everyone,

I am having the following problem.

I have a parent feature layer (globalID) and 4 child tables (parentGuid).

I wrote this simple arcade expression to access the related table attribute:

var relatedrecords = OrderBy(
    FeatureSetByRelationshipName($feature, "TabellaDifetti"),
    "Data DESC"
);

var cnt = Count(relatedrecords);
var output = "";

if (cnt > 0) {
    var info = First(relatedrecords);
    output = 'etichetta: '+ info.Numero_albero
}
return output;
 
 
It works fine for 3 tables but not for the last one. I get the following Result: Test execution error: Unknown Error. Verify test data.
 
I am sure that the problem is in the table and not in the code, but I cannot imagine what it could be.
I have checked:
- the relationship is the same for all the 4 tables (simple, 1:M, forward) built in ArcGIS Pro and shared in AGOL
- I can see access to the related table from the parent feature
- the table should not be corrupted: I accessed to the record directly from the popup of the layer table and I can read it (using $feature.Numero_albero)
- I try to output the Text(info) and I get the same error...
 
This table has 1250 records and 1250 record, the type is integer or string and one date. The only difference from the other one is that the strings are 8000 character long, but ...the problem is also present with the numeric type.
 
Do you have any suggestion that I can check?
 
Thanks, carla
0 Kudos
12 Replies
AustinAverill
Frequent Contributor

Try returning them as just as the variable, without the Text() method. This should allow us to see what data is present in the featureset. 

0 Kudos
CarlaNardinocchi
Emerging Contributor

I re-imported the csv table into ArcGIS Pro, did everything again, this time reducing the size of the fields via the schema.ini file. I don't know if this was the problem or not, but now the expression is valid.

I can move on.
Thanks a lot for the advice @AustinAverill and the support

0 Kudos
AustinAverill
Frequent Contributor

Must have been some sort of issue like that! Very odd, but glad you were able to resolve it!

0 Kudos