Help Needed with ArcArcade Attribute Rule in Enterprise Environment

[StefanAngerer]

Hey folks!

I'm facing a problem with an ArcArcade attribute rule in an enterprise environment and could use your expertise. I have a point feature class where the rule should automatically add another point feature when I place a new one. It works like a charm in a local fgdb, but when I try to use it in an enterprise environment, I keep getting this vague error (attached screenshot). The log files are empty too. Any ideas on how I can get this rule to work?

Thanks a ton for your help!

Cheers,

Stefan

This is my Code:

    // Create right geometry for transition pipeline cp
    var tpGeo = Point({
        x: Geometry($feature).x,
        y: Geometry($feature).y,
        z: -0.90,
        spatialReference: Geometry($feature).spatialReference
        })

    return {  
        'edit': [{
            'className': 'PipelineJunction',
            'adds': [
                {'attributes': {'ASSETGROUP': 50, 'ASSETTYPE': 902}, 'geometry': tpGeo, 'associationType': 'content'}
            ]
        }], 
    }

This is the error i recieve:

[Jake_S]

Morning @StefanAngerer ,

Just to confirm, do you know if when the feature was created z -values were enabled? If so you might want to see if the service is z aware.

If you are trying to edit a feature service consisting of point features which are z-aware will result in the error 'Unable to complete operation' when trying to perform the edit operation on that feature service. If the feature service is published without applying the z-value which is based on point feature data and the data is z-aware. Solution to the issue Configure default z-values for editable feature services 

Lets start there se were it takes us.

~Jake

[StefanAngerer]

Hi @Jake_S  and thanks for the quick reply!

The service is in fact z-aware, i also have other rules up and running that place different features at different height values, so i dont think the problems comes from this. Any other ideas from where the problem could come?

Greets!

[Jake_S]

Are those other features in the same database and service? Are there different permissions on those features then this one?

[StefanAngerer]

Hi again,

yes those features are in the same database and service, also I cannot find any different permissions, so I assume no problem there. What could other possible errors be?

Greets Stefan 🙂

[MikeMillerGIS]

I wonder if you need to pass in the M value too.  The point you constructed does not have a M, but the target is probably M aware.

[StefanAngerer]

Hi @MikeMillerGIS,

I thought about that as well, however i found out that the option "Allow geometry updates without M-value" in the server manager is set on true, so this should be no problem i assume. Or am I missing something. Any other Ideas from what this could come?

Greets,

Stefan

[MikeMillerGIS]

I would not trust that setting here. If you set the log files on debug, do they have anything?

[StefanAngerer]

Hi @MikeMillerGIS,

I found somthing interesting. In the debugging window of the diagnostic monitor, I found out that not one rule, that uses the edits keyword is triggered, the only rules that are triggered have the a field selected and dont use any appy edits operation. Is this a hint towards what the problem could be?

Greets,
Stefan

[JohannesLindner]

Maybe use the complete name in line 11? Database.DataOwner.PipelineJunction