Migrate a data table

Development Asset Creation
, ,
1

Keep the references to others assets storad in other plugins, during the migration of a data table.

2

Steps to Reproduce
Hi

All our assets are stored in plugins, including the data tables.

We use data tables to reference some lists of blueprints stored in others plugins.

When we migrate a such data table to another project (with the same plugins), we loose all the references.

Note that this issue does not appear for the other types of assets.

Best regards

Your have 2 projects X and Y with the same plugins.

In a project X:

1/ Create some BP in a plugin A.

2/ Create a data table un a plugin B to reference a liste of BP stored in the plugin A.

3/ Migrate the data table in the project Y.

4/ Open te project Y.

5/ Open the data table.

3

Hi Romain,

Thank you for reaching out. I’ve been trying to reproduce the behavior you described, but so far without success. In all of my tests here, references were kept valid when migrating the datatable from one project to another (inside the same plugin on both projects).

I have attached a pair of test projects with my attempts. Both projects X and Y contain plugins A and B, each with several blueprint classes, static meshes, and a level containing actor instances of the blueprint classes. Each plugin contains blueprints derived from a base on itself and on the other plugin. Each level also contains actors from both plugins, so everything is as mixed up as I could make it. Project X’s plugin B also contains a couple of test DataTables referencing assets and actor instances on both plugins. After migrating these DataTables (and their row structures) to Project Y’s plugin B and opening that project, everything still seems properly linked.

Would you kindly be able to provide some extra information about your setup?

  • Are you running the vanilla 5.5 engine from the launcher, or building from source with any possibly-relevant changes to the code?
  • What is the exact type of the references that are breaking? (for example: object references, class references, soft object references, soft class references, soft object paths, soft class paths)
  • Are the references pointing to “Actor”, a blueprint based on “Actor”, or a blueprint based on another native class derived from “Actor”? Where was this target type defined (project, plugin A, plugin B)?
  • If the references are to Actor Object Instances instead of Classes, where is the referenced level located (project, plugin A, plugin B)? And does that level have “external actors” enabled?

Also, if would be very helpful if you could provide a small repro project (or a couple of repro projects) where the problem can be observed, along with detailed repro steps. You can start from the ones I attached if it helps.

Best regards,

Vitor