Open danielandelin opened 2 years ago
Need to consider scoping shared resource functionality and maybe change the way that this works. Maybe it's a data download from the master to the child account. but all the data exists separately on each account. downloads can happen periodically and pull in new resources that have been added on the master. Data that doesn't exist on the master account will remain on the child account resources without being overwritten.
I can't replicate the issue on staging. Is there a particular document this is happening for?
Hmm... maybe that wasn't the issue. This happened to Sarah when going through some workflows on Centrae's account.
We do still have an issue with Compatibility with Shared resources and Persistent Form resources - Need a way to be able to merge the resource created by the shared form to get the data from the shared resource.
I have another git issue for that though
Can you link that issue in a comment here @danielandelin
When selecting a shared resource as a recipient of a document. The pandadoc generated is unable to use that resource to set as a signatory of the document and that signature block is left unassigned.