Publish a standalone to Enterprise (by reference)

[AllanBenvin_yyc]

We have a requirement for tables stored in an enterprise geodatabase to be published to Enterprise (portal) and be editable. Currently there are two ways to do this.

1. Publish from Pro and add a dummy featureclass to the map then publish. You do get the table but then you have to always have a feature class published with it. This adds an unnecesary item to the service and makes things more confusing.
2. Publish using Bulk Publishing in Enterprise 10.7. This creates a separate service for each table. No featureclass is required. The downside is it published all objects that the datastore credentials have permissions on. 

    (Manage bulk-published layers—Portal for ArcGIS | Documentation for ArcGIS Enterprise )

So it seems to me that the ability to publish standalone tables exists somewhere internally but does not seem to be exposed in Pro or in the incredibly poorly named "ArcGIS API for Python". It would be very useful to deliberately publish a standalone table by reference to Enterprise (portal) using ArcGIS Pro. 

-Al Benvin

PS: Fifteen years ago we had developers adding Null geometry columns to their standalone tables so they could be published and consumed via services. It seems we are not much further along now than we were then.

[Amanda__Huber]

Yes yes yes! This is exactly our issue as well. 

ArcGIS Enterprise‌ please consider allowing Standalone Tables to be published by reference to ArcGIS Portal/ Enterprise (without a dummy layer). This functionality would help our organization out immensely. 

Thanks!

[JCGuarneri]

This is absolutely critical. I have tables that come in from a non-geodatabase source that I need for web services. Right now, we need to maintain a copy of the data in our geodatabase. Originally, there were some other requirements that made this necessary. Modern Arcade popup options have made this unnecessary. Being able to publish this other table as a standalone would vastly simplify our data storage and workflows.

[TanuHoque]

This limitation was relaxed in while publishing from ArcGIS Pro in v3.3.

Please give this a try. On the server side, I don't think you'd need to upgrade unless it is an older or unsupported release.

[JCGuarneri]

Oh, that's great! Definitely missed that in the release notes. I haven't updated the machine I typically publish from to 3.3 yet, so I'll have to give that a shot once I get there.