[Import/Export] Example Display Layouts are broken on Import or Export

[unlikelyzero]

Summary

@charlesh88 created an example display layout which best illustrates a Mission Display. After importing, I noticed that the layouts did not match what was represented in the email

Expected vs Current Behavior

Import

Exported by Charles

Steps to Reproduce

1. Import the Display Layout from ./e2e/test-data/ExampleDisplayLayout.json
2. Note how the display does not match the screenshot from the initial export

Environment

• Open MCT Version: 2.1.1

Impact Check List

• Data loss or misrepresented data?
• Regression? Did this used to work or has it always been broken?
• Is there a workaround available?
• Does this impact a critical component?
• Is this just a visual bug with no functional impact?
• Does this block the execution of e2e tests?
• Does this have an impact on Performance?

[charlesh88]

Wow! As mentioned in email, this export was the result of exporting a folder with aliases to two layouts. I've attached that original export here, as well as an export of my My Items folder which holds the two layout's originals.

Newly exported My Items folder that contains the two layouts, as well as a number of other things.
Open MCT Examples 10-05-22.json.zip

The original 'bad' export file cited in the bug.
CH My Items export 10-07-22.json.zip

Correct version of 'Display Layout Example 1'

Correct version of 'Flexible Layout Example 1'

[charlesh88]

I tried importing my own previously exported file 'CH My Items export 10-07-22.json.zip' at got these results. In short, the Display Layout was severely broken and identical to what @unlikelyzero observed, while the Flexible Layout is identical to its original.

I also reimported my own My Items export, and in that version the Flex Layout was again identical to the original, while the Display Layout was mostly correct, with a misplaced alphanumeric (upper left), which is a known (?) issue:

A couple thoughts: how do we (do we?) handle in exports Condition Sets that are used by domain objects like Condition Widgets if the export doesn't include a folder that contains them? For example, what happens if the user exports 'Display Layout' below?

> Folder
  > Condition Set
  > Display Layout
    > Condition Widget (that uses Folder > Condition Set)

What location does the Condition Widget's styling Condition Set use? Looking in the 10-05 export JSON file, the '210 Condition Set' object has the property of location: null. Is this part of the problem?

[shefalijoshi]

Are display layout imports that Don't use condition sets also broken?

[shefalijoshi]

@charlesh88 I tried to export a Display layout with a condition widget and condition set like you mentioned and did not have any trouble importing it between Firefox and Chrome browsers on my computer. The layout was fine when imported.
There must be something else going on.

[charlesh88]

@shefalijoshi Some of the elements in use (SWGs, Condition Sets, etc.) are kind of old, so wondering if that’s a factor. I'll see if I can make this happen with freshly made objects.

[shefalijoshi]

I'm unable to reproduce this on either 2.1.1 or 2.1.2 locally. (localhost:8080)
this is what I see when I import it.

[unlikelyzero]

adding @charlesh88 to help in the investigation

[unlikelyzero]

Cannot reproduce with 2.1.1 or 2.1.2. Will close this and remember that it exists 👀