I have some Assets that I would like to convert to a CustomEntity. The best answer I have so far, is to recreate the asset as a custom entity manually, then change the link for all the asset tasks to the new customentity, but this is labor intensive and might not move everything.
I tried to use the api to update the entity type from Asset to the CustomEntity, but that didn’t seem to work.
What is the optimal way to migrate some existing assets with tasks, notes, versions, etc into a new entity?
You’ll need to find all the task, note, version entities, etc and change the link in the “entity” field to point to the new entity.
Can you expand on what the new custom entity is?
Are you customising the templates and schema also? Are there files you also need to move?
So, currently, the asset group is managed by types, but there are dramatically different pipelines that need to be set up and thus, it seems best to separate the assets into new entities to help manage this.
I’m sorry, but not sure what you mean by templates and schema. I’m going to assume task templates and yes, but recreating those and reassigning doesn’t seem terrible. I assume schema is the field list, and yes, this would be different in the new entities as that’s one of the reasons to switch, to have more specific fields per entity instead of a bunch of unneeded fields in each asset.
Yes, files to move too. Which I have no idea how to do this.
Sounds like you’re coming from a producer’s perspective here.
If you already have a lot of data on disk linked to SG, then moving that across will potentially be a real pain in the back-side. File will need moved and possibly renamed.
Schema : This is the folder structure as used by flow toolkit (the application integrations).
Templates : This is the configuration for file/folder naming used in the schema. No task templates.
Are the files on disk in Flow defined paths? or do you just drag and drop them in to the Flow website for review? eg do you publish files using Flow’s integrations or Desktop app?