Open RDmitchell opened 1 year ago
This doc explains the details https://docs.google.com/document/d/1xO25-58s8_H8QWG0tAQlPouzJvawyHxbOM_6oTHilAc/edit?usp=sharing
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
@kflemin -- I wonder if this should be moved to the Q2 bug fix project, if there is time to work on it, since it's almost a bug, ie, we need to warn the user that there are multiple cycles defined for the same time period, and basically not allow the import, or something like that... ??
This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
Instance: seeddemostaging SHA: 22e66f350 Org: ID = 323
I imported an ESPM file with multiple cycles (2018 - 2022) into an org that already had data for 2018 and 2019.
For the 2018 cycle, the ESPM field "Custom Property ID 1" was not merged into the existing records with the same PM Property ID, although it appears that field was imported for the other cycles, one of which had existing data.
What I didn't realize was that there were multiple cycles defined with start and end dates for 2018.
SEED chose one of them, but not the one I wanted the data imported into. It chose the BETTER Test 2 cycle, rather than the 2018 Compliance Cycle.
Would it be possible to show the user that there are multiple cycles defined for the same start and end date and let them pick?