Best practice to do transform map between cross-scoped tables

harshinielath
Tera Expert

Hi.. I have a table which is in a scoped app. I want to get the data from it and create a new table with some extra fields in global scope without disturbing the scoped app table values. I need suggestions on best practices to implement this transform map concerning cross-scoped applications.

5 REPLIES 5

Brad Tilton
ServiceNow Employee
ServiceNow Employee

Do you want to migrate the data one time or setup some sort of scheduled migration?

You should be able to do both of those. What have you tried so far?

I work with Harshini as well.  We need to do a single import of the data and then have it regularly update the other field.  Here is a better description of the situation.  

Our facilities department decided to use the Nuvolo application.  The location table in the Nuvolo application is the most accurate and up to date.  They update it when new construction happens, or they renovate a closet into an office space, etc.  They have agreed to be the source of record for all office location data.  We want to take the table they have in the scoped application of facilities asset management and bring it over to the location table in the global scope, and then do it regularly to make sure it stays up to date.

Since we have not done this before we are looking for the best practice way to do this.  Or do we even need to do this?  Can we create a request item in the global scope that looks at and uses data in a different scoped application?  This is all new territory for us.

You can reference a table in a scoped app from a global table. You could also add some business rules that keep the tables in sync across scopes. For that I would check out cross scope access.

So if I'm reading this correctly it means that we just need to add the needed fields to the global table to and reference what we are looking at in the table in the Nuvolo application?