DAO: Data Migration for GBV Calculated Fields #482
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note
This is related to the DAO: link - already approved & paid
One of the final parts of the calculated decimal average work is to migrate the existing GBV sites. This migration will do that. I am curious how these migrations are actually run though. Is it an automatic process, or will it need to be run manually on each demo site?
Further, I need to destroy and recreate the relevant fields because one of the fields in GBV is mistakenly marked as "numeric_field" rather than "calculated" -- it's not possible to change the field type of an existing field. Are there any consequences of doing this that I might not have foreseen?