cptStatusSheetImport - false positives on deconfliction report?

[AronGahagan]

Problem:

User SD seeing false positives on the deconfliction report. I suspect it has something to do with his unique Master/Sub setup.

Solution:

TBD - meet with SD to diagnose and fix.

Todo:

• assign this issue
• assign issue type (Bug, Feature, Task)
• label the issue with codemodule (so fixes can be aggregated and hotfixed together)
• checkout appropriate branch and create topic branch
• design, code and test
• update codemodule <cpt_version>x.y.z</cpt_version>
• update CurrentVersions.xml manually
• commit message should begin with Issue #XXX -
• commit the change(s)
• merge topic into appropriate branch(es) and push
• delete topic branch

[AronGahagan]

(waiting on user availability to reproduce the error)

[AronGahagan]

User SD is exporting from a very large Master/Sub. The Import expects all group-level summaries, and normal summaries, to have Unique ID = 0...but for some reason the Status Sheet has the (masked) Unique IDs for all task summaries. SD is not grouping before Status Sheet creation.

When the Unique ID is not found (for some reason), the oTask is set to UID = 1.

Either a) change cptCreateStatusSheets in cptStatusSheet_bas to put all task summaries to UID=0; or 2) figure out another way to skip summaries during cptImportStatusSheets in cptStatusSheetImport_bas.

[AronGahagan]

Copy/Paste export drops different UIDs than vba-based export. So finding them on import gets trickier. Accommodate both methods, accommodate export from sub import to master, export from master, import to sub, ex/im master, ex/im sub, and standalone. And convert everything to SetMatchingField instead of looping through all assignment number fields.

[AronGahagan]

Significant refactoring when dealing with master/subs and the different UIDs that come out of VBA vs what's available on screen, especially concerning Assignment UIDs. The following actions are now supported:

• export from master import to master: supported
• export from master import to sub: supported
• export from sub import to sub: supported
• export from sub import to master: not supported

If code cannot find the UID in the active schedule as either a Task or an Assignment, a series of 'retries' fires to mod the source / status sheet UID down to something else it might be able to find. This should make the import process more robust whether the export uses a vba-derived task and assignment uids, or if it uses copy/paste (which are actually different). This also allows us to perhaps use a different export method for speed/efficiency depending on how many tasks are currently selected for export. E.g., for extremely large datasets, copy/paste becomes less reliable (and we can't "wait" for the full "copy" to finish, nor the full "paste") anyway. Would set a low threshold: if < 500 tasks then copy/paste, else use array. Then the issue becomes formatting. Guess we could paste without formatting then use same formatting routine regardless of which export method is used - so sheets come out consistently. Might include the Assignment flag next to UID temporarily so we can identify better for formatting. Onward.

[AronGahagan]

Should ensure that the UID in the Status Sheet matches whatever the user sees, regardless of the "true" VBA value. This needs to happen in CreateStatusSheet.

[AronGahagan]

...maybe the better overall plan is to start relying on GUID. Put GUID in Status Sheet (hidden column). Prior to Import, build map of GUID to UID. Then lookup GUID and go from there.

[AronGahagan]

...better yet: build a map of GUID to the actual object (task or assignment). If oMap.Exists([GUID]) then Set oTask = oMap([GUID]).

[AronGahagan]

(Hidden) GUID column now included in all Status Sheet creation, which enables:

• export from master import to master
• export from master import to sub
• export from sub import to sub
• export from sub import to master

also:

• source UID and target UIDs noted in logs if there's a difference in the displayed values so user can quickly find issues
• UIDs in Status Sheet now match displayed UIDs (i.e., for Assignments) instead of underlying VBA values