Staging for Interfaces

[Guillaume_Boill]

Hello, I have the need for a "staging" environment for interfaces. By that, I mean it would be valuable for me if I could "disconnect" the interface from the underlying data when needed. The idea is to avoid having users see intermediate states of the database while it is being updated. While the read-only interface is "disconnected", users can only see the data just before the disconnection and would see the new state once the interface owner re-engage the connection.

[IPS_Grow_Admin]

Hey, I would maybe duplicate the Interface and keep it unpublished? Or simply make the changes in the Interface you have but do not hit Publish?

[Guillaume_Boill]

Hi, that would work to stage the interface look & feel but what I am interested in is staging the data itself. In other words, I would be interested in having the interface show a snapshot of the data until I am done updating the data....

[Guillaume_Boill]

I figured out a way which consist in introducing an overarching table of versions and use this version as a prefix of the actual records. It is quite involved but remains manageable.

[BenFortunato]

Curious how you solved this. . . I'm facing the same issue. IN my case I'm also changing the interface and working on scripts, potentially renaming fields so this solution might not work? Sounds like this is just about keeping a record of the values in the records not overall changes to the database structure.