Error when importing a legacy data flow into Dataverse

Follow

Khai San Bahn

• February 07, 2017 14:20

 Hi I am getting the following error message when importing a LAE.1 .brg file.

	Data flow 'LAE_UseCase_AML_v18_6.1a.brg' could not be imported
	Show Details Unable to resolve the parent for node dc37ae08-d32d-468b-bf74-ad84f5c71908. No node in the repository matches legacy type null::Lookup. Hide Details I have tried to isolate the problem by removing different parts of my graph but each time, I am getting a similar error message to the above albeit eith a different node serial no. Is there any way to understand which node the above is referring to? Thanks

0

• 

  Catharine Coleman

  • February 07, 2017 14:49

  Hi Kai,

  Could one of the nodes in the your graph be a shadow node from a library?  If so, can you make sure that the library has been upgraded to 6.1.x?

   

  Thanks,

   

  Catharine

   

  0

  Comment actions Permalink
• 

  Khai San Bahn

  • February 07, 2017 14:57

  Hi Catharine,

  How do I make sure the library has been upgraded to 6.1x?

  Thank you

  Khai San

  0

  Comment actions Permalink
• 

  Rocco Pigneri

  • February 07, 2017 15:11

  Dear Khai,

  I recommend importing each dependent library before you import the final graph.  You can find all dependent libraries in BRE by going to View->Dependent Libraries.  Anything that isn't in your Lavastorm directory should be loaded into Dataverse before your final BRG.

  Be sure to use the Import->Legacy Node Libraries option when you import the libraries in Dataverse.  That option is underneath the Legacy Data Flow option as you can see below:

  

  Hope that helps,

  Rocco

  0

  Comment actions Permalink
• 

  Stony Smith

  • February 07, 2017 16:24

  Make sure that you open and save any dependent libraries in BRE first, so that you can ensure that they are all up to date. I've seen a number of times when the main BRG gets upgraded to 6.1, but the users forget to upgrade the Library BRGs also.

  That might not be your problem in this case, but it can contribute to the issue.

  0

  Comment actions Permalink

Please sign in to leave a comment.