Like what you see? Have a play with our trial version.

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

Note: When exporting definitions from Yellowfin there are certain limitations. You cannot export security settings that relate to individual users, only group or roles. These will have to be reset when importing them into the new instance of Yellowfin. Source filter information will be exported but only if it is a scheduled SQL query. Manual records and data file records will not be exported. This is because it's assumed that users will differ between instances, but groups and other structures will be the same.

 

Content Dependencies

...

Column
width470px

Image Removed

...

width99%

When exporting content, it's important to not only select the items you wish to export, but also all other items the main content may depend on to work.

Yellowfin's content dependency structure is illustrated to the right.

For example, if you are exporting a Report you will need to either:

  1. include all images it uses, the category and sub category it's stored in, and the view and source connection it's based on, or
  2. ensure all the items above are already available in the instance you plan on importing the item into

 

...

Image Added

 

Database Independence

If you are using the export and import functions to migrate Yellowfin across platforms then you will have to be mindful of any hard coded SQL. Examples of this may be:

...