I recently worked through a need to create and maintain a many-to-many relationship that would be partially managed in Workfront and partially managed in Salesforce. I'm sharing an overview of our solution in case it helps someone down the road.
The business need is to link the implementation effort (managed in a Workfront Project) with the product sold (managed in a Salesforce Asset).
Here's a look at the Fusion scenarios:
Scenario to manage related asset (copies attributes to [asset issue] and manages Salesforce
Unique scenario to manage deleted [asset issue] in Workfront
Scenario to backload [asset issues]. There is additional complexity when creating the issue record to account for closed and dead projects that need flipped to a current status to make the update. Initially I'd included a sleep instruction to allow for the other scenario to complete, but I ended up just manually flipping the status back because of delays in Fusion processing the Salesforce record creation.
One of the "cool" things in the above is the process to update the project Queue (QUED) and create the new Queue Topic (QUET).
Thanks to @Doug_Den_Hoed__AtAppStore, Glenn Coward, and support for tips at places I got stuck.
That Was Totally Wicked, Jason.
I am so pleased you got it going, and have bent the rules (and the typeahead) in a way that will allow for this sophisticated and valuable data relationship to be modelled successfully. Thanks for sharing!