Skip to main content
S
subhajitb1373
April 22, 2025
Question

Loading Data into a new Table / View from 4 different tables (These 4 tables don't have Record , those are old tables They have CDT)

  • April 22, 2025
  • 6 replies
  • 0 views

Hi ,

We have a requirement of Loading Data into a new Table / View from 4 different tables (These 4 tables don't have Record , those are old tables They have CDT) . 

In terms of Performance and New features of Records which approach will be better ?

1. Use Store Proc ( Creating a new table > Select required columns from 4 different tables > Insert into new table ) 

But in this case , everytime if our 4 tables get updated in Prod, We have to run this Store Proc

       2. Create a materiliazed view . 

but I guess in this case also , we have to update our view if there are entries in those 4 tables

      3. Create a normal view from 4 tables 

But Record Sync and other data fabric features won't work here I guess

Can anyone please help here ? Thank You in Advance

6 replies

mikes0011
mikes0011
Brainy
April 22, 2025
We have a requirement of Loading Data into a new Table / View from 4 different tables (These 4 tables don't have Record , those are old tables They have CDT) . 

This sounds like a standard use case for a traditional View.

But Record Sync and other data fabric features won't work here I guess

Why would this be an issue in this case, exactly?

S
subhajitb1373Author
April 22, 2025

I have explored and found out that these 3 options are suitable for us . 

If we are going with Approach 3 : Using traditional Views , we will be missing out latest features of Data Fabrics like Record Sync , Custom Fields , Data Events and many more . 

If you can still suggest which features of Data Fabrics we can still use for a View ; that would really help .

mikes0011
mikes0011
Brainy
April 22, 2025

Are the 4 old tables going to be maintained, or are you planning to copy their data into a whole new table for the sake of that new table now being used going forward?  In that case I would suggest you use a stored procedure to do the data copy into the new table, then use a Synced Record that relies on that new table alone, and leave the original 4 tables as-is for posterity.

But if the 4 tables are the ones that will be maintained going forward and your view will be a live aggregation of the values of those tables for informational purposes, then I suppose your choices are either 1) make a Synced Record Type for all 4 of them and use record relationships to link them all, or 2) create a traditional view and just use it like a view, including using a Data Store to access it, and Query Entity to query it into appian.

I'm not really clear what your use case is exactly so can't really comment much further on how you will make this decision.

    Terms & ConditionsAccessibility statement