When trying to assess how easy an upgrade to webCRM is going to be, it would be really useful to see a full list of all the custom fields for a given profile in one page on the admin portal (i.e. all the xtra tab fields from the various heirarchy levels displayed on one page).
As a second stage we could get it to lookup the oData definition for that field and display that alongside.
As a third stage we could allow the user to set the oData definition for any custom field that doesnt have one (and perhaps amend non-breaking bits like description).
3.1 should also maybe allow the user to mark a field as obsolete (no longer required) so that
As a fourth stage allow creation of new fields from here.
As a final stage, allow creation and all of the above for custom entities (custom tables with custom fields).
We defninitely dont need to do all of these stages in one go. I just listed them to show that we can do the first one or two really easily (and get something really useful without tonnes of work) but be on the right road to where we want to end up.
We have been working on an update to make these fields available in the Operations portal because customers editing this could cause other systems to break. We will be able to move it to the admin portal at a later date when we add more checks and validation.