Remove distributed collaboration label from AGOL item via Python

[Jay_Gregory]

I have some items in my organization that were created there via a collaboration with Enterprise.  They were created as references to the Enterprise feature layers, ensuring the popups, symbology, etc remained consistent.  However, I have since disabled that collaboration, unshared the items from the groups on either side, and in the case of the AGOL items, used the AGOL assistant to change the URL to an AGOL-hosted feature layer instead.  However, there is still the label on the AGOL items that says "this item was received from a distributed collaboration."  Does anyone know if there is a way to remove that?

Thanks!

[SeanCulpan]

Did you ever get a resolution to this? I have a very similar situation where we have items in AGOL which are now disconnected from their AGE sources (long sad story of failure!).  I haven't been able to find anywhere that this flag is set. 

[Jay_Gregory]

@SeanCulpan No resolution.  Curious to hear your sad story of failure if it has to do with collaboration - I've been having major issues maintaining a functioning distributed collaboration environment between AGE and AGOL and am considering just updating AGOL data sources separately.  

[SeanCulpan]

All was going great with our AGE to AGOL (one-way) collaboration.  Lots of data out to AGOL without issue until the edits started.  We discovered that when we made changes to the enterprise featureclasses they weren't replicating to AGOL.  They showed up in the AGE services but nothing was getting picked up and sent through to AGOL.  We raised a case with ESRI(UK) and eventually they closed it citing BUG-000164335: Feature service edits are not synchronized when the guest in a distributed collaboration has a multi-machine deployment architecture.  This is an 11.1 specific issue and apparently is resolved at 11.3 but my experience with multi-machine in-situ upgrades is not good.   This took around 3 months, multiple analysts and hours of screen sharing.  At the moment we are updating AGOL as a separate process which we can tolerate in the short term.  Longer term we're looking at a new world order where we don't use AGE and only have the  EGDB on prem and all web stuff is delivered from AGOL.