On Foundry-to-Gotham actions: One limitation we’ve identified is that properties of Foundry created objects must be lists (list of strings, ints…) in order to port that object to Gotham, given objects are able to have several values for a given property.
Turns out that Foundry actions do not allow the option of having lists as property types. Our current solution is to have an action that creates an intermediate object (an [Object Request FinalObjectType] object type) that we can then integrate into the FinalObjectType backing dataset.
The only reason why we need that intermediate object is to bypass the “list” in properties constrain. We are wondering if there would be a better solution to this problem.
