AttributeTabEmbeddableControl on Feature Service Layer

[JimmyBowden]

I have created an add-in with an AttributeTabEmbeddableControl, following the instructions at ProConcepts Editing · Esri/arcgis-pro-sdk Wiki · GitHub. The control works as expected on a file geodatabase source (First image) but doesn't work when the layer source is a feature service (Second Image). I have only tested in Pro 3.3.1. Is this expected behavior or is it possible I'm doing something wrong. I have attached the project

[GKmieliauskas · Accepted solution]

Hi,

It was registered bug some time ago, but support page is not accessible.

I have tried your code and it works only with File Geodatabase (gdb).

[NicolasAugustin]

Hello

Is there any update about this issue ? I have compiled @JimmyBowden code on 3.3 and it does not work for SHP based layer
Any hint or update about this issue ?
Thank you

[RussellBrennan]

The ActivationExtension pattern only works with geodatabase datasets and feature services. For feature services this pattern is currently limited to feature services published referencing geodatabase datasets and is not working for Hosted feature services in Enterprise and Online

[JimmyBowden]

I contacted tech support and they said it was NOT the same as the bug reported and created a new bug BUG-000175139.

[DrewDowling]

When I look up BUG-000175139 it says it is a duplicate of ENH-000173660 . However I can find no information on ENH-000173660. Is this bug fixed in any release? I'd like to create a custom inspector panel for a feature service using Pro 3.5 but need to know if the bug is fixed before I start development.

[NicolasAugustin]

Hi

I'm in the same situation that you were.
Did you get any confirmation ?
I'm using version 3.3

[RussellBrennan]

Hi all, 

BUG-000175139 was logged as an issue related to ArcGIS Online feature services and following the AddActivationExtension pattern for custom behavior. This pattern is already supported for feature services published by reference to Enterprise.

ENH-000173660 is to support the ActivationExtension pattern with AGOL based feature services, this has not been implemented yet. I would consider reaching out to Support to get your account attached to this enhancement to help prioritize it if you feel this applies to you.