Any help on this would be greatly appreciated!

I set up a model action on Feedback to save itself (and to save itself and FeedbackSignature) when a new row was created, but to no avail. Still getting the error.

This seems odd:


In the FeedbackSignature model, why would Feedback__r.Id have the right ID, but Feedback__c still have “1”?

Looks like I was able to solve with a model action initiated by a new row on Feedback set to save both Feedback and FeedbackSignature in the same action. Interestingly, it’s still not actually saving FeedbackSignature to the database (the model still has a temporary id), but it’s not giving me the error anymore, so that’s happy. 

So… Glad you figure this out. And sorry this slipped through the cracks. 

You will not be able to save the Signature before saving the Feedback because of the temporary ID.  Trying to save that temp ID to the database will give you an error.  You will have to save Feedback,  which will replace its temp ID with a real one, and pass that along to any models that are using that temp ID.  All this will happen correctly in a single “MultiModel save” but you have to keep your model order right, and you can’t try to do circular references (where A refers to B and B refers to A) cuz we can’t work out the mutual dependencies.  One has to be the winner. 

Hope that all helps.