This is not so much a question as an ongoing issue since the update of ArcGIS Online to 10.2. To support the following, here are the case numbers so far created regarding this problem. Case #03090371 and case #03102366.
I am aware of a large number of other customers with the same or similar troubles since this last update. It is disturbing the bug (BUG-000150632) created by ESRI support was summarily dismissed, knowing a large number of customers are affected. From a customer perspective, ArcGIS Online essentially is telling multiple customers we are lying when we say we used to be able to publish features that had geonetworks functionality. Yes I am aware ArcGIS Online states we were never able to do such a thing, but I and many others were indeed able to do this, know full well the geonetworks piece was removed somehow upon publishing, which in our particular case, was not a problem. For MANY years we WERE able to publish layers that had geonetworks functionality without an issue, until the 10.2 update. During the 10.2 update, something broke, not allowing those features (or any other features in the dataset) to be published. One by one the features that are not associated with geonetworks can be published, but the main, and most important layers cannot be.
In my humble opinion, ArcGIS Online did not vet the update appropriately, and did not consider what this would do to customers. While I'm not a developer, it seems any update would consider what the customer experience would be afterward, and would make sure current users would not see any adverse effects.
The 'work around' is severely time consuming and it appears a new wheel must be re-created with each and every update to the data, as well as the properties of the data for viewing. Again, there may be a solution that this new case will bring forth.
In the meantime, the roll out of ArcGIS Online 10.2 had tragic results for us and I'm told many others. If ArcGIS refuses to fix a problem that affects many users, at least acknowledge you messed up and provide a work around that doesnt take a day or two for each data update.
Very Frustrated User