How do I re-point an imported report to a different data source?
This is actually about migrating reports from QA to Production. I can't see any way to easily re-point the data sources to my production databases.
Surely we are not expected to manually re-create every report when rolling to production? shouldn't it at least just have a datasource ID/Name I can replace in the JSON file?
-
Hi Lauren!
I recommend using this help page to help you export and import your reports into a new environment: https://docs.geocortex.com/reporting/latest/help/Default.htm#rpt5/help/import-export.htm#Copy_Reports_from_One_Portal_to_Another%3FTocPath%3DExport%2520and%2520Import%2520Reports%7C_____1
Note that your data sources will need to be identical in name and content. If some fields are different you will need to open the query builder and remove any fields that are no longer the same and add the new fields and update the query filter. Then, you will need to manually update any components in the layout that use the old field name.
The page's introductory paragraph also notes other considerations when going through this process.
0 -
Thanks Tegan! it's the 'having identical names between test and production' that was causing issues. We like to make it sickeningly clear which database we're working with so have always named with "TEST database" and "PROD database" in each environment.
We are going to go with naming them the same just in this instance but it would be better to be able to re-point data to a new source - sometimes databases move and alias's change.
0 -
Also, if anyone is wondering, it turns out you can change the source in the JSON. you just need to copy the Base64 encoded details into a decoder, make the change, copy that into an encoder and replace in the JSON. then you can import to the new environment with a new database name.
I did this to rename the sources in our test environment without having to manually recreate every report.
2 -
Totally get it Lauren. I'll forward this on to the product manager and see if he can take this into consideration in the future.
0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
4 commentaires