Support for aggregated data exchange#1039
Open
xurxodev wants to merge 38 commits intofeature/routes_as_instancesfrom
Open
Support for aggregated data exchange#1039xurxodev wants to merge 38 commits intofeature/routes_as_instancesfrom
xurxodev wants to merge 38 commits intofeature/routes_as_instancesfrom
Conversation
…o feature/support_aggregated_data_exchange # Conflicts: # i18n/en.pot
…_aggregated_data_exchange
Member
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
📌 References
📝 Implementation
📹 Screenshots/Screen capture
🔥 Is there anything the reviewer should know to test it?
Limitations:
1- It's not possible to edit an ADEX without assign credentials, for this reason is necessary set credentials to create or update ADEX sync rule
2 - ADEX run failed for datasets, dataElementGroups, etc. The unique models working and enabled are indicators, program indicators and data elements
Scenario to test using play 2.41.6 as origin and play 2.42.3 as destination
1 - In 2.41.6 replicate the user tQSUE8azWFG with all aggregated data exchange authorities
2 - Run analytics
3 - In 2.42.3 import the next metadata with dataset and data elements with necessary codes
adex-play-destination.json
4 - Execute Metadata sync against play 2.41.6 using replicated new user credentials
5 - Create a new ADEX instance with url https://play.im.dhis2.org/stable-2-42-3
6 - Create a ADEX events sync rule
Select Sierra Leone org unit
Select doses program indicators: BCG doses, Measles doses, Yellow fever doses
Select this year period
Select monthly aggregation
Select ADEX instance
Set credentials
Save
7 - Create a ADEX aggregated sync rule
Select data element: Accute Flaccid Paralysis (Deaths < 5 yrs)
Select indicator: ANC 2 Coverage
Select Sierra Leone org unit

Select this year period
Select monthly aggregation
Select ADEX instance
Set credentials
Save
After execute these program rules, the result in play 2.43.3 should be:
📑 Others
Any change in the GUI library? If so, what branch/PR?
Any change in the D2 Api? If so, what branch/PR?