Hello all.
We're struggling with migrating data from a FileMaker based application over to Outsystems. We're trying to create a repeatable process that will allow us export from FileMaker and import into Outsystems with all data relationships intact.
We have a table called Identity and a table called Achievements. Then we have a join table tying out Identity to Achievement called IdentityAchievementJoin. So the join would have the IdentityID from the Identity table and one or more AchievementIDs from the Achievement table.
If we export this data out to XLS from FileMaker and then bootstrap it into Outsystems, Outsystems will create new id's for all three tables and the join table will break because it won't understand the FM ID's given it creates its own.
What's the best way to bring a large volume of data, across 30 or 40 tables into Outsystems while maintaining the relationships between those tables?
Thanks,
--Rick
Hi, Richard.
Since Ousystems does not allow turn off auto incremental key and turn on again with migrated data, I think that the best option is create a From To table, where you will store the legacy id, the new OS id and the table name. With that, every new table that needs to reference another table you just query the From To table to know new id based in your legacy id.
If you still need to keep the same id, there is a work around that I don't recommend. Which is use CommitTransaction and AbortTransaction actions, something like that:
Regards,
Gabriel.
Bootstrapping directly is not feasible for your situation due to existing joins. There are two approaches you can consider:
1. Programmatic Approach: Import your data into the respective tables, ensuring to preserve the original IDs in a separate column. After importing, map these old IDs to the new IDs within the join and reference tables during a second pass.
2. Using Data Migration Tools: Consider the Data Migration Manager (DMM) by Infosistema (https://www.infosistema.com/data-migration-manager/). They offer a forge component that facilitates data import into your platform, potentially streamlining the process while maintaining data relationships.