Adding scoped field to global table

[jeremy_gardner]

Is there a way to add a scoped field to a global table?   I'd like to add a custom field to cmdb_ci so that our scoped app can leverage customer's data/relationships in the CMDB, and I see an option for "Allow new fields" option on the form, but it's hidden from everybody but maint.  

Alternatively, is there another way to accomplish something similar?

Thanks,

Jeremy

[aklimenko]

Same problem here with sys_user table. We added few fields to hold additional information that comes from 3rd party system

[aklimenko]

I guess there is nothing we can do right now, so my workaround was to let customers know - if they want to take advantage of extra features that require such extensions - just add the fields yourself.

Hopefully there will be some better solutions later...

[Uncle Rob]

Definitely won't work for us, as we'd use the existence of a relationship to build all kinds of stuff in the app: list views and such.

I'm just not sure if any of our apps are actually do-able.   I understand vacuum packed apps is safer for the rest of the platform... but how good can an app be if its completely isolated.   Much of what I've gained value from on SN over the past decade is the massive gains in interactivity and relationships that come with apps integrating with each other.

[aklimenko]

I absolutely agree with you. Power of ServiceNow is reuse of rich data structures and limiting application developer reduces usefulness and richness of apps.

Our product is fairly complex and what we did was to inherit most of the tables, so we do not have troubles with extensions. Also during migration we decided to completely severe inheritance for some tables (like expense lines) as it brought more complexity than use.

Good luck with, I fell your pain

[jeremy_gardner]

Yeah, this might be a show-stopper.

Extending tables != adding fields to tables.   When customers are already using User, Customer, and Location tables for their data, there's *zero* chance we can tell them to put that data in an extended table instead.

Hrm...