Unable to import BRG into Dataverse

Follow

Stuart Nelson

• May 22, 2018 07:19

I'm trying to import a v6.1.4 BRG into Dataverse (v3.2.0) without much success. 

The error message being returned is:

"Sorry could not import from file <filename>.

Unable to read the file.

Please check that the file is a valid file."

 

The graph works as expected in LAE and I was able to import into the previously installed version of Dataverse (v3.1.6).

Any suggestions would be appreciated.  Many thanks.

0

• 

  Adrian Williams

  • May 22, 2018 09:11

  Hi Stuart,

  
  Can you check whether the LAE graph contains any Visualizer nodes. If it does try deleting these node and save the LAE graph as different .brg file. Then attempt to import that .brg file instead.

  You should also confirm whether any dependent libraries are required by the graph (in BRE use View -> Dependent libraries...). These will need to be loaded into Dataverse first.

  0

  Comment actions Permalink
• 

  Adrian Williams

  • May 22, 2018 09:16

  You may also want to review the Migrating to Dataverse guide available here:

  https://installers.lavastorm.com/Dataverse320/Migrating+to+Dataverse.pdf

   

  0

  Comment actions Permalink
• 

  Stuart Nelson

  • May 22, 2018 09:43

  Hi Adrian,

  No issues relating to the above comments (visualizer, dependant libraries - I have already imported these).

  I did recreate the graph and try to import this with the same result.

   

  Thanks.

  0

  Comment actions Permalink
• 

  Adrian Williams

  • May 22, 2018 09:45

  Would you be able to send us the .brg file by raising a support ticket and attaching the file?

  0

  Comment actions Permalink
• 

  Adrian Williams

  • May 22, 2018 09:46

  Can you also confirm the Dataverse version you are using. Thanks

   

  0

  Comment actions Permalink
• 

  Stuart Nelson

  • May 22, 2018 09:48

  Version is 3.2.0 which we completed the upgrade of yesterday.  I'll look into the support ticket.  Thanks.

  0

  Comment actions Permalink
• 

  Adrian Williams

  • May 23, 2018 13:09

  Update: The root cause for this issue was that a dependent library could not be found by Dataverse when attempting to import the data flow. This was overcome by creating a staging/import folder and then importing the dependent library and the data flow into this folder. Once the data flow has been imported into Dataverse it can be moved to the required folder and the library search paths updated to include the (final) location of the dependent libraries.

  0

  Comment actions Permalink

Please sign in to leave a comment.