I have a calculation attribute rule that runs without errors, but doesn't work as expected:
Attribute rule works in Pro 2.9.2, but not in Pro 2.6.8
I want to debug the code, to see what part of it is failing to update the geometry's vertices.
Does anyone have any tips for debugging Arcade code in that scenario?
Bud,
I believe you can use the error message to your advantage. If the code has an expected return value you can use it to print the value as text.
return{
"errorMessage": Text()
}
Although this may not work if the rule you have is doing something geometry-related.
~Jake