Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrations.XML is not working #9076

aliasguru opened this Issue Aug 30, 2018 · 4 comments


None yet
3 participants
Copy link

aliasguru commented Aug 30, 2018

Dynamo version

Operating system

Windows 10

What did you do?

I've posted the question already here in the Forum, but got no answer so far:

Basically, I have followed the steps in to set up a migrations.xml file. But even though the file name, the file location, and the given package paths are correct, the nodes in question in the node tree are being shown as "Unresolved" when I open the Dynamo file.

What did you expect to see?

no errors, node tree should continue to work

What did you see instead?

unresolved nodes


This comment has been minimized.

Copy link

mjkkirschner commented Sep 5, 2018

@aliasguru can you confirm what type of file you are trying to migrate - a json or xml based file?
I'm not sure JSON files will be able to migrate at this point. I think it was an oversight that remained when we transitioned to json that migration was not required because we only had one released version of dynamo that would create json files.

But this does not take into account packages which might migrate between dynamo versions. 😬 .
@Racel @QilongTang


This comment has been minimized.

Copy link

aliasguru commented Sep 8, 2018

@mjkkirschner Hm that would start to make sense. I'm not trying to migrate from an old Dynamo version. In fact, I only want to change a namespace. I had placed a node in a certain package, and now want to move it to a different one. My understanding of the migration was that it would be evaluated any time I open a node tree, instead of only if the Dynamo version which the node tree was created in differs from the version that it is opened with. It's just because the node trees I'm testing my nodes with can become complex, and it's tedious to re-hook all those unresolved nodes.


This comment has been minimized.

Copy link

johnpierson commented Nov 21, 2018

Tracked internally as QNTM-5547

@johnpierson johnpierson added tracked and removed needs more info labels Nov 21, 2018


This comment has been minimized.

Copy link

mjkkirschner commented Feb 1, 2019

@erfajo this sounds correct - but should be fixed in next release:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.