How to write data entry back to source database?

We've recently moved to a world of trying to maintain a clean production environment and making all changes in dev and then periodically copying the entire dev database across to live.

However.....

We've realised that data entry performed in live now gets overwritten. We have some data entry enabled for both entities and cubes.

Please can someone point me towards documentation that explains the best methodology for pushing data entry cubes and entities either back to a source database, or for copying these from live to dev before migrating changes in dev? I've not been able to find previous posts on this topic.

Thank you in advance.

Find more posts tagged with

Data Entry

Accepted answers

All comments

Previous Member

As an update, I've now discovered documentation on ROLAP cubes (once I figured out the name of what I was searching for!) and have got those working.

Still not sure on the best way to get data entry Entities synced back to source database though, if anyone is able to help with that. Thank you!

Helmut Heimann

Hi Victoria Walton,

if your approach with ROLAP for Cubes is working, you'd only need a possibility to get entries made on entities (new members) back to DEV, correct?

My idea would be to extract those entities (better: the trees) from PROD to HardDrive, provide the appropriate files to the DEV system and re-import the data into DEV.

If you have further questions, don't hesitate to ask.

Kind Regards,

Helmut

Sebastian Gurt

Hi Victoria Walton,

I am not sure I understand the reason for your data getting overwritten. Do you copy your complete database from DEV to PROD? If this is you desired deployment mechanism you should export all the prod data and import afterwards. Check out Database export and Database reload.

Better yet: Use the Transporter to deploy your structural changes (entities, cubes, data reader...) without impacting the data in your prod environment.

Sebastian