DropElementWdg Tactic 4.5

[Bassment]

Hey all, I'm trying to get the DropElementWdg working in a custom view the way it works in the VFX template's "shot planner" tool.
I edit the column definition to reflect the drop type and instance type but when I drop an asset into the respective scene and save all changes the name of the asset disappears from the column.
I also tried to set the display expr to @GET(VFX/asset.code) but that does nothing.
In the VFX template, it lists the assets dropped in to scene and I can export a .csv with all the assets listed in each scene. This is what I'd like for my custom view but no luck.
There's been a few changes but the project was originally created from the VFX template.
Any ideas? 

Thanks

[Diego]

Do you have a schema definition for the relation?

[Bassment]

In the project schema I have my "asset" node related to the "scene" node using "asset_code" to "code"
Not sure if this is what you mean?

[Diego]

I understand you want to connect a VFX/asset stype to a VFX/scene stype as VFX/asset is related to VFX/shot. If you check the VFX projecet schema you'll se you need to create a many to many relationship via an auxiliary table (asset_in_scene), this table is automatically created by the schema editor when you select "many to may" as the "Relationship Type", the DropElementWdg will create an entry in this table to relate an asset code to a scene code

[listy]

In the project schema I have my "asset" node related to the "scene" node using "asset_code" to "code"
Not sure if this is what you mean?

I would not recomend you to change relationship on already "in use" projects, as it will require you to recreate or change all sObjects structures. But if you're creating a new project, you should create many_to_many relationships, as Diego mentioned.

[Bassment]

Ok, after a lot of clicking and typing I figured out why this wasn't working.
I somehow removed the following line from the asset drop column definition

<action class="tactic.ui.table.DropElementAction">
    <instance_type>vfx/asset_in_shot</instance_type>
  </action>


Adding this and saving to the definition fixed everything.
On to the next tool.

[Diego]

Great! Thanks for closing the thread with the solution.