cancel
Showing results for 
Search instead for 
Did you mean: 
RADSr
Partner
Partner
Status: New

I'm about to embark on a major change to a schema.  I need to keep the current "gold" copy intact while I work on this change. 

AFAIK, the process I need to use currently is:

 

1)    Create new schema 

2)    Export new schema

     - find it's ID number in the XML

2)    Export existing schema

   - replace the existing schema ID number with the new one

3)    Rezip existing schema and import

 

What would be better would to be able to make a copy similarly to the way I can make a copy of a dashboard and have Incorta take care of the new ID rather than opening up the process to user error. 

3 Comments
RADSr
Partner
Partner

Here's another use case for allowing this - I need to create some IA tables from a schema but I can't because the main fact table has a runtime security filter associated with it.   

The quick and easy answer would be to copy the schema, remove the filter on the new copy, create the IA tables and then apply the filter there for use in insights.

I *can* do that by doing a bunch of XML editing, but it goes from a quick and easy answer to a last-ditch, PITA answer which relies on manual edits to XML files and introduces risk of corrupting existing work.  

DustinB
Employee
Employee

@RADSr - For now, you could copy the fact table by creating an MV (select * from fact) and create your Incorta tables from that. Assuming your original fact table is an extract from the source, this has the added benefit of not re-extracting data that is already present. 

RADSr
Partner
Partner

That's a good idea and I may go that way, I still need to recreate all the joins but select * w/ Postgres SQL should bring in the formula columns so that will save a bit of time.   Probably be easier and less risky than the XML route.    Thx!